Mac Catalyst: ERROR ITMS-90283: "Invalid Provisioning Profile..."

Question

Created Feb ’21

Replies 3

Boosts 0

Views 1.1k

Participants 2

We have an existing iOS/tvOS app on the App Store available to customers as a Universal Purchase (same bundleId).

Via Mac Catalyst we are looking to port the iOS app to MacOS and submit/release with the same bundleId.

However, uploading to the store via Apple Transporter gives the following error:

Code Block ERROR ITMS-90283: "Invalid Provisioning Profile. The provisioning profile included in the bundle com.XYZ.ABC [com.XYZ.pkg/Payload/MyApp.app/Contents/Resources/ABC.bundle] is invalid. [Invalid 'com.apple.application-identifier' entitlement value.] For more information, visit the macOS Developer Portal."

The app is built with Xcode 12.3 and contains a Mac bundle (ABC) embedded inside My.app

Boost

Answer 1

greg@didsoftware.com OP

Feb ’21

I have a simpler set-up (Standalone MacApp) and am experiencing a similar error when doing Validate App within Organizer.

I created a completely new project with for Mac OS App from the template, used the bundle identifier of my original project and set provisioning to have Xcode automatically manage. The provisioning profile shows "none required" and Organizer validate says everything is OK. I added the In-App purchase capability and Xcode changes the profile to Xcode managed Profile.

Clicking on the i beside Xcode managed profile shows the profile does contain a com.apple.application-identifier and if you then click on the prov icon you can actually drag and drop it on something like textEdit to examine the contents. There is some binary data but it was clear that there was a plist dictionary of Entitlements with a key value pair for com.apple.application-identifier which did appear correct

I also tried to create a provisioning profile and do manual provisioning with it, but got the same error. That profile also contained the com.apple.application-identifier

I suspect, based on some googling that this is an issue on Apple's side and it may correct itself. But if you have added capabilities like IN-App purchase and don't need them for your Mac target, removing them might be a solution.

0

Answer 2

AndrewADCL OP

Feb ’21

We have also tried switching between manual and automatic provisioning and making changes to the AppId with no success.

0

Answer 3

greg@didsoftware.com OP

Feb ’21

Further research determined that, in my case at least, the problem seemed to centre around using an App Id for a prefix instead of the team ID. I think the ability to create App ID prefixes ended in 2011, but if you've been around since then, maybe it is tripping you up as well

Further info [https://developer.apple.com/forums/thread/672934)

Also Tech Note about App IDs [https://developer.apple.com/library/archive/technotes/tn2311/_index.html)

0