In this article we give some tips for troubleshooting, in case the image of a web push notification is not displayed.
Articles about web push notifications
This tutorial can be useful for development if you want to test web push notifications on your domain using Pushpad. You will see how to create a demo page where a user can subscribe to notifications and send a notification with custom options to himself.
A list of all the official documentation provided by the push services about the HTTP status codes and errors that can be returned. When an application sends a notification to a browser push service, it should check the status code returned and take appropriate actions.
The scope of a service worker defines when it is active and usually depends on the path where it is located. However in this tutorial we'll see some directives that allow to change the default scope of a service worker, regardless of its location.
If you subscribe to the notifications of some websites, you may sometimes see a strange notification with this content: "This site has been updated in the background". What does that mean? And if you are the website owner, how can you prevent that notification?
What can you do if you receive that notifications? What does it mean? How can you fix it?
When you send a web push notification to a browser push service, you may get an HTTP status code that represents an error.
This article describes a simple and effective method for debugging web push notifications on a specific browser using Pushpad.
Subscribing users to web push notifications on your website is not enough: you also need to manage and renew their push subscriptions properly over time, otherwise you will lose subscribers.
Why some web push notifications are not delivered to the browser? Why some notifications are not displayed to the user?
Are you stuck with an old version of the service worker or your imported scripts are not being updated as you expect? This guide shows you how to ensure that your service worker and the imported scripts are updated in a timely manner.
This article investigates one of the reasons that negatively impact delivery rates for web push. First it shows that web push subscriptions can last many years without expiring, then it proves a negative correlation between the age of a web push subscription and its expected delivery rate.
If you have problems with web push or with other service worker based technologies on Firefox, then you probably want to use the Firefox developer tools for debugging.
Many issues related to web push notifications can be solved by simply resetting the browser permission. That removes the old browser subscription and creates a new subscription.
If you currently use a service different from Pushpad and you want to migrate your existing web push subscribers to Pushpad you can follow these steps:
In the last months we have rolled out new notification features and other performance improvements.
If you work with the Push API or service workers in general you know that debugging can be a pain. Fortunately Chrome has two hidden gems that can save you many headaches.
If you are struggling with the error above, but all your icons of the push package are of the correct size, you have probably set the **wrong DPI**.
These days we have investigated an issue related to Safari.
Pushpad is a service for web push notifications. In order to add push notifications to their websites, **our customers need to install the service worker that we provide on their websites**.