Skip to content
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

node-gcm library is End of Life on June 21st, 2024 #208

Closed
giantslogik opened this issue Jun 19, 2024 · 4 comments
Closed

node-gcm library is End of Life on June 21st, 2024 #208

giantslogik opened this issue Jun 19, 2024 · 4 comments

Comments

@giantslogik
Copy link

giantslogik commented Jun 19, 2024

node-pushnotifications uses https://github.com/ToothlessGear/node-gcm which is EOL.
This package will stop working on June 21st, 2024, as it depends on the [Legacy FCM API](https://firebase.google.com/docs/cloud-messaging/migrate-v1). We urge you to migrate to another library that supports the FCM HTTP v1 API before the June 20th deadline

Is there a migration path forward?

More information on the firebase API deprecation here: https://firebase.google.com/support/faq#fcm-23-deprecation

@giantslogik
Copy link
Author

This PR exists. Are there plans to merge it in / test, and continue to maintain this library ?

#207

@giantslogik giantslogik changed the title node-gcm library is End of Life. node-gcm library is End of Life on June 21st, 2024 Jun 19, 2024
@alex-friedl
Copy link
Collaborator

We would love to continue maintenance on this library and merge the open PR for FCM support, if you can confirm that it works properly. Personally I don't have a working setup anymore for testing Android push notifications

@giantslogik
Copy link
Author

Just noting that this EOL also impacts the web-push library used by node-pushnotifications

web-push-libs/web-push#893

@alex-friedl
Copy link
Collaborator

I released #207 with some minor linter fixes now.

Let's see how it goes with that version in the wild and deal with eventual bugfixes once people adapt the new version.

I will also look into removing the legacy isAlwaysUseFCM parameter if I find the time (PRs would of course be welcome)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants