Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages

Help for owners

My iPhone notifications stopped after someone revoked an Apple key

Short answer

Apple's key-based push sending signs each request with a key from your developer account, and Apple says a suspected compromised key should be revoked and replaced. Anything still using the old key stops. Find out who revoked it and when, then have the new key and its ID installed on the sending server.

  • Written for business owners
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Does this sound like your situation?

  • iPhone notifications stopped on the day somebody tidied up the Apple account.
  • Android notifications still arrive.
  • My developer says the key was revoked and nobody knows by whom.
  • Sending logs show authentication errors from Apple.
  • A new key was downloaded but nothing changed.

Why does this happen?

  1. The old key no longer signs valid requests

    Apple says requests carry a token signed with your key and that you revoke a key you suspect is compromised and request a new one. Anything still signing with the revoked key stops working.

  2. The new key is not on the server

    Apple gives you a key file and a 10-character key identifier. Both are needed, and the server must use the new pair. Downloading a key does not install it.

  3. Keys have a limit

    Apple states each environment can have a maximum of two team-scoped keys. A tidy-up of the account can be the reason someone revoked one.

  4. Test and live use different keys

    Apple recommends separate keys for the sandbox and production environments. Revoking one can break only the test setup or only real customers, depending on which.

  5. Firebase holds its own copy

    If notifications go through Firebase, the key and its ID are uploaded to the Firebase console, and at least one is required. Revoking the key in Apple does not update that copy.

What can I do about it today?

  1. Find out who revoked it and whyAsk your Apple account administrator. If it was revoked for a security reason, say so to your developer.
  2. Do not revoke more keysAnother revocation can make it worse. Wait for a single, planned replacement.
  3. Keep the key file safeApple says the key must remain private. Send it only to the person who installs it, never in a chat group.
  4. Ask your developer where the key is usedIt can be on your server, inside Firebase, or in a third-party messaging tool. Each place has its own copy.
  5. Test with one phoneAfter the change, send one test notification to a real iPhone before sending anything to customers.

When should I bring someone in?

  • A security problem is the reason the key was revoked.
  • Nobody knows where the key is used.
  • Notifications go through several tools and you cannot tell which one is failing.

How do I handle it?

  1. Find every place the key is usedI check the server, the Firebase project and any messaging tool, because each keeps its own copy.
  2. Create the replacement with the account ownerThe key is created in your Apple account. I never need your password.
  3. Install key and ID togetherThe new key and its identifier go into each place, and the old values are removed.
  4. Test both environmentsI test a test build and a live build separately, since they use different keys.
  5. Write the handover noteThe note lists where the key lives, who owns it and what to do if it must be revoked again.

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?

Is a revoked key a security incident?

Not necessarily. Apple says a suspected compromised key should be revoked, but keys are also revoked in routine tidying. Ask who did it and why.

Do customers need to update the app?

The key is used by the sender, not the app, so a replacement normally does not need a new release. Your developer can confirm.

How often does a key need renewing?

The Apple page I read gives no expiry for the key. It does say tokens built from it must be refreshed at least once an hour, which the server does itself.

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

Next step

Want this off your desk?

Send me a few lines on where things stand. I reply within 24 hours.