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.

This is not possible. TestFlight will only accept apps signed with AppStore Distribution Certificate. To distribute apps with Enterprise distribution profiles you must manage distribution yourself. When you export an IPA from an XCARCHIVE using Xcode Organiser, you will see options to generate files (plists etc) that assist you in IPA deployment. There are 3rd party platforms that enable Enterprise Distribution, for example Test Fairy, and until recently Microsoft App Center.

hi @ChuckMN , thanks for your comprehensive reply, i appreciate the time you spent. We are across all the things you mentioned. We are very large org also, and have had our apple developer and apple enterprise accounts for many years. We have semi-automated workarounds (scripts) to ease some of the pain of managing the enterprise side, but that of course is not ideal. We will just need to continue as we have, or liaise with our apple contacts to see what may work. Apple is certainly trying to move Enterprise Users to other options like Custom Apps (considering the annual enterprise review process in place these days). Thanks.

You can only have a maximum of 2 iOS Distribution Certificates active at a time - you must revoke one of them in order to create a new one. But, it sounds like you're not sure which one to revoke, because you can't tell which one is being used in your provisioning profiles, because both certificates have the same date, making it hard to distinguish. If you examine (Get Info) on the downloaded provisioning profiles, using Finder on the mac, you can see into them and see the Serial Number, and the SHA-1 of the certificate that profile is using. By cross referencing that Serial Number in the profile to the Serial number of the certificates, you can then determine which cert is being used in your distribution profiles. The creation date/time of the cert is also rendered in keychain and the finder down to the second, in addition to the serial number of the cert, so that is another way to distinguish between certs if you download them on your mac to cross reference them with your profiles. Hope that is of assistance.

there was an outage, now resolved https://developer.apple.com/system-status/ notary service still showing outage the moment

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

it took a while before it was showing on the status page - but there's an outage: https://developer.apple.com/system-status/

We had similar issue in project with embedded sticker pack, and resolved it by adding the UIRequiredDeviceCapabilities to the extension's info plist - not the plist of the main app. It looks like you've added the right settings, but just in the wrong place. Additionally, for anyone else arriving here, we had originally added the setting in the Build Settings info plist section, which presumably should be exported to the extensions info plist when the project is archived, however, it does not. We resolved the issue by adding directly to the info plist of the extension , not the build settings of the extension.

Hi Ricard, can you clarify how you managed to get appstore connect api access (and a key) for an enterprise account? As far as I have been able to ascertain the api key is not supported for enterprise accounts. Is see no 'Keys' tab in Users and Access section of my enterprise accounts like I do in regular developer accounts. Thanks.