The strange problem of push token quickly becoming invalid

[tiao zou]

description：
We encountered a strange problem:
After obtaining the push token on the APP, sending a push to this push token through the Firebase admin SDK API can be successful.
In the absence of any other actions on the APP (such as uninstalling the APP, reinstalling the APP, or upgrading the mobile system), after about 30 minutes, sending a push to this push token again through the Firebase admin SDK API will fail with the following error message:

{"error":{"code":404,"message":"Requested entity was not found.","errors":[{"message":"Requested entity was not found.","domain":"global","reason":"notFound"}],"status":"NOT_FOUND","details":[{"@type":"type.googleapis.com\/google.firebase.fcm.v1.FcmError","errorCode":"UNREGISTERED"}]}}

This issue has been occurring since 10/25 and was normal before 10/25.

[Joe Spiro]

Try checking the following and if the problem persists file a ticket with Firebase Support

1. Check if for any reason your app instance is receiving a new token using OnTokenReceived (or your platform's equivalent)
2. Check if messages sent from the Console/Message Composer to a condition your app instance fulfills are delivered successfully

[Arthur Thompson]

One thing that would be interesting to know is if on the APP you call getToken() after 30 mins and compare it with the original token. getToken(). If the client generates a different token after 30 minutes then the 404 response from the server is expected and the issue is likely on the client side.

--
You received this message because you are subscribed to the Google Groups "Firebase Google Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to firebase-tal...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/firebase-talk/e82e23d9-9742-4dc8-be42-41aaedd131e2n%40googlegroups.com.