Text of developer.apple.com › forums › thread › 835497 as Styx crawled it on Nov 19, 2026. The page may have changed since. Only its words are kept, without pictures or layout, and only the first part of a long page.

Open the live page

Updating App - Validation Hell - 9… | Apple Developer Forums

Updating App - Validation Hell - 90286, 91130 Code Signing Certificates, Identifiers & Profiles You’re now watching this thread. If you’ve opted in to email or web notifications, you’ll be notified when there’s activity. Click again to stop watching or visit your profile to manage watched threads and notifications. You’ve stopped watching this thread and will no longer receive emails or web notifications when there’s activity.

Click again to start watching. DrMiller OP Created Jun ’26 Replies 21 Boosts 0 Views 3.6k Participants 3 Updating an App for the first time since 2011. Build, Analyze, Archive all successful. Automatically Manage Signing checked. Validation fails with 90286 - Invalid code signing entitlements, and 91130 - Invalid Provisioning Profile dozens of times after tweaks, clean builds, trying manual signing (thought I was done with that), etc.

For 90286 it seems my Developer ID , e.g. 346JXXXXX (not Team ID, QZ99XXXXX) is the prefix for the bundle ID, com.company.app-name and that generates the error? For 91130 it's invalid "com.apple.application-identifier" which I assume is the same issue with a Developer ID instead of a Team ID. The original version of the app was QZ99XXXXX.com.company.app-name. I even changed the bundle identifier in Xcode to that, and got this: App Record Creation failed due to request containing an attribute already in use.

The app name you entered is already being used for another app in your account. If you would like to use the name for this app you will need to submit an update to your other app to change the name, or remove it from App Store Connect. Yes, the original app name is being used for an app in my account. I was trying to update the app, checked all the boxes, added update text, but of course there was no build to upload. Would appreciate any help.

Answered by DTS Engineer in 899094022 I’m glad you’re making progress here. My experience helping folks with issues like this is that: They first bump into the issue when they adopt an API that requires a restricted entitlement. Prior to that they didn’t need a provisioning profile, and thus the unique App ID prefix wasn’t a concern. The first step is to contact DevPrograms to change the App ID prefix. There are a couple of pitfalls with that: The App ID prefix change can affect APIs, most notably the keychain.

See App ID Prefix Change and Keychain Access . If the app includes app extensions, and those are also using a unique App ID prefix, you have to get DevPrograms to change their App IDs as well. Once that’s done, you can confirm that things are working correctly by manually creating a profile. See the instructions here . Again, if you have app extensions, you have to repeat this for each extension. Once that’s done it’s ‘merely’ a matter of getting Xcode to recognise the change.

My process for that is: In the Xcode organiser, delete the archive that I’m trying to upload (or in the project, update the version). In the Xcode project, choose Product > Clean Build Folder. Quit Xcode. Trash the contents of ~/Library/Developer/Xcode/UserData/Provisioning Profiles [1]. Relaunch Xcode. Choose Product > Archive. And then use the Xcode organiser to upload that. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = "eskimo" + "1" + "@" + "apple.com" [1] Or ~/Library/MobileDevice/Provisioning Profiles if you’re using an old version of Xcode.

Replies 21 Boosts 0 Views 3.6k Participants 3 DTS Engineer OP Apple Jun ’26 What platform are you targeting? This matters because it seems like your app is using a unique App ID prefix, and those aren’t supported on the Mac. which I assume is the same issue with a Developer ID instead of a Team ID. OK, let’s clarify terminology. Developer ID isn’t a term we use in this context. Rather, it refer to the general mechanism for distributing Mac apps directly, rather than via the Mac App Store.

See Developer > Developer ID . You’re dealing with a unique App ID prefix. I explain that identifier, and many others, in Code Signing Identifiers Explained . Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = "eskimo" + "1" + "@" + "apple.com" Add comment DrMiller OP Jun ’26 To clarify, this is a 2021 MacOS app (not 2011), 346JXXXXXX is my Team Member ID, QZ99XXXXXX is my Team ID, my Bundle ID is in this format: com.company.app-name, this app's Apple ID is 1575XXXXXX.

I'm the Admin for the Team (of one). I have no idea why the Team Member ID prefix is appearing in the error messages for a MacOS app and causing this issue. I didn't even know I had that Team Member ID. Hope this info can lead to some resolution. Thanks. Add comment DrMiller OP Jun ’26 Here is the complete descriptions for the validation errors. Again, don't know why Automatic Signing Management for a MacOS app generates these.

Invalid code signing entitlements. Your application bundle’s signature contains code signing entitlements that aren’t supported on macOS. Specifically, the “346JXXXXXXX.com.enatal.Contact-Sheet-Maker” value for the com.apple.application-identifier key in “com.enatal.Contact-Sheet-Maker.pkg/Payload/Photo Contact Sheets.app/Contents/MacOS/Photo Contact Sheets” isn’t supported. This value should be a string that starts with your Team ID, followed by a dot (“.”), followed by the bundle ID.

Invalid Provisioning Profile. The provisioning profile included in the bundle com.enatal.Contact-Sheet-Maker [Photo Contact Sheets] is invalid. Invalid 'com.apple.application-identifier' entitlement value. For more information, visit the macOS Developer Portal. Add comment DTS Engineer OP Apple Jun ’26 346JXXXXXX is my Team Member ID No it isn’t. Rather, it’s your App ID prefix. That much is very clear from my view of your team, but you can prove it for yourself.

Do this: Go to the Certificates, Identifiers, and Profiles section of the Developer website Switch to Identifiers. Filter for App IDs containing com.company.app-name (well, your real bundle ID, not the redacted one we’re using here). Open the one you find. At the top right you’ll see your Team ID and in the App ID Prefix field you’ll see your… well… App ID prefix. Here’s an example of what that looks like for an App ID in one of the DTS test teams: If you manually generate a provisioning profile for that App ID and then dump that profile you’ll see something like this: % security cms -D -i AppIDPrefixTest_Mac_Dev.provisionprofile | plutil -p - { … "ApplicationIdentifierPrefix" => [ 0 => "VYRRC68ZE6" ] … "Entitlements" => { "com.apple.application-identifier" => "VYRRC68ZE6.com.example.apple-samplecode.appidprefixtest" … "com.apple.developer.team-identifier" => "Z7P62XVNWC" … } … "TeamIdentifier" => [ 0 => "Z7P62XVNWC" ] … } Now how the App ID prefix differs from the Team ID.

The interesting thing is how you managed to ship a Mac app this way. We do not, in general, support unique App ID prefixes on macOS [1]. I think the answer likes in this: % codesign -d --entitlements - "YourAppName.app" … [Dict] [Key] com.apple.security.app-sandbox [Value] [Bool] true [Key] com.apple.security.files.user-selected.read-write [Value] [Bool] true Previously your app only used unrestricted entitlements, and thus had no need for a provisioning profile.

Note The terms I’m using — unrestricted entitlement , restricted entitlement , and so on — are from from TN3125 Inside Code Signing: Provisioning Profiles . Nowadays this sort of thing is rare because most apps want to use TestFlight and TestFlight requires the use of restricted entitlements. See TestFlight, Provisioning Profiles, and the Mac App Store . I’m not sure if Xcode’s automatic code signing is capable of dealing with this case, which suggests two paths forward.

The best one, at least in the long term, is to migrate from a unique App ID prefix to using your Team ID. That will e

The rest of this page is on the live site.