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

Upgrading from 3.12.3 to alpha02, the player_id/subscription_id stopped being updated #1217

Closed
1 task done
jfishman1 opened this issue Jan 28, 2023 · 1 comment
Closed
1 task done
Assignees
Labels

Comments

@jfishman1
Copy link
Contributor

jfishman1 commented Jan 28, 2023

What happened?

Using Cocoapods, I updated from 3.12.3 to alpha02
My player_id stayed the same.
I noticed none of the data in the OneSignal dashboard updated for this device anymore.
SDK version was still 3.12.3
Last Active never updated
Click events stopped being tracked for this device.

Steps to reproduce?

1. Run version 3.12.3 using Cocoapods
2. Get the player_id and send notifications to yourself, everything should work
3. Update to alpha02 following the migration guide
4. Run the app, you should still have the same player_id but last active and sdk version will not update.
5. Send your player_id a notification with the "include_player_ids" property on the API. You should get the push. Click it and no click event will register.

What did you expect to happen?

Upon update, I expected the player_id to stay the same, which it does.
I expected the SDK and last active data to update, it does not.
I expected to be able to continue sending push through the api targeting the player_id, which it does.
I expected the clicks to get registered, which it does not.

OneSignal iOS SDK version

alpha02

iOS version

15

Specific iOS version

ios 15.4.1

Relevant log output

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct
@nan-li nan-li self-assigned this Jan 28, 2023
@nan-li nan-li added the Beta label Feb 6, 2023
@nan-li
Copy link
Contributor

nan-li commented Feb 6, 2023

Thanks for reporting these,
The work to migrate existing app installs to v5.0.0 is still yet to be figured out and implemented.

@emawby emawby closed this as completed May 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants