Help for owners
My iPhone app's signing certificate expired and I cannot release updates
Short answer
When an iOS Distribution certificate for the App Store expires or is revoked, Apple says apps already on the store are unaffected while your membership is valid, but you cannot upload new apps or updates signed with it. You need a new certificate, and the private key that goes with it, on the machine that builds.
Does this sound like your situation?
- My developer says the certificate expired and he cannot upload a new version.
- Xcode or the build service reports a missing or invalid signing certificate.
- Someone revoked a certificate and now builds fail.
- The person who created the certificate left, and nobody has the file.
- Customers can still use the app, but I cannot ship a fix.
Why does this happen?
Certificates have an end date
A distribution certificate does not last forever. Apple's documentation lists what expiry or revocation means for each type, and for the iOS Distribution certificate used for the App Store it says you cannot upload new apps or updates signed with it.
Confirmed by developer.apple.com
Your live app keeps working
For the same certificate, Apple states that existing App Store apps are unaffected as long as your membership is valid. The problem is the next release, not the one customers already have. The membership itself is a separate matter, covered on the renewal page.
Confirmed by developer.apple.com
Revocation can be done by people, or by Apple
Developers can create and revoke certificates in Xcode or in the developer account, and Apple says it can revoke a certificate at any time at its sole discretion. Builds not yet submitted that were signed with a revoked certificate may be marked Invalid Binary.
Confirmed by developer.apple.comTechnical detail: Xcode shows a distribution certificate without its private key
The private key lives on one computer
A certificate is only useful with its private key, which is created on the Mac that requested it. If that Mac is gone, a new certificate has to be made, even when the old one has not expired.
Technical detail: Xcode shows a distribution certificate without its private key
Enterprise certificates behave differently
For an iOS Distribution certificate used for in-house distribution, Apple says users can no longer run apps signed with it once it is gone, and a new version signed with a new certificate must be distributed. That is more urgent than the App Store case.
Confirmed by developer.apple.com
What can I do about it today?
- Do not panic about the live appIf your app is on the App Store and your Apple membership is active, customers can keep using what is published. Say so to your team.
- Check the membership is activeAsk the Account Holder to sign in to the Apple developer account and confirm that the membership is current and no agreement is waiting to be accepted.
- Find out who owns the accountOnly the right roles can create certificates. Ask who the Account Holder and the Admins are, and make sure your developer has a named role, not the owner's password.
- Never revoke anything to see what happensRevoking a certificate that something still uses can break other builds. Leave it until the developer has checked what depends on it.
- Tell the developer which release is waitingSay what must ship and by when, so the certificate work is planned with the release and not after it.
When should I bring someone in?
- The certificate was made by someone who has left and no one has the private key.
- Your app is distributed in-house to staff and has stopped opening.
- Builds fail with a signing error and your developer cannot say which certificate is wrong.
How do I handle it?
- Read what the account hasI list the certificates, identifiers and profiles in the account, with dates and what each belongs to, before anything is changed.
- Create the new certificate on a managed machineThe certificate and its private key are created where the build runs, and the key is backed up in a place your company controls.
- Regenerate what depends on itProvisioning profiles that referenced the old certificate are regenerated against the new one, then the build is signed again.
- Prove it with a real uploadThe check is a build that uploads to App Store Connect and processes without a signing error. I write the steps down so the next renewal is routine.
The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.
What do owners ask about this?
Will customers lose the app?
Apple says that for the App Store distribution certificate, existing apps are unaffected when the membership is valid. In-house apps are the exception and stop running for users.
Do I need to give my developer my Apple password?
No. You can invite them to the account with a role. I do not need anyone's password.
How often does this need doing?
Apple's page does not give a lifetime for this certificate, so check the expiry date in your developer account and put it in a calendar.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.
For your developer: the technical fixes
Missing private keyXcode shows a distribution certificate without its private keyProvisioning profile doesn't include signing certificateXcode says the profile does not include your signing certificateXcode couldn't find any provisioning profiles matchingXcode finds no provisioning profile for your bundle ID