Open your website in a new browser profile.

• Use the latest version of Chrome or Firefox.
• Push does not work in incognito/private/guest modes.
• Check the supported browsers list.

Launch the Developer Console by pressing F12, right-click and selecting “Inspect”, or navigating to View > Developer > JavaScript Console.

Try subscribing to your site and check the Console for errors. Then match the error against the list below for guidance.

Desktop Debugging:

• Chrome: Right click on the page, click Inspect, and click the Console tab of the popup window that opens up.
• Firefox: Right click on the page, click Inspect element, and click the Console tab of the popup window that opens up.
• Safari: Go to Safari → Preferences → Advanced and make sure Show Develop menu in menu bar is checked. Then, on your webpage, right click, click Inspect element, and click the Console tab of the popup window that opens up.

Android Debugging:

• Chrome on Android: Enable USB Debugging, connect your device into your computer and access the Dev Tools with chrome://inspect#devices in your Desktop Chrome browser.
• Firefox on Android: Enable USB Debugging, connect your device into your computer and access the Dev Tools with about:debugging in your Desktop Firefox browser.

You should be able to run commands in the developer tools Console now.

Execute the following code:

OneSignal.Debug.setLogLevel('trace');

You should see undefined as the result.

If you see:

Then OneSignal is not active on your webpage, or you need to switch to the top frame context (see above screenshot).

Now that our web SDK’s debug logging is enabled, please close the tab and open a new tab to the same page (refreshing the page is not enough to trigger some of our SDK events). You should see a lot of output in the Console.

You can always disable this additional logging by entering this code:

OneSignal.Debug.setLogLevel('warn');

Run in the Console:

function getUserInfo() {
	console.log('getUserInfo()');
	Promise.all([
		OneSignal.Notifications.permission,
		OneSignal.User.PushSubscription.id,
		OneSignal.User.PushSubscription.token,
		OneSignal.User.PushSubscription.optedIn,
		OneSignal.context.serviceWorkerManager.getActiveState(),
	])
		.then(
			([
				isSubscribed,
				subscriptionId,
				pushToken,
        optedIn,
				serviceWorkerActive,
			]) => {
        console.log('What is the current URL of this page?', location.href);
         console.log(
					"Is a service worker registered and active? (should be false on Safari, otherwise should be 'OneSignal Worker')?",
					serviceWorkerActive
				);
        console.log('')
        console.log('Are you subscribed, in the browser?', isSubscribed)
        console.log('Are you opted-in, in OneSignal?' , optedIn);
				console.log('');
				console.log('What is your OneSignal Subscription ID?', subscriptionId);
				console.log('What is your Push Token?', pushToken);

			}
		)
		.catch(e => {
			console.error('Issue determining whether push is enabled:', e);
		});
}
getUserInfo();

Depending on whether you are subscribed, you should see similar to the below:

What is the current URL of this page? http://localhost:8080/
Is a service worker registered and active? (should be false on Safari, otherwise should be 'OneSignal Worker')? OneSignal Worker

Are you subscribed, in the browser? true
Are you opted-in, in OneSignal? true

What is your OneSignal Subscription ID? 22ff6b0d-60e1-469d-b667-005274204322
What is your Push Token? https://fcm.googleapis.com/fcm/send/drKvxiBc9Eo:APA91bFoa88bzkuudYFmuyNb8uIA60dI44SnBbXi0_4GAYa2Ln07XzrOs1-k5KVxrwKf8oVxBvzIXVN-44bamCRkaQ6cFODy7-8slGgnV3i2OqS3EgYrzU6VcO1KZaBHacsZhqvWqIRv

Only if you are subscribed (see above section), you can send yourself a test notification. See Find & Set Test Subscriptions for details.

• Make sure you aren’t blocking notifications at the operating system level.
• See Notifications Not Shown: Web Push.

• For step #3, are you subscribed? If not, stop here, completely clear your site data following these specific instructions, and then re-subscribe to your site in order to receive notifications. Run step #3 again after to verify you’re actually subscribed. When following the clear site data instructions, please do remember to close all tabs to your site or restart your browser, since Chrome prevents the site’s storage from being accessed until all existing tabs to your site are closed.
• For step #4, do you receive a test notification? If you do, you’re done!

If you’re subscribed but you did not receive a test notification, please visit your OneSignal dashboard Delivery Page to view if the test notifications you’ve sent yourself shows at the top.

If you’re subscribed, did not receive a test notification, but you see the message has been delivered (colored green), please open Chrome to chrome://gcm-internals.

Click the “Start Recording” button on the top left. Making sure you see “Connection State: CONNECTED”.

Leave this open and send yourself a push (follow step #4 above to send yourself a test notification).

You should see something in the “Receive Message Log” if you got it.

• If you don’t see a “Data msg received”, then your Chrome browser is not receiving the notification at all. Please let us know on support about this.
• If you see “Data msg received” but you still didn’t receive a notification, proceed to step #4.

Visit chrome://serviceworker-internals.

Search for Scope: https://your-site.com.

Click Inspect, or Start -> Inspect, like below. A Chrome Developer Tools popup will appear.

On the Chrome Developer Tools popup to our service worker, click the Console tab, and run OneSignalWorker.log.trace();. It should return undefined. Any messages from our service worker should now appear in this pop.

Switch back from the service worker’s Dev Tools popup to your main page’s Developer Tools console (the same one used in step 2).
Send yourself another test notification. If you still do not see the notification, review the console output for any new errors or messages.
To share this information with support:

• Right-click inside the Console.
• Select Save as … to export the log file.
• Attach this file and reach out to our chat support for further assistance.