Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages

Help for owners

My app's push notifications stopped arriving

Short answer

Push notifications fail for a few ordinary reasons: the user never allowed them or switched them off, the server sends to a stale device address, a key or certificate is wrong, or the app does not show messages while it is open. Check one test phone's settings first, then ask whoever runs the server.

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

Does this sound like your situation?

  • My customers say they no longer get alerts from the app.
  • Notifications work on my phone but not on a customer's, or only on iPhone, or only on Android.
  • They stopped after an app update or a server move.
  • The notification arrives only when the app is closed, never while it is open.
  • The tool that sends them says 'sent', yet nothing appears on the phone.

Why does this happen?

  1. The phone is not allowing notifications

    On Android 13 and higher, a newly installed app has notifications off until the user grants the notification permission. If a user taps Don't allow, the app cannot send notifications, which is the same as switching them off in system settings.

  2. The app does not handle a message while it is open

    Firebase documents that a notification message may not appear if the app has no logic to handle it while the app is in the foreground. On Android, the app's message handler is not called for notification messages when the app is in the background, because the system tray shows them instead.

  3. The server sends to a device address that no longer works

    Each install gets its own address (a token) that the server stores. Firebase documents one way it breaks: when an app is restored from a backup, the restored copy and the original share one installation ID, and only one token is kept, so using both removes the other's token.

  4. The server cannot reach the push service

    Firebase notes that a firewall can block outbound traffic to its messaging service, and that quota errors can occur when many messages are sent in a spike. A server move or a new firewall rule is a common time for this to start.

  5. A key or certificate was lost with the old developer

    iPhone alerts depend on a key or certificate tied to the Apple developer account, and Android alerts on the Firebase project. If the person who set these up left, or the account changed, the server may be using credentials that no longer belong to you.

What can I do about it today?

  1. Test with one phone you controlInstall the app on a phone you hold, allow notifications when asked, and send one test message. Note whether it is iPhone or Android and whether the app was open.
  2. Check the phone's own settingsIn the phone's settings, open the app and confirm notifications are switched on. A user who tapped Don't allow once will see nothing until they change it there.
  3. Write down when it stoppedNote the date and what changed around it: an app update, a server move, a new developer, a changed account. This one fact shortens the search.
  4. Find out who owns the sending setupAsk who holds the Firebase project and the Apple developer account. Do not delete, regenerate or replace any key to try your luck, because old keys can still be in use by apps already installed.
  5. Send me the facts, not your passwordsA screenshot of the test result, the app version and the date it stopped is enough to start. I never need a password.

When should I bring someone in?

  • A test phone with notifications allowed still receives nothing.
  • The problem began after a server move, a developer change or an app update.
  • Alerts carry orders, bookings or payments, and customers are missing them.

How do I handle it?

  1. Separate the phone from the serverI send a test to a known device to learn whether the message leaves the server, reaches the push service and arrives, and where it stops.
  2. Check the credentials and the projectI confirm which Firebase project and Apple account the app and the server really use, and whether those belong to your company.
  3. Fix the app or the server, not both blindlyPermission prompts, foreground handling and stored device tokens are fixed in the app. Keys, firewall rules and sending code are fixed on the server. I change one thing at a time.
  4. Prove it on real phonesA fix is finished when a test arrives on an iPhone and an Android phone, with the app open and closed.

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?

Why do notifications work for some customers only?

Because each phone has its own permission and its own device address. Users who denied the permission, or whose stored address is stale, are missed while others are served.

Can I just resend everything?

Not safely. Resending to old addresses will not reach anyone new, and a large burst can run into the push service's quota. Find the cause first.

Is it the app or the server?

A test to one known phone tells them apart. If the server logs a send but nothing arrives, the problem is between the two; if nothing is sent, it is the server.

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.