Signing, expired

Apple Distribution Certificate or Provisioning Profile Expired: What Stops, What Keeps Running, and Who Can Renew

Xcode refuses to upload the build and the word in red is "expired." Before anyone revokes anything, take a breath: for most App Store apps, Apple says the apps already in the store keep working. What stopped is your ability to ship the next one.

November 19, 2026 · 9 min read

acmefieldcrew.com · Apple signing inventory
Everything in the developer account with a date on it
One certificate expired, two more coming due
Sample
In-house distribution certificateExpired Nov 14, staff app locked
Provisioning profile, Crew SchedulerInvalid until regenerated
APNs provider certificateExpires in 9 days
Developer program membershipCurrent, renews Mar 2
Account HolderFormer office manager
Admins on the teamNone
First jobGet an Admin role on the account
Illustrative: sample signing inventory for a fictional field service crew's apps

The short answer

If your iOS Distribution Certificate expired, Apple says existing App Store apps are not affected as long as your developer program membership is valid, but you cannot upload new apps or updates signed with it. In-house enterprise apps are different: users can no longer run apps signed with an expired certificate. Only the Account Holder or Admin role can create distribution certificates, so find that person first.

On this page
  1. Which certificate expired decides how bad today is
  2. What each expiry stops, in Apple's words
  3. The first hour, beginning with who holds the keys
  4. The Apple account belongs in the company's name
  5. Renewing without breaking the next build
  6. Enterprise apps: where staff get locked out
  7. Renew it yourself or call for help

Which certificate expired decides how bad today is

Apple uses the word certificate for several different things, and they fail in very different ways. One expired certificate means your public app is fine and your next update is stuck. Another means every employee using your in-house app was locked out this morning. A third means notifications went silent. The first job is finding out which one you have, because the fix and the urgency follow from that.

This page covers the signing emergency: a certificate or provisioning profile expired or was revoked, and something stopped. It is part of DataCram's emergency repair section. If your app is crashing on launch with no crash report, read iOS app crashing alongside this one, since signature failures do not show in Xcode's Crashes organizer. The broader work of keeping an app healthy belongs to our fixing broken mobile apps service.

A word on what you will not find here. No Apple page we read says how long a distribution certificate lasts, so we do not say. If a forum post gives you a number, treat it as rumor and read the expiration date in your own developer account, which is the only date that matters for your app.

What each expiry stops, in Apple's words

Apple's certificates overview, read in November 2026, explains the two everyday types: "Use development certificates to run your app on Apple devices and enable app capabilities during testing, and distribution certificates to distribute your app or upload it to App Store Connect." The same page then says what happens when each kind expires or is revoked.

Layered colored-paper scene of a blank phone outline with a paper padlock, a small paper key and a bandage across one corner, soft shadows
An expired certificate locks the door to the next release, while the app already in the store keeps working.
What expires and what it stops, per Apple's account help pages as of November 2026
What expired or was revokedWhat Apple says happensHow urgent
iOS Distribution Certificate (App Store)With a valid membership, "your existing apps on the App Store won't be affected," but you cannot upload new apps or updates signed with itUrgent only if you need to ship a build
In-house (enterprise) distribution certificate"Users will no longer be able to run apps that have been signed with this certificate"Urgent now: staff are locked out
Apple Push Notification service certificate"You can no longer send push notifications to your app"Urgent if the business runs on notifications
A certificate inside a provisioning profile, revoked"Provisioning profiles that contain a revoked certificate become invalid"Urgent before the next build
A provisioning profile, expiredApple says you need to regenerate the provisioning profileUrgent before the next build
The developer program membershipApps stop being available for download; installed copies still workUrgent: see the removal page

The profile lines come from Apple's pages on revoking a certificate and on editing, downloading or deleting profiles. A lapsed membership is its own emergency, covered on app removed from the App Store. Push certificates get the full treatment on push notifications stopped.

The first hour, beginning with who holds the keys

  1. 1

    Name what expired

    Read the exact error in Xcode, App Store Connect, the device or your push server. Match it to a row in the table above before doing anything else.

  2. 2

    Find out who can sign in

    Identify the Account Holder and every Admin on your Apple developer team. Apple says only those two roles can create distribution certificates.

  3. 3

    Do not revoke as a reflex

    Revoking a certificate invalidates the profiles that contain it. An expired certificate needs replacing, which is a calmer job than revoking one that still works.

  4. 4

    Check the membership date

    While you are in the account, confirm the membership itself is current. A lapsed membership changes the whole picture.

  5. 5

    Create, regenerate, rebuild

    With the right role, create the new certificate, regenerate the provisioning profiles that need it, and rebuild the app signed with both.

  6. 6

    Test the thing that broke

    Upload the build, run the in-house app on a staff phone, or send a test push. The fix is not done until the original failure is gone.

Every step after the second depends on access. That is why the second step is the real emergency in most businesses. The technical part of renewing a certificate is short. Finding someone who can sign in, with a working second factor, can take the rest of the day.

The Apple account belongs in the company's name

Apple is clear about ownership. The certificates overview says "Distribution certificates belong to the team" and "Only the Account Holder or Admin role can create distribution certificates." The team is the business. The Account Holder should be someone the business can reach on a bad day, signed in with an email address the business controls.

The certificate always expires on the one day the only person with the Apple login is on a cruise.

We say that with a straight face because it describes how these mornings go. The developer who set up the account years ago used a personal email. The phone number for the second factor belongs to someone who left. The renewal reminder went to an inbox that forwards nowhere. None of it is malicious, and all of it turns a short task into a hunt.

General advice, drawn from how cloud providers recommend handling account recovery: keep account ownership, recovery email and phone numbers on addresses the business controls, not on a single contractor's personal accounts. Add a second Admin. If the person who holds your account has vanished, our developer disappeared page lists what to gather before you ask Apple or anyone else for help.

Renewing without breaking the next build

Apple also offers certificates it manages for you. Its cloud-managed certificates page, read in November 2026, says: "A new cloud-managed certificate is automatically created 90 days before expiration when new signing requests are received." It adds that manual rotation opens "once the certificate has less than half of its validity duration left (often 180 days)." Those windows are Apple's, as of November 2026.

Apple also notes that "Apple can revoke digital certificates at any time at its sole discretion," and that the intermediate Worldwide Developer Relations certificate in use since January 28, 2021 "expires on February 20, 2030." Put that date in the same shared calendar as your own expirations. It is years away, which is exactly how dates like it get forgotten.

  • Keep one shared calendar with every certificate, profile, push credential and membership date, owned by the business.
  • Renew inside the window Apple opens, not on the expiration morning.
  • Regenerate provisioning profiles when you enable or disable an app service, as Apple's profile help requires.
  • Store signing files and keys where the business controls them, with a note on what each one is for.

Enterprise apps: where staff get locked out

In-house apps distributed through Apple's Enterprise Program are the sharp edge of this topic. Apple's line on an expired or revoked in-house distribution certificate is short and severe: users can no longer run the apps signed with it. For a field service crew, a warehouse or a clinic running on an internal app, that is a stopped business, not a delayed update.

Apple's membership renewal page, read in November 2026, adds a separate rule for the program itself. When an Enterprise Program membership lapses, Apple gives already-downloaded software a 90-day window to keep running, as of November 2026, but only while its certificates and profiles remain valid. The two rules work together. A lapsed membership leaves a window; an expired certificate does not.

Today

Create the new in-house certificate, regenerate profiles, rebuild, and get the new build onto staff devices through whatever channel you use.

This week

Confirm every internal app was re-signed, not just the one people complained about first.

This quarter

Decide whether the app should stay in-house or move to a web app your staff open in a browser, which our web app development team builds.

Renew it yourself or call for help

Do it in-house when

  • An Account Holder or Admin can sign in today
  • Only an App Store distribution certificate expired
  • Your developer can rebuild and upload the app
  • The membership itself is current

Call us when

  • Staff cannot open your in-house app
  • Nobody on staff can sign in to the Apple account
  • Someone revoked certificates and builds now fail
  • Signing, push and membership all look wrong at once

Our reply comes the same business day, inside the hours posted on the contact page. We sign in to your Apple developer account, never one of ours, using a role your Account Holder grants, and the emergency app repair page lists everything else we ask for. Certificate emergencies are priced like other mobile repairs: from $575, depending on complexity, and you see a written estimate before anyone starts. The emergency pricing page shows what raises or lowers it.

After the emergency, our iOS app development team can take over signing and releases so the calendar lives with someone who reads it. DataCram has been building for the web since 1999 from San Antonio, Texas. Browse published projects, or phone (210) 346-0848 and ask for the signing calendar conversation.

Questions owners ask in an emergency

Apple says that if your developer program membership is valid, existing apps on the App Store won't be affected. You will no longer be able to upload new apps or updates signed with the expired or revoked certificate to App Store Connect. Create a new certificate and rebuild.

We do not state a length, because no Apple page we read gives one for distribution certificates. Check the expiration date shown in your own developer account. The one-year figure Apple publishes applies to APNs provider certificates.

Apple says users can no longer run apps signed with an expired or revoked in-house distribution certificate. Someone with the Account Holder or Admin role must create a new certificate, regenerate the provisioning profiles and re-sign the app, then get the new build onto staff devices.

Apple says only the Account Holder or Admin role can create distribution certificates, and that distribution certificates belong to the team. If nobody at your business holds either role, finding or restoring that access is the first job.

Apple says provisioning profiles that contain a revoked certificate become invalid. Apple also says that if you enable or disable app services, or if a profile expires, you need to regenerate the provisioning profile before building again.

DataCram's emergency mobile work starts from $575, depending on complexity, with a written estimate before work starts. Apple's own developer program fee, 99 USD per membership year as of November 2026, is separate and paid to Apple.

Keep reading

Free · No obligation

Get your signing sorted out today

Tell us what expired, what stopped and who can sign in to your Apple account. We answer the same business day with the safe order of work and a written estimate.

Which of these sounds like you? (pick any)

Rather talk now? Call (210) 346-0848.

CallGet a quote