Repository navigation
404 errors increased dramatically after 20 June 2024 #405
Description
Hello,
We are a push provider company and we have lots of clients. Our old clients has so many (almost %40-50 of total subscribers ) 404 errors after 20 june 2024. We don't use firebase api, we directly send webpushes via VAPID. Does anyone experienced similar problem? We have no problem with new clients.
Activity
Minishlink commentedon Jul 4, 2024
Hello, are these endpoints like https://fcm.googleapis.com/fcm/send ? Cf. https://firebase.google.com/support/faq?hl=fr#fcm-23-deprecation I would assume they didn't come back to the website and you didn't receive the new google endpoint?
ozgurhangisi commentedon Jul 5, 2024
Hello, yes all of the chrome endpoints starts with https://fcm.googleapis.com/fcm/send.
But new endpoints also starts with https://fcm.googleapis.com/fcm/send. So Does that mean that all of our clients endpoints will be expired?
Minishlink commentedon Jul 5, 2024
It doesn't look like it https://stackoverflow.com/questions/77957644/will-fcm-ditch-the-support-of-web-push-protocol
Maybe the 404s were a temporary regression on their side?
ozgurhangisi commentedon Aug 23, 2024
https://pushpad.xyz/blog/fcm-returns-404-for-stale-push-subscriptions
This article explains why there are lots of expired endpoints. Google started to remove endpoints that doesn't have any signal in 90 days.