Invalid Provisioning Profile error when updating macOs app with Xcode 14.2

I'm trying to update our Mac version of our iOS app using Xcode 14.2, the update worked using Xcode 11. The detailed error is:

Invalid Provisioning Profile. The provisioning profile included in the bundle maccatalyst.com.xxxxxxx.yyyyyyyy [maccatalyst.com.xxxxxxx.yyyyyyyy.pkg/Payload/yyyyyyy.app] is invalid. [Invalid 'com.apple.application-identifier' entitlement value.] For more information, visit the macOS Developer Portal. (ID: 8dd00921-66a8-4eea-b0c5-e674b5073df5)

The entitlements are: com.apple.security.files.user-selected.read-write true com.apple.developer.associated-application-identifier YYYYYYYYYY.com.xxxxxxxx.yyyyyyyy com.apple.application-identifier ZZZZZZZZZZ.maccatalyst.com.xxxxxxxx.yyyyyyyyy com.apple.security.network.server true com.apple.security.personal-information.photos-library true com.apple.security.device.bluetooth true get-task-allow false com.apple.security.network.client true com.apple.security.device.camera true com.apple.developer.team-identifier ZZZZZZZZZZ application-identifier ZZZZZZZZZZ.maccatalyst.com.xxxxxxxxxx.yyyyyyyyy com.apple.security.app-sandbox true com.apple.security.personal-information.location true

I assume the problem has something to do with the application-identifier having a team identifier prefix (ZZZZZZ...) instead of the developer identifier prefix (YYYYYY...)? How can I fix this? I have seen posts from other people having the same problem but haven't found any solution.

Up vote post of anterok Down vote post of anterok
733 views
Posted by
anterok
Reply
Add a Comment

Replies

Does the Mac version of your app ship on the Mac App Store? Or do you distribute it independently, using Developer ID signing?

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

Posted by
eskimo
Up vote reply of eskimo Down vote reply of eskimo
Add a Comment

It ships on the Mac App Store

Posted by
anterok
Up vote reply of anterok Down vote reply of anterok
Add a Comment

OK.

You wrote:

I assume the problem has something to do with the application-identifier having a team identifier prefix (ZZZZZZ.) instead of the developer identifier prefix (YYYYYY.)?

The latter is not related to the developer. Rather, when you created your Mac app you gave it a unique App ID prefix [1].

Unique App ID prefixe are a pain. While they are still supported, they limit your options and often cause tooling problems. In most cases it’s easier to switch to using your Team ID as your App ID prefix.

The standard reference on this is TN2311 Managing Multiple App ID Prefixes. I also discuss one aspect of this change in App ID Prefix Change and Keychain Access.

So, my advice is:

  1. Look at your app to see whether changing from a unique App ID prefix to your Team ID is feasible.

  2. If it is, start that process.

  3. Then deal with this issue.

If changing your App ID prefix isn’t feasible, we’ll have to explore other options.

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

[1] This probably isn’t your fault, in that there’s an ongoing misfeature on the Developer website (r. 70571514) that encourages folks to make this mistake.

Posted by
eskimo
Up vote reply of eskimo Down vote reply of eskimo
Add a Comment