In trying to upload to appstoreConnect an app, using Xojo’s new signing and notarising details I hit the following problems:
If I use the ID from the Distribution certificate - I get the error “Error Retrieving the AppID from the App Store”. Yet, as far as I can see the bundleID is the same on the app as in the store.
If I use the ID from the Developer certificate - I get the error “The Developer ID value has to be the full Apple Distribution string”
So, I have determined that I should be using the ID from the Distribution Certificate. But now, by using Transporter to upload the app, I get the message…
Validation failed (409)
Invalid Code Signing Entitlements. The entitlements in your app bundle signature do not match the ones that are contained in the provisioning profile. According to the provisioning profile, the bundle contains a key value that is not allowed: ‘XXXXXXX.biz.iThought.PhotoFiler2MAS’ for the key ‘com.apple.application-identifier’ in ‘biz.iThought.PhotoFiler2MAS.pkg/Payload/PhotoFiler 3.xx.app/Contents/MacOS/PhotoFiler 3.xx’ (ID: YYYYYY)
Where XXXXXX is the Distribution Certificate code.
I have downloaded a new provisioning profile for the mac, with the correct bundleID but still seems to give the same error.
Besides the entitlements or AppID error message… one thing that is really odd to me is the pkg file using the bundle identifier as the file name instead of the app name.
“biz.iThought.PhotoFiler2MAS.pkg”
Should be
“PhotoFiler 3.xx.pkg”
Also, I would recommend not to use version numbers in the app name… because that simply doesn’t make sense on an app distributed to the MAS (so the app name should be just “PhotoFiler”)
This plagued me for weeks prior to going on holiday. I fixed it and now can’t remember the solution. I will continue to look. I’m pretty sure it involved adding something to the plist. It wouldn’t work with Xojo’s built in signing or AppWrapper.
As for the entitlements error message… maybe you’re enabling entitlements during the Provisioning profile creation that are not really required / used by your app?
Also, during the provisioning profile creation, did you choose the right option? → Mac App Store Connect and, then, in the next page… just Mac instead of Mac Catalyst?
Apple’s messages related with “everything this” doesn’t always point to the right cause of the problem… (by personal experience). And exactly that message is the one that can lead to enabled entitlements that are not required / used / set by the app.
I did send a private message to you to see if you can send over the Distribution Profile so I can look into it… just to see if I can see “something else” there.