4

I've got a command line script I use to compile, archive and submit my ios builds to ITC for TestFlight deployment. They work great, but I recently ran into an issue when trying to use an embedded framework within my otherwise working project. My script compiles and archives the project successfully but is getting ITC signing errors because of the embedded binary conflict. 

xctool -workspace $BASE_DIR/$PROJECT_NAME -scheme $SCHEME -configuration $CONFIG clean archive -archivePath ./$PRODUCT_NAME.xcarchive
xcodebuild -exportArchive -archivePath ./$PRODUCT_NAME.xcarchive -exportPath $PRODUCT_NAME -exportFormat ipa -exportProvisioningProfile "$DIST_PROVISIONING_PROFILE_NAME"

# result is successful, with .ipa file generated

After a successful compilation my script tries to upload to ITC, and fails with the below msg. I get the same message if I try to upload the generated IPA file to ITC myself using Application Loader tool.

ERROR ITMS-90046: "Invalid Code Signing Entitlements. Your application bundle's signature contains code signing entitlements that are not supported on iOS. Specifically, value 'XXXXXXXXX.com.domain.Product' for key 'application-identifier' in 'Payload/Product.app/Frameworks/Charts.framework/Charts' is not supported. This value should be a string starting with your TEAMID, followed by a dot '.', followed by the bundle identifier.

There is no application-identifier string used in my project or settings that I can find with a global search.

Extra Info

com.domain.Product would be my project's main bundleIdentifier, which has a distribution certificate and provisioning profile generated for it. Without the embedded binary that works just fine. The "Charts" embedded project has a bundleIdentifier but the team is set to "None" in the Info tab, and signing is set to Automatic. Since it is an embedded binary/framework, I'm assuming it doesn't independently sign it. When using Xcode's Archive, it is listed as a subset of the main Project with no independent identifier or entitlements.

I have also tried creating an independent appId and distribution provisioning profile for the embedded binary called "com.domain.ProductCharts" and setup the project correctly. This does not change the error.

I have further tried setting the embedded binary's project to use the same bundleIdentier and settings as the parent Project, but this does not change the error.

Why is xctool/xcodebuild unable to properly compile and sign this to get through to ITC, while the native Archiver can?

Miro
  • 5,307
  • 2
  • 39
  • 64

3 Answers3

3

Currently, I encountered what I think is a bug in xcodebuild command similar to this, way I fixed it for me was to setup provisioning profile in the project settings. Try updating your project and run build again.

The investigation into the issue was here: https://forums.developer.apple.com/thread/14378

But others reported problem with associated domains:

SO question: Apple Store submit fails with Error ITMS-90046, but Associated Domains is not among entitlements

What is your OS, XCode ... etc?

Community
  • 1
  • 1
jr.root.cs
  • 185
  • 1
  • 15
  • The forum topic seems identical to the problem I'm having, and their solution is to use XCode to build the app store release. That I can do, but since my build script is run multiple times a day for TestFlight releases, it becomes tedious fast. I tried the manual entitlements.plist addition but that didn't help. My provisioning profiles+ code signing are all properly set on the project, but I also set it in the xcodebuild cmd specifically. Using latest Xcode 7.2, on Yosemite. It seems like xcodebuild needs a bug fix for this. – Miro Jan 04 '16 at 02:22
  • Does anyone know if Apple has at least acknowledged this issue? As of Xcode 7.3 they've still not fixed it. – Bungles Jul 07 '16 at 19:14
  • "way I fixed it for me was to setup provisioning profile in the project settings" -- Which project, the app or the embedded framework? – Bungles Jul 07 '16 at 19:45
0

Just a guess: Maybe you need to specify an application-identifier in your Entitlements.plist if you use the command line. Here https://developer.apple.com/library/ios/qa/qa1710/_index.html it is stated that in "In modern versions of Xcode.."

You said:

They work great, but I recently ran into an issue...

Have you created a new profile meanwhile and now there are two? Or two certificates? Here is a description on how to check your entitlements. Maybe this helps.

theguy
  • 1,232
  • 1
  • 9
  • 21
  • I have tried creating the entitlements.plist with the identifier set, but it did not change anything. – Miro Dec 31 '15 at 17:39
0

Creating .entitlements for the embedded framework will solve the issue only in Xcode 7.x. In the version 8.x the issue still exists.

Dmitry
  • 171
  • 3
  • 12