Set up Web push notifications in your test environment

Web push notifications require a secure context. In practice that means one of two things:

• Production and staging: the site must be served over https:// with a certificate issued by a trusted Certificate Authority. Self-signed certificates are not trusted by browsers and will block service worker registration, and with it web push.
• Local development: http://localhost, http://127.0.0.1 and [::1] are treated as trustworthy origins by browsers, so service workers and web push work there over plain HTTP. You do not need a certificate to test on localhost.

Setting up a test environment

1. Serve your test page from http://localhost:<port>. A file:// path or a LAN address such as http://192.168.1.10 is not a secure context and will not work.
2. Place the Pushwoosh service worker file at the root of that origin so its scope covers the page, and initialise the Web SDK with your Application Code and Device API token.
3. If you must test on a hostname other than localhost, use a real HTTPS certificate (for example through a tunnelling service that terminates TLS for you) rather than a self-signed one.
4. Browsers remember the notification permission per origin. Reset it in the browser's site settings between test runs, otherwise a previously denied prompt will not reappear.
5. Safari on macOS and iOS requires the site to be added to the Home Screen / Dock for web push, which is worth reproducing in your test plan.

If you have any additional questions or concerns, please contact the Support team.