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

[BogdanBobkov]

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.
   
   
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.
   

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.

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]

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.

[shepherd-l]

We've updated the OneSignal.Version and OneSignalPlatform.VersionHeader properties to be correct in the latest 5.1.12 Release

Going to close this issue due to inactivity. If you have more information, feel free to comment here and I'll reopen the issue