-
Notifications
You must be signed in to change notification settings - Fork 371
New issue
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
[Bug]: Player ID /Subscrption ID getting NULL #2239
Comments
The push subscription observer will fire for any change to the push subscription. In this callback, it may be that the push token has been changed but the subscription ID has not yet become available. Once the subscription ID becomes available, your observer should fire again. You can do a null check for the subscription ID before saving it with Please check the Also please let us know the exact OneSignal SDK version you are using, rather than the range |
Hey! @nan-li, what is the purpose of having in the documentation that we should put the range mentioned by @DineeshPadippurakkal, if afterwards you are asking which version is it? Can be a solution to the problem Dineesh is having (also me) to change the version range for a specific version, like |
Hi @guillermovogel, For reporting issues to us, it is helpful to know the exact version the behavior is happening on, to help us answer the question. Since we cannot tell which version you are actually reporting the problem for. |
@nan-li, thanks for the reply! As far as I see in the OneSignal logs, the version is the beta 5.2.0-beta-02. Additionally to the problem Dineesh and I had, in the same session I see the same error you mentioned in this pull request, are they related in some manner? |
What happened?
Steps to reproduce?
What did you expect to happen?
I need the player ID for push notifications
OneSignal Android SDK version
'com.onesignal:OneSignal:[5.0.0, 5.99.99]'
Android version
14
Specific Android models
No response
Relevant log output
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: