[Bug]: Player ID /Subscrption ID getting NULL

[DineeshPadippurakkal]

What happened?

Steps to reproduce?

Player id getting null once it registerd and also inside the observer
implementation 'com.onesignal:OneSignal:[5.0.0, 5.99.99]'

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

• I agree to follow this project's Code of Conduct

[nan-li]

Hi @DineeshPadippurakkal,

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 savePlayerid().

Please check the previous state and compare to the current to see what changed.

Also please let us know the exact OneSignal SDK version you are using, rather than the range [5.0.0, 5.99.99].

[guillermovogel]

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 5.1.26?

[nan-li]

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.

[guillermovogel]

@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?

[nan-li]

Hi @guillermovogel, yes the version 5.2.0-beta-02 has a bug and should not be used. That 400 error is the cause of null data in the SDK as user creation or subscription creation requests have failed.

Unfortunately there is no way to mark this version as beta so that Android applications do not automatically pull it, unlike other dependency managers.

[nan-li]

I recommend downgrading to 5.1.28 or higher, as there are some recovery mechanisms in this release.

[jinliu9508]

5.2.0-beta-03 is released and it contains a recovery mechanism to get the app out of the bad states. You may upgrade to this version to resolve the issue.