"Delivered" notifications in OneSignal means we have successfully sent the notification to the push servers (FCM/APNS/WNS etc..). These push servers then distribute the notifications to your subscribers. The "Confirmed" stat means our SDK received the notification which should have been shown on the device. See Confirmed Deliveries for more details.

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

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).

Wifi-connection, Firewall or VPN

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. Also try without wifi using cellular data.

If you are restricting traffic to or from the Internet, you need to configure it to allow connectivity with FCM which requires open ports to: 5228, 5229, and 5230. More details: https://firebase.google.com/docs/cloud-messaging/concept-options

APNS devices must connect to: TCP port 5223 & TCP port 443 or 2197. More details: https://support.apple.com/en-us/HT203609

If you check the logs from the app, you may also see:

ERROR: Encountered error during push registration with OneSignal: 
Error Domain=OneSignalError Code=0 "(null)" UserInfo={error=Error Domain=NSURLErrorDomain Code=-1004 
"Could not connect to the server." 
UserInfo={NSUnderlyingError=0x2834051a0 {Error Domain=kCFErrorDomainCFNetwork Code=-1004 "(null)" 
UserInfo={_kCFStreamErrorCodeKey=61, _kCFStreamErrorDomainKey=1}}, NSErrorFailingURLStringKey=https://api.onesignal.com/players, NSErrorFailingURLKey=https://api.onesignal.com/players, _kCFStreamErrorDomainKey=1, _kCFStreamErrorCodeKey=61, 
NSLocalizedDescription=Could not connect to the server.}}

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 Subscription 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.

App Push Permissions Disabled - Device Not Subscribed

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:

Android Categories Disabled

Android Settings App > Notifications > Your App you should see "Show notifications" enable and all categories underneath enabled. If you have a category disabled, you will not get notifications from that category.

In this example, the "Abandoned Cart - Urgent" Category is turned off. If I set this category in the notification, the device will not get this notification.

If no category is set, OneSignal uses a default "Miscellaneous" category. Make sure that is enabled if not setting categories. See Android Notification Categories for more details.

The app is currently In Focus

Keep the app running, but put it in the background/out of focus when testing.

If your app is open while sending, you may be hiding the notification using the Foreground Notification Received Event if on our updated Major release SDK or In-Focus Displaying is set to None or 0 if on an older version of OneSignal SDK.

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.

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.

Android 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

Firebase Conflicts

Please check your Android Manifest file and double-check that the following line is not interfering nor blocking your notifications.

com.google.firebase.iid.FirebaseInstanceIdReceiver

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). Navigate to your dashboard Audience > Subscriptions 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/