Prompt
Push notifications are inconsistent across devices, what am I doing wrong?
Latest observation
Nov 3, 2026
OpenAI APIWeb search: off
Inconsistent push notifications across devices are usually caused by one of a few common issues rather than “push being flaky” in general. The most likely problems are:
-
Different notification permissions/settings
- Some devices may have notifications disabled at the OS level.
- Android: battery optimization, background restrictions, notification channels disabled.
- iOS: Focus modes, scheduled summary, low power mode, app notification settings.
-
Using the wrong push token
- Make sure you’re sending to the correct device token / FCM token / APNs token for each device.
- Tokens can rotate or become invalid after app reinstalls, OS updates, or account changes.
-
Environment mismatch
- iOS dev vs production APNs certs/tokens
- Sending from a staging backend to production tokens, or vice versa
- Using sandbox tokens with a production APNs endpoint
-
Payload differences
- Some devices need a valid notification payload, not just data payload.
- On iOS, silent/data-only pushes behave differently and may be delayed or dropped.
- Android may require a proper
notificationordataformat depending on app state.
-
Background processing limits
- Both iOS and Android limit background execution.
- Data-only pushes are not guaranteed to wake the app immediately.
- If your app does work after receiving the push, that work may be killed or deferred.
-
Collapse/priority settings
- Low-priority pushes can be delayed.
- Messages with the same collapse key may replace each other.
- Some services throttle “normal” priority notifications when the device is idle.
-
Bad device state
- Outdated app version
- Corrupted token registration
- Notification permissions not re-registered after reinstall
- Device offline or behind aggressive battery saver/network restrictions
-
Backend delivery issues
- Not checking provider responses from FCM/APNs
- Ignoring errors like invalid token, unregistered, expired token
- Not logging per-device delivery status
What to check first
- Confirm each device has the correct, fresh token.
- Check OS notification permissions on each device.
- Verify you’re using the right APNs/FCM environment.
- Inspect push provider responses for errors.
- Compare payloads between devices that receive notifications and those that don’t.
- Test with a simple, high-priority notification payload.
If you want the fastest path to diagnosis
Send me:
- platform(s): iOS, Android, or both
- push provider: FCM, APNs directly, OneSignal, Firebase, Expo, etc.
- a sample payload
- whether it fails on foreground, background, or terminated app states
- what “inconsistent” means: delayed, missing, duplicated, or only some devices
And I can help you narrow it down quickly.