Skip to main content

iOS Renew & Send Apple Certificates

When the iOS signing certificates expire we can no longer build or publish your app, so we need you to generate fresh ones and send them to us.

What we need​

Required (Stores / distribution):

  • Distribution certificate: the .cer and the .p12, with its password
  • App Store provisioning profiles, for both the app and the Notification Service Extension (NSE)

Optional (development):

  • Development certificate: the .cer and the .p12, with its password
  • Development provisioning profiles (app and NSE)
warning

We need the password of each .p12 — without it the certificate cannot be used.

How to get them​

  1. Sign in to Apple Developer → Certificates, Identifiers & Profiles.
  2. Under Certificates, create/download the Apple Distribution certificate (.cer) — and the Apple Development one too only if you're sending the optional development files.
  3. In Keychain Access, export each certificate as a .p12 (set a password and share it with us).
  4. Under Profiles, generate the App Store provisioning profiles for the app and the NSE (and the Development ones only if sending the optional development files), and download them.
  5. Send us all the files together with the .p12 passwords.

Push notifications (APNs)​

Push notifications need an APNs credential. There are two types:

  • APNs Auth Key (.p8) — token-based, one key for all your apps, does not expire. Preferred. If you already use this, you don't need to send anything extra for push.
  • APNs certificate (.p12) — certificate-based, one per app, expires every year like the signing certificates.
info

If your push notifications are set up with the .p12 certificate (not the .p8 key), please send us that push .p12 with its password too — and regenerate and resend it whenever it expires.

If anything is unclear, just let us know.