<aside> ☝

OneSignal's AI Chatbot is extremely helpful. While the official documentation often contains outdated or incorrect information, the chatbot consistently provides accurate and reliable solutions. I recommend consulting it rather than relying solely on the official documentation.

</aside>

References

• The official documentation is inadequate. Following their guides didn't work for me on the first attempt!
• Dashboard
• Developer Guide
• Server SDK Reference
• Package @onesignal/node-onesignal
• Local Testing
• Users, OneSignal ID, External ID
• Aliases

Remarks

• Ensure the integrated file OneSignalSDKWorker.js is accessible via http://localhost:<port>/<subfolder>/OneSignalSDKWorker.js

  importScripts('<https://cdn.onesignal.com/sdks/web/v16/OneSignalSDK.sw.js>');
  

  Note that you will only see the above file content (importScripts….). Only the service worker can fetch and load the content of OneSignalSDK.sw.js.

• After modifying anything on the OneSignal Dashboard or in your code, clear your browser's cache, reset notification permissions, and reload the page.

• Be aware of caching issues when changing the location of OneSignalSDKWorker.js. The service may continue working due to browser caching even after relocating the file. To verify it's truly working, perform a hard refresh, wait a bit, or test with a fresh browser/profile.

• Should use Soft Prompt (display an explanation before asking for the notification permission from the browser) ← Soft prompts are recommended by browsers and help maximize opt-in rates while protecting your domain reputation.

Very simple sample

• With just a HTML file.
• Sample Github repository

With Angular (or Web SDK)

• Angular Web SDK setup (Though incomplete, it provides useful information)