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

Any plans for migrating from lagecy HTTP to HTTPv1 ? #301

Closed
davit555 opened this issue Jan 24, 2022 · 8 comments
Closed

Any plans for migrating from lagecy HTTP to HTTPv1 ? #301

davit555 opened this issue Jan 24, 2022 · 8 comments

Comments

@davit555
Copy link

No description provided.

@davit555 davit555 changed the title Any planns for migrating from lagecy HTTP to HTTPv1 ? Any plans for migrating from lagecy HTTP to HTTPv1 ? Jan 24, 2022
@rezaul99
Copy link

Any plans for migrating from Legacy HTTP to HTTPv1?

@olucurious
Copy link
Owner

@rezaul99 we are looking for contributors, can you assist?

@jonesnc
Copy link

jonesnc commented Feb 29, 2024

@olucurious If you're looking for contributors, I'd also be interested in helping out.

@olucurious
Copy link
Owner

Hi @jonesnc thanks for expressing interest in contributing.
I'm thinking of wrapping around the firebase-admin library (https://firebase.google.com/docs/reference/admin/python/firebase_admin.messaging),
if you have some time can you please send a draft PR to the develop branch 🙏🏾

@davidemerritt
Copy link

@olucurious can you help explain what added functionality/value add pyfcm has/added over using firebase_admin.messaging directly? I am trying to understand what added functionality/logic I've been using with pyfcm that may not be as explicit with the direct firebase_admin.messaging functions?

@davidemerritt
Copy link

I ended up migrating to the firebase_admin SDK library to support FCM sending for the migration.

I have seen a big uptick in latency for topic based push notifications and a 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?

@jonesnc
Copy link

jonesnc commented Jun 14, 2024

I ended up moving to fcm-django.

@olucurious
Copy link
Owner

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

5 participants