Silence from APNs

Push Notifications Stopped Working on iOS: Expired APNs Certificates, Stale Tokens and the First Hour

The appointment reminders went out at 8:00, the way they have every morning for two years. Nobody received one. No crash, no error on any phone, no angry email yet. Just a quiet morning, and a calendar full of people who forgot to come.

November 19, 2026 · 9 min read

acmedentalcare.com · reminder pushes, Tuesday 8:00
Appointment reminders, from server to phone
The server sent them; Apple turned them away
Sample
Reminders queued by the scheduler640
Sent to APNs640(100%)
Accepted by APNs0(0%)
Delivered to phones0
Opened0

provider certificate expired Monday night

Illustrative: sample push funnel for a fictional dental office's patient app

The short answer

When iOS push notifications stop, check how your server authenticates to Apple Push Notification service (APNs). Apple says certificate-based provider certificates are valid for a year, and once one expires you can no longer send pushes. Token-based connections fail with ExpiredProviderToken (403) when the token is more than an hour old. Read your server's APNs response first, then renew or refresh what failed.

On this page
  1. The outage nobody reports, because nobody notices it
  2. Two ways your server talks to Apple, and how each one fails
  3. Sixty minutes, starting in the server log
  4. When the provider certificate ran out
  5. When the token is stale or the key was revoked
  6. Failures that look like Apple's fault and are not
  7. Fixing it in-house, or handing it to someone who reads APNs errors

The outage nobody reports, because nobody notices it

A crashing app announces itself. A silent one does not. When push notifications fail, the app opens fine, every screen works and your developer's test phone looks normal because nobody thought to send it a push. The first sign is usually a business number: fewer bookings confirmed, more no-shows, carts that stayed abandoned. By the time someone connects the dots, the problem may be days old.

This page is the first hour for an iPhone app whose notifications stopped arriving. It belongs to DataCram's emergency repair section. If the whole app is misbehaving, start at iOS app crashing. If the app has deeper, older problems, our fixing broken mobile apps service is the longer conversation. Here the job is narrow: find out why Apple stopped delivering your messages, and get them flowing again.

The good news is that push failures have a short list of causes, and most of them leave a written trace on your server. The bad news is that the trace is usually in a log nobody reads, written by a job nobody remembers setting up.

Two ways your server talks to Apple, and how each one fails

Your server does not send notifications to phones. It sends them to Apple Push Notification service, and Apple delivers them. To be allowed through, your server must prove who it is, in one of two ways. Which one your app uses decides almost everything that follows, and many owners have never been told.

Certificate-based and token-based APNs connections, per Apple's developer documentation as of November 2026
Certificate-basedToken-based
What Apple issuesA provider certificate for one appA signing key as a .p8 text file plus a 10-character Key ID
How many appsApple says you "must create separate certificates for each app"Apple says one token can serve "all or a subset of your company's apps"
What expiresThe certificate: Apple says provider certificates "are valid for a year," as of November 2026The token your server builds from the key, which Apple says must be refreshed at least once every 60 minutes, as of November 2026
Typical failurePushes stop on the day the certificate expiresAPNs rejects pushes with ExpiredProviderToken (403) when the token is more than an hour old
The usual root causeNobody renewed itThe server stopped refreshing tokens, or the key was revoked
Small glowing cyan pulses traveling along a thin line across a deep blue and violet grid, stopping at a dark gap in the middle
Push delivery tends to fall off a cliff on one day, and it comes back as soon as the credential is fixed.

Sources: Apple's guides to a certificate-based connection and a token-based connection, both read in November 2026. Apple describes the token method as "a stateless way to communicate with APNs." The one-year line applies to APNs provider certificates. It is not a statement about other Apple certificates, a distinction our expired Apple certificates page keeps careful.

Sixty minutes, starting in the server log

  1. 1

    Confirm it with one phone

    Send a test push to a device you control, with notifications allowed in its settings. If it arrives, the problem may be narrower than it looks: one audience, one feature, one job.

  2. 2

    Find the sender

    Identify what actually sends your pushes: your own server code, a scheduled job, or an outside push service. Write down where its logs live.

  3. 3

    Read Apple's answer

    Find the response APNs returned for the failed sends. An expired-token error, a certificate failure and a bad device token each point to a different fix.

  4. 4

    Identify the credential type

    Is there a .p8 key and a Key ID in your server settings, or a certificate file? Ask the developer, or check the server configuration.

  5. 5

    Check the dates

    For a certificate, find its expiration date in your Apple developer account. For a token, check that the server is still creating fresh ones on schedule.

  6. 6

    Fix the credential, then resend carefully

    Renew the certificate or restore token refresh. Resend only messages that still make sense; a reminder for an appointment that already passed is worse than none.

The order matters. Owners often start by reinstalling the app or rebuilding it, which changes nothing about a credential that lives on the server. The phone is rarely the problem. Apple's answer to your server almost always says what is.

When the provider certificate ran out

Apple's certificates overview, read in November 2026, states the consequence plainly: with an expired or revoked Apple Push Notification service certificate, "You can no longer send push notifications to your app." No grace period is described. The certificate-based guide adds the instruction your team skipped last year: "update your provider certificates before they expire."

Renewal is a job for someone with the right role in the Apple developer account, a new certificate loaded onto the server that sends pushes, and a test. It is not hard. It is just held hostage by access. If the only person who can sign in is unavailable, the fix waits on them, and that is the conversation our developer disappeared page prepares you for.

That 2025 change is the kind of thing an old server misses. Read the Apple news post if your pushes stopped around February 24, 2025 and nobody has touched the server since. It is also a fair argument for moving to token-based authentication when the crisis is over: one key, no yearly certificate for each app.

When the token is stale or the key was revoked

Token-based authentication has its own trap, and it is a clock. Apple's token guide says: "Refresh your token no more than once every 20 minutes and no less than once every 60 minutes." It also says that if the token's issued-at time "is more than one hour old, APNs rejects any notifications containing the token, returning an ExpiredProviderToken (403) error." Those windows are Apple's, as of November 2026.

So a token setup can break without anything expiring in your Apple account. The server process that refreshes tokens crashed. A clock on the server drifted. Someone copied a token into a configuration file by hand instead of generating it. Each of those produces the same 403. For the meaning of 403 itself, MDN's status code reference explains that unlike a 401, "the client's identity is known to the server": Apple knows who you are and is still saying no.

  • Find where the .p8 key file lives and who can reach it. If it sits on a former contractor's laptop, that is the real emergency.
  • Confirm the Key ID and team details in the server configuration match the key in your Apple developer account.
  • Check the refresh logic is running and producing a new token inside Apple's window.
  • If the key may have leaked, follow Apple's instruction: "revoke it and request a new one," then deploy the new key before turning sends back on.

Credential problems on servers are the same family as broken API keys anywhere. Our API integration broken page covers the wider pattern, and connections like this are restored the same day once we have access in hand.

Failures that look like Apple's fault and are not

The scheduled job stopped

The code that decides who gets a reminder never ran. APNs cannot deliver a message it never received. Check the scheduler before the certificate.

Sandbox and production crossed

Apple runs separate sandbox and production environments. A server pointed at the wrong one, or a test build's device tokens used against production, fails quietly.

A capability changed in the app

Apple's provisioning help says that if you enable or disable app services, you need to regenerate the provisioning profile. A build shipped with the push capability missing cannot receive.

Old device tokens

Devices that reinstalled the app or changed hands may carry tokens your database still holds. Those sends fail one by one, not all at once.

The user turned them off

If only some customers say they get nothing, check whether they allowed notifications. That is a product question, not an outage.

A login or account change

If pushes are tied to signed-in accounts and sign-in broke, the push list goes stale. See app login broken.

These are patterns from practice, and the server's response from APNs is what separates them. A blanket failure starting on one day points to a credential. A slow fade points to tokens and audiences. Apple's provisioning profile help, read in November 2026, is the source for the capability point.

Fixing it in-house, or handing it to someone who reads APNs errors

You can probably handle it when

  • The certificate simply expired and your Admin can renew it today
  • The server logs name the error clearly
  • Your developer knows where the key or certificate is installed
  • A test push arrives once the credential is replaced

Bring us in when

  • Nobody knows which server sends the pushes
  • The key or certificate lives with someone who is gone
  • The credential is fine and pushes still fail
  • Login, accounts and notifications broke at the same time

DataCram responds the same business day, during the hours on our contact page. The emergency app repair offer lists the access we need: an Apple developer account role, the server that sends pushes, and the app's source. A push repair is billed like any mobile emergency: from $575, depending on complexity, and nothing starts until you have a written estimate. Emergency pricing explains what moves the number.

Once pushes flow again, the follow-up is boring and worth it: move to token-based authentication if you are still on yearly certificates, keep the key in a place the business controls, and put any remaining expiration dates in a shared calendar. Our iOS app development team handles that work, and API integrations covers the server side. DataCram is based in San Antonio, Texas and has been building for the web since 1999. The projects we can show are in our portfolio, and the phone number is (210) 346-0848.

Questions owners ask in an emergency

Most often a credential failed. If your server uses a certificate, it may have expired; Apple says that with an expired APNs certificate you can no longer send push notifications. If it uses a token, the server may have stopped refreshing it. Your server's log of APNs responses usually names the cause.

Apple's certificate-based connection guide says provider certificates are valid for a year, as of November 2026, and that you must update them before they expire to keep communicating with APNs. That statement is about APNs provider certificates, not other Apple certificates.

Apple says APNs returns ExpiredProviderToken (403) when the token's issued-at time is more than one hour old. Apple asks servers to refresh tokens no more than once every 20 minutes and no less than once every 60 minutes, as of November 2026. Check that your refresh job is running.

Often, once the emergency is over. Apple says one token can send notifications for all or a subset of your company's apps, while certificates must be created separately for each app. That removes a yearly expiration for each app, though the signing key still needs safekeeping.

Usually not. Certificates, keys and tokens live on your server, so most push repairs happen there and need no App Review. A new build is needed when the app itself lost the push capability or mishandles device tokens.

Emergency mobile work starts from $575, depending on complexity, with a written estimate before work starts. We respond the same business day. A simple certificate renewal costs less to fix than a push system nobody can find.

Keep reading

Free · No obligation

Get your notifications delivering again

Tell us when pushes stopped and what sends them, if you know. Someone at DataCram replies the same business day with what to check first and a written estimate.

Which of these sounds like you? (pick any)

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

CallGet a quote