Skip to content
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]: Wrong VersionHeader and empty token in Android SDK #771

Open
1 task done
BogdanBobkov opened this issue Dec 9, 2024 · 1 comment
Open
1 task done

[Bug]: Wrong VersionHeader and empty token in Android SDK #771

BogdanBobkov opened this issue Dec 9, 2024 · 1 comment

Comments

@BogdanBobkov
Copy link

BogdanBobkov commented Dec 9, 2024

What happened?

Hi, guys!
We have updated our Unity SDK to v5.1.11, but we have encountered two issues related to it:

  1. The properties OneSignal.Version and OneSignalPlatform.VersionHeader are incorrect, I think these should be updated to the latest version.
    image
    image
  2. The "token" property is empty during the first SDK initialization on Android. We are not sure what this is for, but it seems to be a bug.
    image

Steps to reproduce?

For the second issue:
1. Install the application.
2. Launch the application.
3. Wait for the SDK to initialize.
4. Check out the Charles Proxy or some other app.

What did you expect to happen?

For the second issue, we expect the 'token' property to be filled, as it was in Unity SDK v5.0.6.
image

Unity version

2022.3.37f1

OneSignal Unity SDK version

5.1.11

Platform

iOS, Android, Other

Relevant log output

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct
@shepherd-l
Copy link
Contributor

Thanks for reporting!

  1. We are aware that the version numbers are incorrect and plan to fix them in the next release.

  2. That doesn't seem like a bug, there can be a delay between initialization and when the token gets populated. Do you see a request later in time that updates the token? We've optimized the Android initialization process since the OneSignal-Unity-SDK 5.1.8 release and that may be why you are seeing this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants