Notifications Not Shown

When a notification shows as "Delivered" in OneSignal, it means we have successfully sent the notification to the FCM/APNS/WNS servers which then distribute the notifications to your subscribers.

The following are reasons why notifications may show as "Delivered" on the OneSignal dashboard or API, but are not visible on your device or website.

Common Issues for All Platforms

Network issues - No Internet

Devices must be online to receive push notifications. If your device is turned off, in airplane mode, has unstable or no internet connection, the push will not show until a proper connection is made. You can set the timeframe Google and Apple Servers will wait for a connection with the Time To Live (TTL) Parameter (the default is 3 days).

Also check the network / WiFi you're connected as it may have closed your connection to Apple or Google servers'. Try disabling and re-enabling your internet connection. See our Notifications delayed troubleshooting guide for more details details.

Not Subscribed

Make sure your device is still subscribed to push notifications. You can find your player id with this guide to make sure your device is still subscribed.

Not Targeted In the Push

1. Check the segment you sent the push to and make sure it is setup correctly. This is under Segments. Sometimes an incorrect filter is added to the segment removing certain devices.

2. Check the Player ID record in the Audience > All Users section of the dashboard. Under the "Segments" column, you will see if that user is in the segment targeted for push.

---

Mobile App Notifications Not Showing

If your device is subscribed and has a working network connection, try adding your device as a Test User. Make sure you are using the latest version of the OneSignal SDK and have the app running in the background when you test the push.

The app is currently In Focus

Please check the value you added in you init for In-Focus Displaying.

If you set this to None or 0 then no notification will show while the app is open. There are other options you can set this to if you want to show notifications while the app is open.

The app has push permissions Disabled

Android,iOS: In your Device Settings > Notifications > Your App, you can turn on and off push notifications.

Make sure push permissions are enabled for your device:

Do Not Disturb Mode

If Do Not Disturb is enabled, this prevents the notifications from "popping up" on the screen but still shows in the "Notification Center".

iOS: Disable within in Settings > Do Not Disturb.

Android: Disable within in Settings > Notifications > Do Not Disturb. Or search for "Do not Disturb" in Settings and disable.

Low Power, Energy Saving

Some devices have a specific battery optimization that will stop or decrease rate of notifications showing.

Android: In Settings, search for:

• Power Saving Mode or Energy Saving - If "Power Saving Mode" and/or "Limit apps and Home Screen" is enabled, this will limit all background activity (push notifications) from being received.
• Adaptive power saving mode - If enabled, device will automatically turn on/off "Power Saving Mode" based on your usage patterns.
• or Battery Optimization or Background usage limits - Battery optimized apps will have background functions (like push notifications) restricted. Make sure your app is Not Optimized.

iOS: If the device has Low Power Mode enabled and has low power, it will reduce the rate at which notifications can be received. Check if enabled in Settings > Battery > Low Power Mode.

---

Android Mobile App Notifications Not Showing

The App is Force Stopped

When an app is in a Force Stopped / Force Killed state most events including FCM messages for push notifications will not be received. An app can be placed in this state in the following ways.

• From Settings > Apps, "Force Stop" is pressed.
• Long pressing the back button on some devices.
• Using a 3rd party task killer like Greenify.
• Swiping away your app while remote debugging it. (Not the same as viewing the logcat but launching your app as a remote debug process.)
• Automatically on some devices due to custom Android tweaks done by manufactures. This is a known issue affecting all push providers (not just OneSignal). We have written a blog post about this and provide more details and discussion in this Github Issue.

Based on your device manufacturer, you can follow these steps to enable push for your device. For your app users, if you want to help educate them on this issue, you can send these specific devices In-App Messaging to enable proper settings.

More information on problematic devices can be found in our blog post: Notifications are highly reliable, except when device manufacturers interfere

Checking your app state

1. Run the following to check the current state of your app.
Replace "com.company.appname" with your package name.

adb shell dumpsys package com.company.appname | grep stopped

If you see stopped=false if everything is fine, otherwise you will see stopped=true then your app was force killed in some way.

2. Another way is to send a few notifications and check for the following GCM logcat entry.

W/GCM-DMM: broadcast intent callback: result=CANCELLED forIntent {
   act=com.google.android.c2dm.intent.RECEIVE pkg=com.onesignal.example (has extras)
}

If you seen this cancelled intent above then your app could not be started to process the notification.

Some device manufactures will white list apps from going into the force closed state. Example such as Gmail and Whatsapp.

Additional Debugging

FCM provides a REST API to query the last time a device has been connected to FCM. See the following Google documentation on how to get this.
https://developers.google.com/instance-id/reference/server#get_information_about_app_instances

---

iOS Mobile App Notifications Not Showing

The most common reason is an outdated version of the OneSignal SDK in the app. Make sure you updated to the latest version of the OneSignal SDK in your app. You should have minimum version 2.10.1.

Xcode 11 change

If you are using Xcode 11, make sure you are using the latest version of the OneSignal SDK (minimum version 2.10.1). You can open your All Users page and check the SDK VERSION column to see what version you are on. Xcode 11 made a breaking change that affects push token registration. More details here: https://onesignal.com/blog/ios-13-introduces-4-breaking-changes-to-notifications/

---

Web Push Notifications Not Showing

Notifications are blocked in Settings

This is the most common reason. Check your browser settings on desktop or app settings on mobile:

Windows Notification Settings

Turn off Focus Assist: https://support.microsoft.com/en-us/windows/turn-focus-assist-on-or-off-in-windows-10-5492a638-b5a3-1ee0-0c4f-5ae044450e09

Check Settings > Notifications & Actions > Turn on Get notifications from apps and other senders. Make sure your site and browser are also enabled. More details in this article: https://www.digitaltrends.com/computing/how-to-configure-notifications-action-center-windows-10/2/

macOS Notification Settings

In the System Preferences > Notifications > Chrome or browser of choice, make sure "Allow Notifications" is turned on.

In System Preferences > Notifications > Do Not Disturb, make sure this is mode is not turned on. More details: https://www.imore.com/how-use-do-not-disturb-mac

macOS also has temporary Do Not Disturb notification settings in the top right menu > scroll up.

Android Notification Settings

Check in your Settings > Application Manager > Chrome (or browser of choice). Make sure "Show notifications" is checked like this: https://i.imgur.com/LY810Mj.png on Firefox it will be the same: https://i.imgur.com/a3lB88b.png

Service Worker or PWA

If you have another service worker or PWA on the site, this can cause issues with the OneSignal Service Worker required for push notifications.

Please see our Service Worker guide on integrating multiple service workers

Browser is Closed

Some browsers will not receive push if it is not running. More details in our Browser Behavior Guide.

Clearing Browser Data

Clearing your browser cookies, data, and/or history will cause the browser to not get notifications any longer and will need to revisit the site to re-subscribe.

Browser App Data Full

If your mobile browser app has reached its data limit or its data is full, you will need to clear the data on the app.

If your mobile browser app has many unread push notifications and/or many tabs open, this can cause notifications to now show.

Unsupported Browser

Users must subscribe to notifications on their desktop or mobile device to receive notifications and it must be a browser that supports push notifications. Please see Supported Web Platforms.

Full Screen

Full screen mode in some older browser versions prevent web push notifications from appearing. Make sure no windows are in full screen mode. Please see Web Push Troubleshooting Docs for more.

Debugging Web Push Notifications

• Check that you are not blocking Notifications at the Operating System level, see: Notifications Blocked In Your Settings.
• Open Chrome and go to your website page with the OneSignal code.
• Do not use Incognito mode or Guest Browser mode.
• Do not have any other tabs or windows open to your site.
• Mobile Device Debugging:
  • iOS (iPhone/iPad does not support web push)
  • Use Android, plugin your android device into your desktop with a USB cable and open this link on Chrome on Desktop: chrome://inspect/#devices then follow the below instructions using your mobile device.

1. Reset Browser Permissions

Follow these steps to reset browser permission to access site like a first time user.

1. Click the lock next to your URL
2. Next to Notification, select "Ask (default)"
3. Click Cookies

4. Select your site
5. Click Remove
6. Click Done

7. Reload the page

You have successfully reset your browser data for your site and visiting it like a first time user.

2. Subscribe to your site

Follow the steps you normally take to get prompted for push and subscribe to your site.

3. Find your Player ID and send yourself a Push Notification

1. Using Chrome, go to your site url with the OneSignal code. Open the JavaScript debugging console in one of the following ways:

• press F12, or
• right click the site and press "Inspect", or
• in the Chrome Menu select View > Developer > JavaScript Console

2. Open the Console
3. Use this code to get your new OneSignal Player ID:

OneSignal.getUserId(function(id){console.log(id)});

If you do not get a Player ID, make sure you followed the steps and are subscribed to your site.

4. If you have a player id, use this code to send yourself a push notification:
   OneSignal.sendSelfNotification();

5. If you do not get the notification, contact OneSignal Support using the intercom button in the bottom right and provide your new player id and site URL with the OneSignal code you are testing on.

If you did get the notification, copy paste your player id to set yourself as a Test User.