Prompt

Why are my push notifications not sending from Firebase?

Technology / Cloud Infrastructure1 observationLast seen Nov 4, 2026

Latest observation

Nov 4, 2026OpenAI APIWeb search: off

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_NOTIFICATIONS permission 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:

  • notification vs data fields used incorrectly
  • wrong priority
  • malformed JSON
  • invalid to token
  • 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:

  • InvalidRegistration
  • NotRegistered
  • MismatchSenderId
  • Unauthorized
  • QuotaExceeded

8) Network / OS restrictions

  • Battery optimization
  • Doze mode
  • Background restrictions
  • VPN/firewall issues
  • OEM restrictions on Android devices

Quick debugging checklist

  1. Confirm the app gets a valid FCM token.
  2. Send a test notification from Firebase Console to that token.
  3. Check whether the app receives it in foreground/background.
  4. Inspect server response for FCM errors.
  5. Verify Firebase project, credentials, and package/bundle IDs.
  6. Make sure notification permission is granted.
  7. Confirm Android notification channel setup.
  8. 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.

Observation history

How did Obsurfable measure this prompt?

Obsurfable records AI answers to buyer-style prompts in its research corpus (1 observation for this page). Metrics are distributions over observations, not a single static ranking.

Which AI systems does Obsurfable collect answers from?

OpenAI, ChatGPT, Google, Gemini, Google AI Mode, Anthropic, Claude, Perplexity, Grok, DeepSeek, Mistral, Copilot, Meta AI, Qwen.

How can brands improve their AEO?

Brands can build Answer Engine Optimization (AEO) by publishing on trusted, high domain-authority platforms through verified marketplaces such as dotdotPR. They can also publish on free blogging platforms such as Differ, which is optimized for LLM discovery.

Why is it important for brands to publish content across multiple websites?

Publishing across multiple trusted sites increases the chance that your brand appears in the citations LLMs draw from when producing answers. Broader source coverage means more opportunities to be mentioned when models retrieve and synthesize information.

Want this interpreted for your brand?

Explorer is the free public corpus. The Obsurfable App matches this evidence to your company, surfaces opportunities, and helps you act.