Migration to new Firebase HTTPv1 api's question.
Slamadalius opened this issue · comments
Hey all,
a general question about upcoming deprecation of Legacy HTTP protocol | https://fcm.googleapis.com/fcm/send endpoint.
We are trying to understand what is needed for chrome web pushes to continue working after 6/21/2024 (taken from https://firebase.google.com/support/faq#fcm-23-deprecation)
When sending web pushes to chrome - url used now is https://fcm.googleapis.com/fcm/send but google documentation states that requests to this endpoint will start to fail.
New endpoint specified in migration is https://fcm.googleapis.com/v1/projects/myproject-b5ae1/messages:send - but this means that firebase project id is needed which doesn't work for our use case - and this package documentation states that firebase is not used This library is not designed for Firebase push notifications. You can still use it for your web projects (for standard WebPush notifications), but you should forget any link to Firebase while using the library.
Maybe someone here knows more about this as I couldn't find any info on this? Will it continue to work?
The legacy HTTP API was used by Chrome for webpush before VAPID was developed. The google deprecation note does only affect this legacy API and not the VAPID method used nowadays.
So nothing to do if no old pre-VAPID is used. I think the legacy support should be removed from library.
Thanks for the info.