ERROR ITMS-90046 using xctool / xcodebuild versus Xcode Archive success

I have a script command line that I use to compile, archive and send my ios collections to ITC to deploy TestFlight. They work fine, but I recently ran into a problem while trying to use the embedded infrastructure as part of my other project. My script compiles and archives the project successfully, but receives ITC signature errors due to the built-in 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 successful compilation, my script tries to load into ITC and does not work with the following msg. I get the same message if I try to upload the generated IPA file to ITC myself using the Application Loader tool.

ERROR ITMS-90046: "Invalid code signing rights. The package signature contains code signing rights that are not supported by iOS. In particular, the value is" XXXXXXXXX.com.domain.Product "for the key" application identifier "in" Payload / Product.app/Frameworks/Charts.framework/Charts "is not supported. This value must be a line starting with your TEAMID, followed by a dot". "Followed by the package identifier.

In my project or settings, which can be found during a global search, there is no application identifier string.

additional information

com.domain.Product , , . , . "" bundleIdentifier, "" "", "". /, , . Xcode Archive .

, com.domain.ProductCharts, . .

, , .

xctool/xcodebuild , ITC, Archiver ?

+4
3

, , , ​​ xcodebuild, , , provisioning profile . .

: https://forums.developer.apple.com/thread/14378

associated domains:

SO: Apple Store ITMS-90046,

, XCode... ..?

+3

: , application-identifier Entitlements.plist, . https://developer.apple.com/library/ios/qa/qa1710/_index.html , " Xcode.."

:

, ...

, ? ? , . , .

0

Creating .entences for the built-in framework will solve the problem only in Xcode 7.x. In version 8.x, the problem still exists.

0
source

Source: https://habr.com/ru/post/1621381/


All Articles