We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
For a decent chunk of our users (about 4%), a push notification subscription is not being created.
The response from OneSignal.initialize is the following for these users:
OneSignal.initialize
{ "notificationPermission": true, "pushSubscriptionState": { "id": "", "optedIn": true, "token": "ftjo7cue........." }, "result": "success" }
As you can see, the subscription id is empty.
I can't reproduce this myself, but from Sentry I can see that this is the response for these users.
I expect the SDK to create a valid subscription.
5.0.3
No response
The text was updated successfully, but these errors were encountered:
Then it's probably an issue on your side,
Are you really sure 100% that you set your id properly and that there is no risk that you login an empty id to one signal ?
Sorry, something went wrong.
Hi @nachos5, there is no response from OneSignal.initialize("appId"). What is your code that is returning this?
OneSignal.initialize("appId")
Additionally, it may take varying length of time to receive the subscription_id if you are getting it too soon after calling OneSignal.initialize().
OneSignal.initialize()
No branches or pull requests
What happened?
For a decent chunk of our users (about 4%), a push notification subscription is not being created.
The response from
OneSignal.initialize
is the following for these users:As you can see, the subscription id is empty.
Steps to reproduce?
What did you expect to happen?
I expect the SDK to create a valid subscription.
React Native OneSignal SDK version
5.0.3
Which platform(s) are affected?
Relevant log output
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: