iOS code signing, handled for each build.

The words, explained

You only need to create the App Store Connect key. Certificates and profiles are sorted for each build.

• Signing certificate: proves to Apple that your app comes from your Apple Developer account
• Provisioning profile: a file from Apple that links your app, its App ID and your certificate
• App Store Connect key: a small file ending in .p8 that lets Push200 talk to Apple for you, with an Issuer ID

Creating your key

1. 01

   Open Apple's keys page

   It's in App Store Connect under Users and Access, then Integrations. Stay on Team Keys.

2. 02

   Make a new key

   Name it Push200, choose App Manager access, and press Generate. Always make a new one, because Apple won't let you download an old key again.

3. 03

   Download it and copy the Issuer ID

   Download the .p8 file. Apple only lets you download it once. Then copy the Issuer ID shown above your keys.

4. 04

   Add both to Push200

   We check them with Apple straight away. The key goes into your GitHub's encrypted secrets.

If you reach the certificate limit

Apple allows only a few signing certificates at a time. This is normal if you've published apps before, and it doesn't mean your key is wrong. You have two choices:

• Use a certificate you already have: paste its private key into the box Push200 shows you. It's text, usually in a file ending in .pem or .key
• Remove a certificate you no longer use on Apple's certificates page, and we'll create a new one for you. Check nothing else uses it first, because another build service or developer using it would stop being able to sign new builds

Where your certificate key lives

Your Apple certificate key goes into your own GitHub as an encrypted secret, and Push200 keeps no copy. Apple limits how many certificates you can have, so when you add another app, a short job in your own GitHub copies the key across.