Hi Christian, taking a guess here, but what stood out to me is the error regarding no internet connectivity when attempting to connect to http://ocsp.apple.com thats an apple certificate validation server most likely scenario is maybe that this is first launch of app on this device, and the OS is attempting to validate the signing-certificate/app with apple servers, and can't reach them because the device has no internet connection. this page shows the purpose of the URL as certificate validation: https://support.apple.com/en-us/101555 if the certificate can't be validated, it won't launch the app

there is an outage https://developer.apple.com/system-status/

there's an outage https://developer.apple.com/system-status/

there's an outage https://www.apple.com/au/support/systemstatus/

there's an outage https://www.apple.com/au/support/systemstatus/

https://www.apple.com/au/support/systemstatus/

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.