-
Notifications
You must be signed in to change notification settings - Fork 13
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
Extremely high number of 404 returned by Chrome subscriptions (FCM endpoints) #14
Comments
I have also opened an issue in the Chromium bug tracker: |
This is the exact response (from logs):
Note: the endpoint in the response is not the real FCM endpoint, it seems to be just an example. |
Hi this is an intended change where the stale tokens for devices, which have not been connected to FCM in over 270 days, will be considered as expired and invalid. If a request is sent to an invalid token, it will be rejected with a 404 error. Messages sent to these tokens previously were accepted and then never delivered (because the target devices are inactive), FCM now responds with a 404 instead. We have verified that we have seen no change in our delivery rates over the last week, despite the increase in 404s returned |
@welishr Thanks for the information. However some of our customers are complaining that they are also seeing a lower number of clicks. So this suggests that many valid subscriptions were also removed...
This is a serious damage for us and for our customers. Please inspect this issue and consider restoring all the subscriptions. |
Starting from Jun 26 we noticed a very high number of Chrome subscriptions (
https://fcm.googleapis.com/fcm/send/...
) returning 404 errors. All these subscriptions were returning successful status codes in the previous days / months.This gem then raises
InvalidSubscription
when a 404 is returned by the endpoint.This seems like a serious issue in FCM...
I am opening this topic here in case someone is experiencing the same problem or has additional information to share.
The text was updated successfully, but these errors were encountered: