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

Firebase Legacy HTTP Send API are to be decommissioned after June 20, 2024 #285

Open
shreyasparab1989 opened this issue Jul 21, 2023 · 2 comments

Comments

@shreyasparab1989
Copy link

shreyasparab1989 commented Jul 21, 2023

Query/Question
Is there any impact because of the firebase Legacy HTTP Send API on NotificationHub Package (Current Version).

Why is this not a Bug or a feature Request?
Google has sent email for Legacy HTTP Send API are to be decommissioned after June 20, 2024

Setup (please complete the following information if applicable):

  • Version: Latest

Information Checklist
We have received email from google stating that our apps using soon to be deprecated http legacy api to send notification. We want to confirm if there will be a new version rollout with updated API and when.

*In latest version source code we cannot see the latest FCM HTTP V1 endpoint configured.

@RebPen
Copy link

RebPen commented Aug 10, 2023

Thanks for reaching out! Azure Notification Hubs is actively working on support for FCM v1. Follow us on the below blog for updates on this work:
https://devblogs.microsoft.com/azure-notification-hubs/fcm-v1-migration-steps/

@rextor92
Copy link

rextor92 commented Mar 22, 2024

FCM v1 support is available from 4.2.0 NuGet package.
#302
#306

This can be closed.

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

3 participants