You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Although I registered OneSignal different scope than PWA service worker, It's causing issues. In the devtools service workers tab this can be observed that OneSignal service worker is stopped accordingly the notifications are not delivered.
What browsers are you seeing the problem on?
Chrome (Chromium)
What operating system are you running?
Windows 11
Steps to reproduce?
Node version: 18.16.0
Angular version: 16.1.0
NPM version: 9.5.1
onesignal-ngx version: 2.0.1
I created a repo to reproduce the issue. https://github.com/ertugrulbakidal/AngularWithOneSignal- Change the OneSignal app id
- Install dependencies
- run ng build
- npm install --global http-server
- npx http-server -p 4200 -c-1 .\dist\angular-pwa-with-one-signal\
What did you expect to happen?
The OneSignal notifications should be delivered while using Angular PWA
Relevant log output
No response
The text was updated successfully, but these errors were encountered:
@ertugrulbakidal Thanks for reporting. I believe there is a race condition bug in the OneSignal-Website-SDK where it can sometimes pick up the wrong Service Worker when registering for push. This is something we are looking into.
What happened?
Although I registered OneSignal different scope than PWA service worker, It's causing issues. In the devtools service workers tab this can be observed that OneSignal service worker is stopped accordingly the notifications are not delivered.
What browsers are you seeing the problem on?
Chrome (Chromium)
What operating system are you running?
Windows 11
Steps to reproduce?
What did you expect to happen?
The OneSignal notifications should be delivered while using Angular PWA
Relevant log output
No response
The text was updated successfully, but these errors were encountered: