Lorixen.
EN

iOS build failing? Fix an expired certificate or profile

Short answer: If your iOS app suddenly won't build, install on test phones or upload to App Store Connect, an expired or revoked signing certificate or provisioning profile is the usual cause. Apple's guidance is reassuring on one point: if your developer membership is valid, apps already on the App Store keep working when a distribution certificate expires. What stops is uploading new builds signed with it. Create a new certificate, regenerate the profiles that use it, rebuild, and set reminders or automated signing so it doesn't catch you out again.

The pieces involved

iOS code signing has a few moving parts that small teams only touch once a year, which is why expiry is so often a surprise:

  • Certificates prove who signed the app. Apple's support page explains that development certificates are used to run your app on devices and enable capabilities during testing, while distribution certificates are used to distribute your app or upload it to App Store Connect. Development certificates belong to individuals, labelled with their computer's name.
  • Provisioning profiles tie together an app ID, a certificate and, for testing, a list of devices. A build needs a valid profile that matches its certificate.
  • The developer account membership itself, which must be active for anything to work.

Certificates and profiles have expiry dates. When either lapses, or when someone revokes a certificate, builds that depend on it fail.

What breaks and what doesn't

Apple's certificate support page sets out the effects by certificate type. For an iOS distribution certificate used for the App Store:

  • Existing apps on the App Store aren't affected, as long as your membership is valid.
  • You can no longer upload new apps or updates signed with the expired or revoked certificate.
  • Builds already uploaded but not yet submitted for review may be marked as an invalid binary if they were signed with a revoked certificate.

The picture is different for in-house enterprise apps: Apple states that users can no longer run apps signed with an expired or revoked in-house distribution certificate, so a new version must be signed and distributed. Push notification certificates have their own consequence: you can no longer send push notifications through that certificate.

For development and ad hoc builds, testers typically find the app won't install or won't open once its profile has expired.

Typical symptoms

  • Xcode reports that no valid signing identity or matching profile was found.
  • The CI pipeline fails at the signing or export step after months of working.
  • Testers report a test build that "won't open any more".
  • Uploading to App Store Connect is rejected with a signing error.

Fixing it step by step

  1. Check what expired. In your developer account, review certificates and profiles and their expiry dates. In Xcode, the account settings show signing certificates for your team.
  2. Create a new certificate of the right type, using Xcode or your developer account. If the old one was revoked because a private key leaked, make sure nobody keeps using the old key.
  3. Regenerate or edit the provisioning profiles that used the old certificate, so they include the new one. Download them, or let Xcode fetch them.
  4. Update CI. Build servers usually hold their own copy of the certificate and private key, often as an encrypted secret. Replace both, along with any stored profiles.
  5. Rebuild and upload a fresh build. Don't try to re-sign an old build manually unless you know the process well.
  6. Redistribute test builds to testers if their installed version has stopped working.

Preventing the next surprise

  • Calendar reminders. Note the expiry dates of distribution certificates and key profiles, with a reminder a month ahead.
  • Automatic signing in Xcode handles development certificates and profiles for individual developers with little effort.
  • Shared signing for teams and CI. Tools such as fastlane's match create the required certificates and profiles and store them in a separate encrypted store, such as a private Git repository or cloud bucket, so every team member and build server uses the same identity. That avoids the common situation where each developer creates their own distribution certificate and the team hits the limit or loses track.
  • Keep the private key safe. A certificate is useless without its private key. Store it in your password manager or secrets store, not on one developer's laptop.
  • Own the account. Make sure the developer account belongs to the business, with more than one admin, so renewals don't depend on a single person or a former agency.

When an agency built the app

Many small businesses have an app built by an agency or freelancer who managed signing on their own machine. When the certificate expires and the agency has moved on, nobody knows where the keys are. If that's you:

  • Confirm the app is in your company's developer account, not the agency's.
  • Create new certificates under your account; you don't need the old private key to issue a new certificate.
  • Ask for the project's signing configuration and CI secrets as part of any handover.

A worked example

Take a hypothetical Belfast physiotherapy clinic with an exercise-programme app built by a freelancer two years earlier. When they needed an urgent update, the build failed: the distribution certificate had expired, and the freelancer's laptop held the only private key. The app itself stayed available in the App Store throughout. A new developer created a fresh distribution certificate in the clinic's own account, regenerated the App Store profile, stored the key and profiles in an encrypted shared store for CI, and uploaded the update the same day. A calendar reminder now sits a month before the next expiry.

FAQ

Will my app disappear from the App Store when the certificate expires?

According to Apple, not if your developer membership is valid. You just can't upload updates signed with the expired certificate.

Do I need the old certificate's private key?

No, to issue a new certificate. You only lose the ability to sign with the old one.

Why do testers' builds stop working?

Development and ad hoc builds depend on provisioning profiles that expire. Send them a new build.

Is automatic signing enough for CI?

Sometimes. Many teams prefer a shared, stored identity for CI so builds don't depend on a logged-in Xcode account.

If your app's signing setup is a mystery and an update is due, tell us what's failing and we'll help untangle it.

Sources

WhatsAppBook a call