Prompt
Why are my push notifications not sending from Firebase?
Latest observation
There are a few common reasons Firebase push notifications don’t send. The exact fix depends on where it’s failing: token generation, backend send, device receipt, or app display.
Most common causes
1) FCM token is missing or invalid
If your app never gets a valid device token, Firebase can’t deliver anything.
Check:
- App requests notification permission
- Firebase config is correct
- You’re retrieving the token successfully
- Token is being saved to your backend correctly
2) Wrong Firebase project / credentials
If your server is using credentials from a different Firebase project than the app:
- sends may fail
- tokens may be rejected
- messages may go nowhere
Check:
- Same Firebase project in app and server
- Correct service account / API key / server key
- Correct package name / bundle ID
3) Notification permissions not granted
On iOS and Android 13+, users must explicitly allow notifications.
Check:
- iOS permission prompt was shown and accepted
- Android 13+
POST_NOTIFICATIONSpermission is granted - App isn’t blocked in system settings
4) App is receiving messages, but not displaying them
Sometimes FCM is working, but notifications aren’t visible because:
- you’re sending data-only messages and not handling them in the app
- the app is in foreground and you’re not showing a local notification
- Android notification channel isn’t created / has low importance
5) Incorrect payload format
Firebase expects different payloads depending on platform.
Common issues:
notificationvsdatafields used incorrectly- wrong
priority - malformed JSON
- invalid
totoken - sending to a topic the device never subscribed to
6) Expired or refreshed tokens not updated
Tokens can change. If your backend stores old tokens:
- messages may fail
- sends may appear random
Check:
- handle token refresh
- update backend when token changes
- remove invalid tokens from your database
7) Sender is failing silently
Your backend might be returning an error but not logging it.
Check the send response:
InvalidRegistrationNotRegisteredMismatchSenderIdUnauthorizedQuotaExceeded
8) Network / OS restrictions
- Battery optimization
- Doze mode
- Background restrictions
- VPN/firewall issues
- OEM restrictions on Android devices
Quick debugging checklist
- Confirm the app gets a valid FCM token.
- Send a test notification from Firebase Console to that token.
- Check whether the app receives it in foreground/background.
- Inspect server response for FCM errors.
- Verify Firebase project, credentials, and package/bundle IDs.
- Make sure notification permission is granted.
- Confirm Android notification channel setup.
- Update stale tokens.
If you want, I can help you debug it step by step
Send me:
- your platform: Android / iOS / Web
- whether you use Firebase Console or your own server
- the payload you send
- any error message or server response
- the code where you get the FCM token and send the notification
If you share those, I can pinpoint the likely cause.