Why this happens
Apple distribution certificates (Apple Distribution and legacy iOS Distribution) are valid for one year from the day they are issued. When you receive an expiration warning email from Apple, your natural instinct is to look for a Renew button in the Apple Developer portal—but none exists. Apple’s public key infrastructure treats every certificate as immutable: you never extend an existing certificate’s expiration date; you replace it with a freshly generated certificate and private key.
The biggest concern most developers have is whether an expiring or revoked certificate will break apps currently on the App Store. Your live App Store apps will not be taken down or stop working. When Apple approves and distributes your app on the App Store, Apple re-signs the binary with its own certificate. Your distribution certificate is only used to prove your team’s identity during archive signing and upload to App Store Connect.
Once your distribution certificate expires (or if you click Revoke), two things happen:
- Expired certificates automatically disappear from
Certificates, Identifiers & Profiles, and any manual provisioning profiles linked to that certificate change status toInvalid. - You can no longer archive, sign, or upload new builds using those profiles until they point to a valid certificate. (Note: if you also distribute Ad Hoc builds directly to registered test devices outside the App Store, those Ad Hoc installs will stop launching once their signing certificate expires or is revoked.)
How to fix it
1. Create a new Apple Distribution certificate in Xcode (Automatic Signing)
If your project uses Automatically manage signing in Xcode, replacing an expiring certificate takes only a minute and usually does not require visiting the browser portal first.
Apple permits multiple active distribution certificates per developer team up to an account limit. If you have an open slot, create the new certificate before the old one expires rather than revoking the old one first. Overlapping them avoids breaking teammates’ builds or CI/CD pipelines mid-release.
- Open Xcode and go to
Xcode > Settings > Accounts(orXcode > Preferences > Accountsin older Xcode versions). - Select your Apple ID on the left, choose your Team on the right, and click
Manage Certificates.... - Click the
+button in the bottom-left corner and chooseApple Distribution. - Xcode generates a new private key in your Mac’s login keychain, requests the certificate from Apple, and downloads it automatically.
- Open your project’s target settings under
Signing & Capabilities. WithAutomatically manage signingenabled, Xcode will automatically regenerate its Xcode-managed provisioning profiles when you next archive for distribution.
If Apple Distribution is greyed out with a message stating you have reached the maximum number of certificates, proceed to Step 2 to revoke the expiring certificate in the Apple Developer portal first, then try again.
2. Replace the certificate manually via Keychain Access and the Developer Portal
If you manage code signing manually or maintain certificates for a shared CI/CD server, generate the Certificate Signing Request (CSR) on your Mac so you retain complete control over the private key.
- Open Keychain Access on your Mac.
- From the menu bar, choose
Keychain Access > Certificate Assistant > Request a Certificate From a Certificate Authority.... - Enter your email address and a clear Common Name (for example,
Team Distribution Nov 2026), leaveCA Email Addressblank, selectSaved to disk, and clickContinueto save the.certSigningRequestfile. - Sign in to the Apple Developer portal and open
Certificates, Identifiers & Profiles > Certificates. - Check whether you can click the
+button to create a newApple Distributioncertificate right away:
– If you have an available slot: Create the new certificate immediately without revoking the expiring one.
– If you have hit the certificate limit: Click the expiring distribution certificate, verify its expiration date so you don’t revoke a newer certificate used by another pipeline, and clickRevoke. (Alternatively, if the certificate expires today, wait until it expires and disappears on its own.) - Click
+, selectApple Distribution(oriOS Distribution (App Store and Ad Hoc)only if supporting older tooling that strictly requires it), clickContinue, and upload your.certSigningRequestfile. - Download the resulting
.cerfile and double-click it to install it into Keychain Access, where it will pair automatically with the private key you generated in step 3.
3. Re-save invalid App Store provisioning profiles
Whenever a distribution certificate expires or is revoked, every manual App Store and Ad Hoc provisioning profile that referenced it turns Invalid in the Apple Developer portal. You do not need to delete and recreate those profiles from scratch—you only need to associate them with the new certificate.
- In the Apple Developer portal, go to
Certificates, Identifiers & Profiles > Profiles. - Locate each distribution profile marked
Invalid(or expiring on the same date as your old certificate). - Click the profile name, then click
Edit. - Under
Certificates, select the radio button next to your newly created distribution certificate (verify its new expiration date). - Click
Save, then clickDownload. - Double-click each downloaded
.mobileprovisionfile to install it for Xcode, or re-import the profile in your project’sSigning & Capabilitiestab.
4. Remove expired or revoked certificates from Keychain Access
Leaving a revoked or expired distribution certificate in your local keychain alongside a new certificate for the same team can confuse codesign and custom archive scripts, sometimes triggering ambiguous signing identity errors.
Check which signing identities macOS currently sees on your machine by running this command in Terminal:
security find-identity -v -p codesigning
If you see a certificate flagged with (CSSMERR_TP_CERT_REVOKED) or (CSSMERR_TP_CERT_EXPIRED), or two Apple Distribution entries for the same team where one is about to expire:
- Open Keychain Access, select the
loginkeychain on the left, and open theMy Certificatestab. - Inspect the
Expirescolumn (or double-click each certificate) to confirm which one is the old or revoked certificate. - Right-click only the expired or revoked certificate and choose
Delete. - Re-run
security find-identity -v -p codesigningto confirm that only your validApple Distributionidentity remains.
If teammates or CI/CD runners share this distribution certificate, right-click the new valid Apple Distribution entry in My Certificates, choose Export..., save it as a .p12 Personal Information Exchange file protected with a strong password, and update your CI secrets.
How to prevent it
- Overlap certificates before expiration: Create your replacement distribution certificate two to three weeks before the old one expires (assuming you have an available certificate slot), update CI/CD secrets and provisioning profiles at your own pace, and let the old certificate expire naturally.
- Back up the
.p12bundle immediately: Export the new certificate and its private key to your team’s password manager right after creation so you never have to revoke a working certificate just because someone got a new Mac. - Use App Store Connect API keys on CI/CD: Passing an App Store Connect API key with
-allowProvisioningUpdatestoxcodebuild(or using Xcode Cloud) reduces manual.mobileprovisiondownloads when certificates rotate. - Plan separately for Ad Hoc builds: Remember that while App Store apps are unaffected by certificate expiration, Ad Hoc test builds installed on QA devices will stop opening once their signing certificate expires—re-sign and redistribute active Ad Hoc builds ahead of time.
FAQ
Will revoking or expiring my distribution certificate remove live apps from the App Store?
No. Apps already published on the App Store are re-signed by Apple and continue to download, launch, and function normally for all users regardless of whether your distribution certificate expires or is revoked.
Why is there no Renew button in Apple Developer Certificates, Identifiers & Profiles?
Cryptographic code-signing certificates have fixed validity dates baked into their signed structure and cannot be extended in place. Apple always requires generating a new certificate and linking your provisioning profiles to that replacement.
Should I revoke the expiring certificate now or wait for it to expire?
If your developer account allows creating another Apple Distribution certificate right now, create the new one first without revoking the old one so existing workflows keep working during the transition. Only revoke the expiring certificate early if you have reached Apple’s certificate limit and need to free up a slot immediately.
Parts of this guide are adapted from content licensed under CC BY-SA 3.0; this article is shared under the same license.
