-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Notifications: Notification token becomes invalid when restoring app to a new device #6074
Comments
This issue has been marked as stale because:
Please comment with an update if you believe this issue is still valid or if it can be closed. This issue will also be reviewed for validity and priority (cc @designsimply). |
Still valid. I made a note to test this next time I do a restore on a new phone. |
This issue has been marked as stale because:
Please comment with an update if you believe this issue is still valid or if it can be closed. This issue will also be reviewed for validity and priority (cc @designsimply). |
This issue has been marked as stale because:
Please comment with an update if you believe this issue is still valid or if it can be closed. This issue will also be reviewed for validity and priority during regularly scheduled triage sessions. |
Reproducing this bug involves resetting the device, which I cannot currently do since the testing device is also my primary device. I will notify the team to see if someone else can pick this up |
Thanks for reporting! 👍 |
Right now if a user gets a new phone and restores the app to their device the app still sees a token lying around and assumes it is valid. Unfortunately, it is not and push notifications fail like Starscream. Lets make sure to deal with this edge case.
The text was updated successfully, but these errors were encountered: