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
On button click we call OneSignal.User.PushSubscription.optIn(), after that the OneSignal.User.PushSubscriptionchange event is fired twice:
The first time current.id and current.token only have changed from undefined to null
Shortly after this the event is fired again, now both current.id and current.token have expected values
Since the first time the event is fired no actual changes were made, I expect this to be an error.
What browsers are you seeing the problem on?
Chrome (Chromium)
What operating system are you running?
W11
Steps to reproduce?
1. Clear site's data and permissions
2. Call `OneSignal.User.PushSubscription.optIn();`
What did you expect to happen?
I expected the event to only be fired once
Relevant log output
See screenshot attached
The text was updated successfully, but these errors were encountered:
lmeurs
changed the title
[Bug]: after PushSubscription _optIn_ the _change_ event is fired twice (160001)
[Bug]: after calling PushSubscription.optIn() the change event is fired twice (160001)
Aug 18, 2023
What happened?
On button click we call
OneSignal.User.PushSubscription.optIn()
, after that theOneSignal.User.PushSubscription
change event is fired twice:current.id
andcurrent.token
only have changed fromundefined
tonull
current.id
andcurrent.token
have expected valuesSince the first time the event is fired no actual changes were made, I expect this to be an error.
What browsers are you seeing the problem on?
Chrome (Chromium)
What operating system are you running?
W11
Steps to reproduce?
What did you expect to happen?
I expected the event to only be fired once
Relevant log output
The text was updated successfully, but these errors were encountered: