Can't upload macOS app: legacy App ID prefix differs from Team ID (errors 91130, 90286)

I need Apple to update a legacy App ID prefix to match my Team ID, and my support case has gone unanswered. Posting here in hopes a code-signing engineer can advise or nudge it along.

My app VHDLRef (bundle ID com.squishLogic.VHDLRef, Apple ID 418473744) dates back to my original individual developer account. The App ID's prefix is still the legacy value CN7ZHAEHF4, while my current team (squishLogic LLC) has Team ID R55F2X4J69. Certificates, Identifiers & Profiles confirms the prefix mismatch.

The iOS app builds, uploads, and was just approved (v3.2), since iOS accepts an App ID prefix that differs from the Team ID. The macOS build of the same target is rejected at upload by App Store Connect:

Error 91130: "Invalid Provisioning Profile ... Invalid 'com.apple.application-identifier' entitlement value." Error 90286: "the 'CN7ZHAEHF4.com.squishLogic.VHDLRef' value for the com.apple.application-identifier key ... isn't supported. This value should be a string that starts with your Team ID, followed by a dot, followed by the bundle ID."

My understanding is that the Mac App Store requires application-identifier to be TeamID.bundleID, there is no self-service way to change an App ID prefix, and the fix is for Apple to update the prefix to R55F2X4J69. The app has no keychain items or keychain sharing (entitlements are empty), so no user data depends on the old prefix.

Questions: (1) Is a prefix update the correct and available fix here? (2) Is there any developer-side workaround short of shipping the Mac app under a new bundle ID and losing universal purchase? (3) Any way to escalate the support case, given phone support is currently unavailable?

Case number: 20000152117550

Answered by DTS Engineer in 903832022
1- Is a prefix update the correct and available fix here?

Yes.

There are a couple of caveats I want to highlight:

  • Keychain access — Fortunately it doesn’t look like this is an issue for you. For anyone else reading along at home, I talk about this in depth in App ID Prefix Change and Keychain Access.
  • Extensions — If your app contains any extensions, make sure that you’re clear with DevPrograms that they need to change the prefix on those App IDs as well.
2- Is there any developer-side workaround … ?

No.

3- Any way to escalate the support case … ?

No.

The case number you posted indicates that you’re in touch with DevPrograms, who are the right folks to deal with this.

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

1- Is a prefix update the correct and available fix here?

Yes.

There are a couple of caveats I want to highlight:

  • Keychain access — Fortunately it doesn’t look like this is an issue for you. For anyone else reading along at home, I talk about this in depth in App ID Prefix Change and Keychain Access.
  • Extensions — If your app contains any extensions, make sure that you’re clear with DevPrograms that they need to change the prefix on those App IDs as well.
2- Is there any developer-side workaround … ?

No.

3- Any way to escalate the support case … ?

No.

The case number you posted indicates that you’re in touch with DevPrograms, who are the right folks to deal with this.

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

Can't upload macOS app: legacy App ID prefix differs from Team ID (errors 91130, 90286)
 
 
Q