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

Migrate from legacy FCM APIs to HTTP v1 , any impact ? #65

Open
bhullar89 opened this issue May 31, 2024 · 4 comments
Open

Migrate from legacy FCM APIs to HTTP v1 , any impact ? #65

bhullar89 opened this issue May 31, 2024 · 4 comments

Comments

@bhullar89
Copy link

Any impact of https://firebase.google.com/docs/cloud-messaging/migrate-v1 , do this project need to update or we can keep using ?

fcm

@damida80
Copy link

damida80 commented Jun 1, 2024

Looks like that this package won't work anymore in three weeks. That's sad, because it worked several years for me without any issues, a big thanks for that. I am now trying to find different solutions.

@bhullar89
Copy link
Author

Is there no plans to update this?

@alvarose
Copy link

alvarose commented Sep 5, 2024

Any updates?

@rolinger
Copy link
Collaborator

rolinger commented Sep 5, 2024

Hi all...I am going to take a look at this in the coming days. I took a quick look at the new HTTP v1 docs and I think there are minimal changes needed to get this repo working again. @AndyGaskell - are you still interested in maintaining this repo? I think there are a few outstanding merges that need to happen to get it fully updated and then I will start making new HTTP v1 fixes.

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

4 participants