Push notifications not working? How to fix them on iOS and Android

A checklist for diagnosing missing push notifications, from permissions and tokens to certificates, server configuration, battery optimisation and notification channels.

By the UK Technology Hub teamPublished 4 minute read

The short answer

Push notifications usually fail because the user hasn't granted permission, the device token is missing or outdated, the server uses the wrong credentials or environment, the messaging service rejects requests, Android notification channels or battery optimisation suppress messages, or the payload is malformed. Check the device first, then the token, then server logs and provider responses, working along the delivery chain.

Push notifications travel through several systems: your server, Apple Push Notification service (APNs) or Firebase Cloud Messaging (FCM), the operating system and finally your app. A failure anywhere means silence. Work through the chain step by step.

Step 1: Check the device

  • Permissions: on iOS, check Settings for the app's notifications. On Android 13 and later, apps need the notification runtime permission.
  • Focus and Do Not Disturb modes may hide notifications.
  • Notification settings for the app may be set to deliver quietly or disabled for certain categories.
  • Battery optimisation on Android can delay or block background delivery, especially on some manufacturers' devices.
  • Network connection must be available.

Step 2: Check the device token

Each installation registers with APNs or FCM and receives a token, which your server uses to send notifications.

  • Confirm the app registers successfully and sends the token to your server.
  • Tokens can change after reinstalls, restores or periodically. Update them whenever the app receives a new one.
  • Remove tokens that providers report as invalid.

Step 3: Check server credentials and environment

iOS (APNs):

  • Use a valid authentication key or certificate. Certificates expire; authentication keys don't, but must be kept secure.
  • Match the environment: development builds use the sandbox environment, App Store and TestFlight builds use production.
  • Use the correct bundle identifier as the topic.

Android (FCM):

  • Use the current FCM HTTP v1 API with service account credentials. Google shut down the older legacy FCM APIs in 2024, so servers still using them need migrating.
  • Make sure the app's Firebase configuration matches the project used by the server.

Step 4: Read the provider response

APNs and FCM return responses for each request. Errors often state the problem directly, such as invalid tokens, wrong topics, authentication failures or payload issues. Log these responses on your server.

Step 5: Check the payload

  • Payloads must be valid and within size limits.
  • iOS needs the right alert fields and, for background notifications, the content-available flag and appropriate priority.
  • Android notification messages and data messages behave differently, especially when the app is in the background.

Step 6: Check Android notification channels

On Android 8 and later, notifications must use a notification channel. If the channel doesn't exist or the user disabled it, notifications won't appear.

Step 7: Check app behaviour in different states

Test with the app in the foreground, background and closed. Apps often need code to display notifications while in the foreground, which can make it seem like nothing arrived.

Step 8: Check for app crashes

If the app crashes when handling notifications, they may appear to fail. Crash reports help; see our guide to fixing iOS crashes on launch for how to read them.

Testing tools

  • Send test notifications from Firebase console or APNs testing tools.
  • Use logging on the device during development.
  • Test on several devices and OS versions, including manufacturers with aggressive battery management.

Prevention

  • Monitor delivery and error rates.
  • Rotate and store credentials securely, with reminders before any expiry.
  • Clean up invalid tokens automatically.
  • Include notification tests in release checklists.

Strategy matters too

Delivery is only half the story. Users who receive irrelevant notifications disable them. Our push notification strategy guide covers sending messages people value.

Web push notifications

Websites and progressive web apps can send push notifications too, with their own permission prompts and service worker requirements. If web push isn't working, check browser permissions, service worker registration, push subscription storage and server credentials. Safari on iPhone supports web push for home-screen web apps, so test that path separately.

Keeping a delivery log

Log every notification sent, its target, the provider's response and any errors. When users report missing notifications, the log quickly shows whether the problem is on your side, with the provider or on the device.

Reinstall as a last resort

Asking users to reinstall can refresh tokens, but it's disruptive. Fix server-side and app-side causes first.

How we help

Our mobile app development team diagnoses and fixes notification delivery on iOS and Android. Our web app developers build reliable notification servers with logging and token management, and our app development service includes notification testing in every release.

Frequently asked questions

Why do push notifications work in development but not production on iOS?

Often because the server uses the sandbox environment or wrong credentials for production builds.

Why are Android notifications delayed?

Battery optimisation and manufacturer power-saving features can delay background delivery.

Do I need to migrate from legacy FCM APIs?

Yes. Google shut down the legacy FCM APIs, so servers must use the FCM HTTP v1 API.

This guide is general information, not legal, tax or financial advice, and details such as prices, features and rules can change. Product and company names mentioned are trademarks of their respective owners and are used only to identify those products; UK Technology Hub is not affiliated with or endorsed by them.

Related guides

How to fix the WordPress white screen of death

A calm, step-by-step guide to diagnosing and fixing a blank white WordPress page, from recovery mode and debug logs to plugins, themes and memory limits.

All bug fixes & troubleshooting guides