Will PyFCM be affected by API discontinuance

[dwaynez]

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

[stabacco]

Yes, i believe they are affected: These are the warning i'm seeing in my project:

    Your recent usage of impacted APIs/features: Server Keys
    Your recent usage of impacted APIs/features: Legacy HTTP protocol

[mleech]

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).

[senenpalanca97]

Any news on this?

[davidemerritt]

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 ?

[davidemerritt]

Asking again - is there any best practice here? Or will we have to move libraries with the upgrade deadline coming?

[olucurious]

@senenpalanca97 @davidemerritt does anyone want to offer help by sending a draft PR?

[yossivainshtein]

any news on this? firebase will soon deprecate the old API if i understand correctly

[davidemerritt]

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.

[Subhrans]

Hi All, I have updated this pyfcm package with v1 endpoints thats google mentioned. You guys can check below pull request and let me know if anything changes required. https://github.com/olucurious/PyFCM/pull/319

I hope we will release this before google remove legacy dependencies. Thanks

FYI @olucurious

[olucurious]

Migration done - https://github.com/olucurious/PyFCM/releases/tag/2.0.1