[Bug]: In v5, the Subscription Status does not change to 'Subscribed'. #1706
Comments
|
Having a similar issue here which seems to happen often when you reinstall an app (iOS). I can reproduce the steps easily via:
Not sure if this is by design and didn't find a work around. |
|
Just to add something to this mystery, when you call One thing which seems to work to enable push notifications again, is to first call |
|
Another interesting result. I'm now getting an error when sending a notification however the notification is received. I hope this info helps. In my admin panel, I see that one subscription has changed to "Not Subscribed" suddenly and a new entry appeared which is subscribed. I did not reinstall the app. |
|
In conversation with support, the guidance was to use In App Message, even if I don't want to. Requesting permission using native prompt will make OneSignal unaware of the change in permission, therefore, it will not trigger the change of subscription status in the panel. This is frustrating. |
|
Thanks! Isn't there a way to force a subscription? I thought using |
|
Solved! I contacted onesignal support and they told me that OneSignal will not be able to know about the change in permission status if requested natively or via a third-party prompt. The only way for OneSignal to update the subscription is to request it with OneSignal.Notifications.requestPermission() or using In App Message. |
What happened?
In v5, even if permission is granted on the OS notification permission dialog, the Subscription Status does not change to 'Subscribed.' I'm not using "In App Message", instead I'm using a custom Modal that invokes a native prompt.
Original issue 1947 OneSignal-Android-SDK
Steps to reproduce?
What did you expect to happen?
At the moment when permission is granted on the OS notification permission dialog, the Subscription Status changes to 'Subscribed.'
React Native OneSignal SDK version
5.1.3
Which platform(s) are affected?
Relevant log output
Code of Conduct
The text was updated successfully, but these errors were encountered: