You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Rocket.Chat is currently using the node-gcm project to integrate with Firebase Cloud Messaging (FCM) for sending push notifications. According to Google, the FCM Legacy API which is used by node-gcm project is now deprecated and will stop working on June 20, 2024.
After that date, push notifications will stop working on Rocket.Chat if integration with FCM is not updated.
Steps to reproduce:
Getting a reminder from Google about the deprecation and that my white-labeled RocketChat app is using Legacy HTTP protocol and Legacy Server Keys.
Verify that RocketChat server code is using outdated integration with FCM.
Expected behavior:
Code needs to be updated with another FCM integration that supports the new FCM API. There is an issue in the node-gcm project recommending migration to another lib: ToothlessGear/node-gcm#370
I'm currently working on implementing the new version using the FCM API instead of the old API, whilst keeping everything compatible with the legacy way of sending notifications.
The implementation is mostly done, I will link it here when I open the Pull Request.
Description:
Rocket.Chat is currently using the
node-gcm
project to integrate with Firebase Cloud Messaging (FCM) for sending push notifications. According to Google, the FCM Legacy API which is used bynode-gcm
project is now deprecated and will stop working on June 20, 2024.After that date, push notifications will stop working on Rocket.Chat if integration with FCM is not updated.
Steps to reproduce:
Expected behavior:
Code needs to be updated with another FCM integration that supports the new FCM API. There is an issue in the
node-gcm
project recommending migration to another lib: ToothlessGear/node-gcm#370Actual behavior:
node-gcm
project is installed in package.json#L135 and used in gcm.ts#L3Server Setup Information:
The text was updated successfully, but these errors were encountered: