Post

Replies

Boosts

Views

Activity

Unique App ID prefix migration stalled; Mac App Store validation fails with 90286/91130 on a universal-purchase app
My two apps, com.qrafter.Qrafter and com.qrafter.QrafterPro, have been on the iOS App Store since 2011, and their App IDs still use my team's unique App ID prefix 99T3FA87E9 instead of the Team ID GH4CGS3B5H. I'm adding native Mac versions to the same App Store records (universal purchase), so the bundle IDs can't change. Every profile Apple generates for these App IDs pairs com.apple.application-identifier = 99T3FA87E9.com.qrafter.Qrafter with com.apple.developer.team-identifier = GH4CGS3B5H. iOS uploads are accepted, but Mac App Store validation (xcrun altool --validate-app -t macos) rejects even a minimal one-window app with exactly two errors: Invalid code signing entitlements. … the "99T3FA87E9.com.qrafter.Qrafter" 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. (90286) Invalid Provisioning Profile. … Invalid 'com.apple.application-identifier' entitlement value. (91130) Following "Code Signing Identifiers Explained" (thread 811970), I requested the prefix migration through Contact Us on 4 September (case 102953576372). On 20 September Developer Support asked me to confirm the one-time keychain data loss described in "App ID Prefix Change and Keychain Access" (thread 706128), and I confirmed. Since then the case has had no reply despite follow-ups on 24 and 29 September, and as of 6 October both App IDs still show 99T3FA87E9. Two questions: Is there anything else I need to do to get case 102953576372 completed, or a better route to escalate it? Is there any way to ship a Mac App Store build for these App IDs before the migration, or is the migration the only path? I have a minimal sample project and the full validation log if that helps.
2
0
411
4w
macOS 26 not available under iPhone and iPad Apps on Apple Silicon Macs
To make an iOS app available on Apple Silicon Macs, we need to enable the availability option under Pricing and Availability in App Store Connect. But unfortunately, macOS 26 is not still available as a choice there and I don't want to make the app available on earlier macOS versions. Does anyone have any solutions? Would adding the LSMinimumSystemVersion key to Info.plist work?
1
0
287
Sep ’25
MacBook Pro provisioning UDID on macOS Ventura shows as iPod when registering
The provisioning UDID of my MacBook Pro with an M2 Max processor registers as an iPod in the devices section of my developer account. Because of that, I cannot test my macOS apps on this device, reducing it to a brick as long as macOS development is considered. Has anyone encountered such an error? I believe the UDID is fixed, so with more Apple silicon devices, we may start seeing these kind of bugs unless Apple does something to remedy the issue.
6
2
2.7k
Aug ’23
Unique App ID prefix migration stalled; Mac App Store validation fails with 90286/91130 on a universal-purchase app
My two apps, com.qrafter.Qrafter and com.qrafter.QrafterPro, have been on the iOS App Store since 2011, and their App IDs still use my team's unique App ID prefix 99T3FA87E9 instead of the Team ID GH4CGS3B5H. I'm adding native Mac versions to the same App Store records (universal purchase), so the bundle IDs can't change. Every profile Apple generates for these App IDs pairs com.apple.application-identifier = 99T3FA87E9.com.qrafter.Qrafter with com.apple.developer.team-identifier = GH4CGS3B5H. iOS uploads are accepted, but Mac App Store validation (xcrun altool --validate-app -t macos) rejects even a minimal one-window app with exactly two errors: Invalid code signing entitlements. … the "99T3FA87E9.com.qrafter.Qrafter" 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. (90286) Invalid Provisioning Profile. … Invalid 'com.apple.application-identifier' entitlement value. (91130) Following "Code Signing Identifiers Explained" (thread 811970), I requested the prefix migration through Contact Us on 4 September (case 102953576372). On 20 September Developer Support asked me to confirm the one-time keychain data loss described in "App ID Prefix Change and Keychain Access" (thread 706128), and I confirmed. Since then the case has had no reply despite follow-ups on 24 and 29 September, and as of 6 October both App IDs still show 99T3FA87E9. Two questions: Is there anything else I need to do to get case 102953576372 completed, or a better route to escalate it? Is there any way to ship a Mac App Store build for these App IDs before the migration, or is the migration the only path? I have a minimal sample project and the full validation log if that helps.
Replies
2
Boosts
0
Views
411
Activity
4w
macOS 26 not available under iPhone and iPad Apps on Apple Silicon Macs
To make an iOS app available on Apple Silicon Macs, we need to enable the availability option under Pricing and Availability in App Store Connect. But unfortunately, macOS 26 is not still available as a choice there and I don't want to make the app available on earlier macOS versions. Does anyone have any solutions? Would adding the LSMinimumSystemVersion key to Info.plist work?
Replies
1
Boosts
0
Views
287
Activity
Sep ’25
MacBook Pro provisioning UDID on macOS Ventura shows as iPod when registering
The provisioning UDID of my MacBook Pro with an M2 Max processor registers as an iPod in the devices section of my developer account. Because of that, I cannot test my macOS apps on this device, reducing it to a brick as long as macOS development is considered. Has anyone encountered such an error? I believe the UDID is fixed, so with more Apple silicon devices, we may start seeing these kind of bugs unless Apple does something to remedy the issue.
Replies
6
Boosts
2
Views
2.7k
Activity
Aug ’23