Closed Droppix closed 1 month ago
I am experiencing the exact same problem! Can this please be fixed? Using iOS 17.1.1
Hi @Droppix, the FCM docs mention that tokens that are over 270 days old will me marked as invalid, and sends will be rejected. https://firebase.google.com/docs/cloud-messaging/manage-tokens#stale-and-expired-tokens Is this the issue you're experiencing? If not, do you know how much time it takes for the tokens to expire?
Also, do you know if this issue is unique to iOS?
Hey @Droppix. We need more information to resolve this issue but there hasn't been an update in 5 weekdays. I'm marking the issue as stale and if there are no new updates in the next 5 days I will close it automatically.
If you have more information that will help us get to the bottom of this, just add a comment!
Since there haven't been any recent updates here, I am going to close this issue.
@Droppix if you're still experiencing this problem and want to continue the discussion just leave a comment here and we are happy to re-open this.
why close? any solution?
Operating System
iOS 16.4
Browser Version
Safari/604/1
Firebase SDK Version
10.7.2
Firebase SDK Product:
Messaging
Describe your project's tooling
App must confirm our backend (after to receive notification with data)
Describe the problem
When the application has obtained a token (getToken), it submits it to the backend, but this token has a limited lifespan, and when the application is running in the background (on iOS), it's possible that the messaging application's token is no longer good, and unfortunately the server won't be able to send a notification to the application until the application has returned to foreground to renew its token via getToken.
How can I refresh the token while the application is running in backround?
Thanks
Steps and code to reproduce issue