Prompt

my push notifications are not sending what should I check

Technology / API Platforms1 observationLast seen Oct 14, 2026

Latest observation

Oct 14, 2026OpenAI APIWeb search: off

If push notifications aren’t sending, here’s a practical checklist to go through:

1) Confirm the basics

  • Is the user/device subscribed to notifications?
  • Is the app getting a valid push token / device token?
  • Are notifications enabled in the OS settings for the app?

2) Check your push provider

Depending on what you use:

  • FCM (Firebase Cloud Messaging): verify server key/service account, project ID, and token validity
  • APNs (Apple Push Notification service): check certificate/key, bundle ID, team ID, and environment (sandbox vs production)
  • Third-party services (OneSignal, Expo, Pusher, etc.): verify API key, app config, and delivery logs

3) Validate the payload

  • Make sure the payload matches the provider’s required format
  • Ensure required fields exist:
    • title/body or alert content
    • correct target token/topic/condition
  • Check for invalid characters, oversized payloads, or malformed JSON

4) Verify environment mismatch

A very common issue:

  • Sending production push to a sandbox token, or vice versa
  • Using the wrong app bundle/package name
  • Testing on a simulator that doesn’t support remote push properly

5) Inspect server logs and response codes

Look for:

  • Auth errors
  • Invalid token errors
  • Rate limits / quota exceeded
  • Expired credentials
  • “accepted” by provider but not delivered errors

6) Check token freshness

  • Tokens can expire or rotate
  • Remove and replace old/invalid tokens in your database
  • Re-register on app launch if needed

7) Notification permissions and device state

  • User may have denied permission
  • Focus / Do Not Disturb / battery optimization may suppress delivery or display
  • On Android, notification channels may be disabled
  • On iOS, provisional/critical/scheduled delivery settings may affect visibility

8) App-side handling

  • If you’re sending silent/background pushes, verify background modes and proper headers
  • If the app is in foreground, notifications may arrive but not display unless you handle them
  • Check if your app is intercepting and suppressing display

9) Delivery diagnostics

  • Use your provider’s dashboard or test tools
  • Send a push to a known-good device/token
  • Compare a working payload vs failing one

10) Recent changes

Ask yourself:

  • Did you recently rotate keys/certificates?
  • Change bundle ID/package name?
  • Update app permissions?
  • Modify backend push code?

If you want, tell me:

  • iOS or Android
  • which push service you’re using (FCM/APNs/OneSignal/etc.)
  • whether you get any error message or logs

…and I can help you narrow it down fast.

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.