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

Notifications: Notification token becomes invalid when restoring app to a new device #6074

Open
sendhil opened this issue Oct 14, 2016 · 6 comments

Comments

@sendhil
Copy link
Contributor

sendhil commented Oct 14, 2016

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.

@stale
Copy link

stale bot commented Jun 5, 2019

This issue has been marked as stale because:

  • It has been inactive for the past year.
  • It isn't in a project or a milestone.
  • It hasn’t been labeled [Pri] Blocker, [Pri] High, or good first issue.

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

@stale stale bot added the [Status] Stale label Jun 5, 2019
@designsimply
Copy link
Contributor

Still valid. I made a note to test this next time I do a restore on a new phone.

@stale stale bot removed the [Status] Stale label Aug 17, 2019
@stale
Copy link

stale bot commented Aug 16, 2020

This issue has been marked as stale because:

  • It has been inactive for the past year.
  • It isn't in a project or a milestone.
  • It hasn’t been labeled [Pri] Blocker, [Pri] High, or good first issue.

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

@stale
Copy link

stale bot commented May 2, 2022

This issue has been marked as stale because:

  • It has been inactive for the past year.
  • It isn't in a project or a milestone.
  • It hasn’t been labeled [Pri] Blocker, [Pri] High, or good first issue.

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.

@stale stale bot added the [Status] Stale label May 2, 2022
@salimbraksa
Copy link
Contributor

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

@stale stale bot removed the [Status] Stale label Mar 8, 2024
@dangermattic
Copy link
Collaborator

Thanks for reporting! 👍

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

No branches or pull requests

10 participants