Open jpdelmundo opened 5 months ago
I also called OneSignal.setSubscription(true) manually in the web console after OneSignal.registerForPushNotifications(), and still the status is "Not Subscribed".
@jpdelmundo Thanks for reporting this issue. I confirmed this happens in v15 of the OneSignal SDK. I also tested in v16 and can confirm this is no longer an issue.
Can you update to v16 by following following the details in the release notes? https://github.com/OneSignal/OneSignal-Website-SDK/releases/tag/160000
@jkasten2 Thank you for your response and confirming this issue is a bug.
I confirmed this happens in v15 of the OneSignal SDK
If this is a confirmed bug, when will this be fixed on v15?
I also tested in v16 and can confirm this is no longer an issue.
We are not yet planning on upgrading to v16.
What happened?
Setup works initially the first time the user accepts/allows the browser notification setting. However, when I manually disable the browser notification and decided to re-enable it again after some time (a few minutes), and calling OneSignal.registerForPushNotifications() does not re-subscribe the player ID.
What browsers are you seeing the problem on?
Chrome (Chromium)
What operating system are you running?
Windows 11 Pro 23H2 22631.2861
Steps to reproduce?
What did you expect to happen?
I expected the player ID status to be subscribed (check mark under "Subscription Status")
Relevant log output
No response