If I am reading this correctly: Before January 31: you can submit new app versions without updating the rating but you should update the rating if you do After January 31: before you can submit the app, you must update the rating You don't have to immediately push a new version, apps will not be removed or blocked. It's only if you want to push a new version that you will then be stopped until you update the age rating. I had an app that I 'Removed from Sale' months back - and I still got that notification too.

the 'profileContent' is binary data that is the binary content of the mobile provisioning file. Save that binary data to disk as a .mobileprovision file, and work from there This tech note is pretty good when you're deailing with provisioning files using bash: https://developer.apple.com/documentation/technotes/tn3125-inside-code-signing-provisioning-profiles

individual key will be tied to the permissions that that individual user has, ie, the users role in app store connect users and access, https://developer.apple.com/help/account/access/roles/

it might depend on the role permissions that the authkey has that is limiting it to development certificates, so maybe check-in on that. ie, maybe that role does not have access to distribution certificates https://developer.apple.com/help/account/access/roles/

Hi @Mishalk , You must apply for an Enterprise Developer Account. It is a completely separate entity to any App Store Developer account you may have: https://developer.apple.com/programs/enterprise/ If you're after an Enterprise version of App Store Connect API, then the Enterprise Account Holder must sign-in to request access to Enterprise Program API in the Integrations section of Users and Access. https://developer.apple.com/documentation/enterpriseprogramapi

Hi @ww-bmerivale - did you resolve this? Our team is using Enterprise API successfully. I know there were teething issues when it was first released. You wont see Team Keys etc until the request for API access is accepted by Apple. Enterprise account screen is slightly different to App Store account screen:

hi @huanling820713 Its been a few years since your question, but in case you were not across it, Apple introduced enterprise API this year (2024): https://developer.apple.com/documentation/enterpriseprogramapi

Hi @CloudosaurusRex , I did not get an answer - we have just accepted that this is how it works. Many attempts to workaround, but basically, when the app is signed with the certificate and profiles to produce an IPA, it is at that stage the aps-environment is set. Sign with a distribution certificate (adhoc/store/inhouse) - you get prod - sign with a developer certificate, you get sandbox

hi @Fictix , Did you ever get resolution on this? I have similar issue, but with a single test device (duplicated 5 times), and fortunately saw your post - so have not disabled them all - the one I did disable and attempt to re-enable brought up same error about the duplicate UDID.

API Key issue is now resolved by revoking old keys and generating and using new keys. API works as expected: https://forums.developer.apple.com/forums/thread/763225

API Key issue is resolved by revoking old keys and generating and using new keys. API works as expected.

Thanks - our team faced similar issue - and I can confirm for us it is now resolved with newly generated keys working as expected. API calls are succeeding. Please pass on grateful thanks to the Enterprise API team for making these APIs available - a welcome bonus.

For anyone coming here, know that Apple has released Enterprise Program API for managing resource in the Enterprise domain. https://developer.apple.com/documentation/EnterpriseProgramAPI Only caveat for me at moment, is that I am having issues reading the API key that is generated. I have no problems reading our regular App Store API keys. The exact same code does not read the Enterprise API Key

This is great news. I have dipped toes into the water to try it out - but I am having an issue with the API Key that is generated. So curious to know if anyone else coming here has faced similar issues? Essentially, the exact same code used to read our regular App Store Connect API Key does not work when reading the Enterprise API key. We use (from CryptoKit): P256.Signing.PrivateKey(pemRepresentation: pemString) to read the string representation of the key from the p8 file. This works fine for App Store Connect API key files. This does not work for Enterprise API key files. Error is 'invalidPEMDocument' suggesting some issue either with the key file, or, maybe the p8 for Enterprise is not in PEM format, and I should use a different format to read it.

Hi Andrea, The store account needs to be a new and separate apple id account from the enterprise account. The accounts cannot map to the same person. Proof of identity is required, and that identity cannot be the same person. We face similar issues, - our approach was to nominate a separate senior team member to be the 'account holder' for each account. We queried directly with apple support, but It is currently the apple policy so we just had to work with that.