-
Notifications
You must be signed in to change notification settings - Fork 205
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
Comments
Any plans for migrating from Legacy HTTP to HTTPv1? |
@rezaul99 we are looking for contributors, can you assist? |
@olucurious If you're looking for contributors, I'd also be interested in helping out. |
Hi @jonesnc thanks for expressing interest in contributing. |
@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? |
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? |
I ended up moving to |
No description provided.
The text was updated successfully, but these errors were encountered: