Mac Build upload to App Store Connect Error_ITMS-90283

I’m not entirely sure what the ingestion process is complaining about here, but it’s clear that it’s not happy with your App ID. Are you submitting using Xcode? Or outside of independently, using Transporter or altool?

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

I am experiencing a similar error when doing Validate App within Xcode Organizer.

To isolate the issue, I created a completely new project 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

I also tried to create a provisioning profile in certificates, identities and profiles and do manual provisioning with it, but got the same error. The profile also contained the com.apple.application-identifier. There aren't really a lot of options to go wrong here, I selected Distribution - Mac App Store, Profile type Mac and my App ID from the drop down and then a distribution certificate. That generated the Prov Profile which did include the com.apple.application-identifier.

It seems like either the validate option is broken or the provisioning profiles for Mac are being generated with the application-identifier and shouldn't be.

I'm using Xcode 12.4 on MacOS 11.2

I'm still unable to validate my existing App, however I did discover something interesting.

When I created the identifier for my app there was a pull down menu called App ID prefix, which showed an alphanumeric code, starting in my case with 9FX. However, this is not my team ID, (which starts with SEK and shows up under my name when using the developer site).

If I create the bundle identifier using my SEK TeamID rather than the 9FX number, Organizer can validate it.

I found tech note 2311 from 2014 which talked about having multiple App ID prefixes. it talks about how to move an App ID from a non-Team ID prefix to the Team ID but chances are that info is now outdated.

Unfortunately, this doesn't help solve the problem for my app since the bundle ID can't be changed once a build is uploaded and I have my App on the store already

However, having an App ID prefix which is different from the Team ID appears to somehow relate to the issue.

Not sure if that helps you at all but, if you have an App ID different from your Team ID, it might. If you have found another answer please share.

However, having an App ID prefix which is different from the Team ID
appears to somehow relate to the issue.

Yeah, that’s generally a bad idea, and the fact that the developer web site makes it so easy to fall into this trap is most definitely a bug (r. 70571514).

Unfortunately, this doesn't help solve the problem for my app since
the bundle ID can't be changed once a build is uploaded and I have my
App on the store already

For sale on the store? Or just uploaded to the store?

If it’s the latter, I encourage you to tear down this app and start again with the App ID prefix set to your Team ID. This problem only gets worse as you get further along the path, so it’s best to turn back now.

If the app is already for sale on the store then you have a hard choice to make. You can either continue down this path or you can turn back, but turning back is trickier because it can impact on your users (specifically the one-time loss of keychain items discussed in TN2311). If, in the end, you decide to turn back, you’ll need to contact DevPrograms to have them change your App ID prefix (per the instructions in TN2311).

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

Unfortunately, the app is already for sale on the store, so I'm at the intersection of Rock Street & Hard Place.

I could live with the one-time loss of keychain items if get DevPrograms to change the AppID prefix, but TN2311 doesn't speak to customers already purchased In-App Purchases. Will the In-App purchases still be associated with the App after it is assigned the new Team prefix and, more importantly, will customers retain/be able to restore their purchases they made when the app had the old prefix?

As for continuing down this path, I'm at a loss to determine how. I can't validate the app with the AppID Prefix (which worked in Aug). Is there some way I can stumble down the app id prefix path at least long enough just to get an update out?

Will the In-App purchases still be associated with the App after it is
assigned the new Team prefix and, more importantly, will customers
retain/be able to restore their purchases they made when the app had
the old prefix?

I don’t know, alas. In-app purchase isn’t an area I know a lot about, alas.

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