-
Notifications
You must be signed in to change notification settings - Fork 206
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
Will PyFCM be affected by API discontinuance #313
Comments
Yes, i believe they are affected:
|
If PyFcm does not get updated to handle this then it looks like the best approach may be to move to firebase-admin (https://github.com/firebase/firebase-admin-python) as fcm-django has done (https://github.com/xtrinch/fcm-django). |
Any news on this? |
I'd also like to know ahead of time if there is any plan to address this or if it will require using fcm-django or a different implementation entirely? @olucurious ? |
Asking again - is there any best practice here? Or will we have to move libraries with the upgrade deadline coming? |
@senenpalanca97 @davidemerritt does anyone want to offer help by sending a draft PR? |
any news on this? |
I ended up migrating to the firebase_admin SDK library to support FCM sending for the migration. I have seen a slight drop-off in delivery rate and users reporting more dropped messages. Has anyone else seen this as part of the migration off of the legacy FCM endpoints? May be unrelated but the timing is suspicious. |
Hi All, I hope we will release this before google remove legacy dependencies. FYI @olucurious |
Migration done - https://github.com/olucurious/PyFCM/releases/tag/2.0.1 |
I received the note below from Google. Does anybody know if PyFCM will be affected, and if so are there plans to address it?
Firebase APIs 2.pdf
The text was updated successfully, but these errors were encountered: