Skip to main content
All CollectionsPWA Questions
I can't receive push notifications
I can't receive push notifications

Troubleshooting tips and common reasons for issues with push notifications

Kevin Basset avatar
Written by Kevin Basset
Updated over a week ago

1. Check your device settings

Frequently, your device may receive notifications as intended, but they may not be displayed due to settings specific to your device. To access the relevant guide, please click on your device type below:

πŸ‘‰ iPhone/iPad

πŸ‘‰ Windows

πŸ‘‰ macOS

πŸ‘‰ Android

2. Ensure there is a recipient

Another common reason for notifications not being received is that you are sending it to a particular email... but there is no user with that email in your device list. Alternatively, they might be on the list but haven't enabled push notifications.

To check if a user with a particular email has notifications enabled, click on this button to open the device list:

See the example below:

  • is on the list but hasn't enabled push notifications. They can't receive your notifications

  • is on the list and has enabled push notifications. They can receive your notifications

  • is not on the list at all. They can't receive notifications.

To ensure users are on the list, make sure they allow notifications by following the instructions below. Also, ensure to connect your user data (with Bubble or with any other platform) so that emails are synced with push subscriptions.

3. Check the logs

Progressier keeps track of all your push notification requests (failed or successful) in the Push Notifications section.

  • A 201 response means your request was successful

  • A 200 response means your request was successful but that there were no active devices matching your targeting criteria

  • A 202 response means your request was successful and has been scheduled for later

  • A 403 response means your request was denied, e.g. if your subscription is unpaid

  • A 400 response means your request was invalid

  • A 500 response means that there was something wrong with the Progressier server.

4. Disable/Re-enable notifications

Ensure that you're using a compatible device and that you've indeed allowed notifications. In most browsers, you can verify this by clicking on the padlock icon in the URL bar. Try disabling and re-enabling notifications.

5. Ensure notifications were not auto-blocked

However, some browsers may also auto-block notifications if you usually block them on other sites. In that case, you won't see an option to block or allow notifications when clicking on the padlock icon. But you'll see a variation of this icon. Click on it to manually allow notifications.

6. Make sure there are no leftover service worker registrations

If you've previously installed another service worker on your domain (via another push service like OneSignal for example), it may still be registered and interfere with the delivery of your push notifications.

Open the Developer Console, go to Application > Service Workers, and Unregister every service worker. Also doesn't hurt to completely clear your domain's cache. Then refresh the page.

Did this answer your question?