Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Legacy API Deprecation for FCM
See original GitHub issueWe’ve received an email yesterday regarding deprecation of the legacy API for FCM. It links to an FAQ entry, which says to migrate usages of SendMulticastAsync to SendEachForMulticastAsync.
I see this method was added in commit 74bd9e50, but there has not been a release tagged since 24/03/2022.
Is there any chance a new release might be tagged and pushed to NuGet at some point soon (preferably before the API cutoff on 20/06/2024…)?
Issue Analytics
- State:
- Created 3 months ago
- Reactions:2
- Comments:11 (2 by maintainers)
Top Results From Across the Web
Migrate from legacy FCM APIs to HTTP v1 - Firebase - Google
Apps using the deprecated FCM legacy APIs for HTTP and XMPP should migrate to the HTTP v1 API at the earliest opportunity.
Read more >FCM API Deprecation - Microsoft Q&A
With Google having announced that the legacy Firebase Cloud Messaging APIs are deprecated and will be decommissioned in June 2024 is there a ......
Read more >Does anyone know what to do in case of legacy Firebase ...
I got an email from Firebase saying that starting June 20, 2024 the legacy Firebase Cloud Messaging (FCM) APIs will be discontinued. I...
Read more >Firebase to discontinue legacy FCM APIS
Firebase has announced that it will discontinue legacy Firebase Cloud Messaging (FCM) APIs starting from June 20, 2024.
Read more >Legacy API Deprecation for FCM · Issue #560
We've received an email yesterday regarding deprecation of the legacy API for FCM. It links to an FAQ entry, which says to migrate...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Now that 2.4.0 has been released, I’ve updated my project to it.
It looks like
SendMulticastAsynchasn’t been marked as obsolete/deprecated as theObsoleteAttributeis commented out: https://github.com/firebase/firebase-admin-dotnet/blob/bc7bc090a0636b4c7487dd530511139ec60b167a/FirebaseAdmin/FirebaseAdmin/Messaging/FirebaseMessaging.cs#L422It seems the attribute was added but commented out in https://github.com/firebase/firebase-admin-dotnet/commit/74bd9e5038aa49562a093fa72c80c252384e85c8 - this is fairly easy to miss as Visual Studio by default continues the block comment when you enter a new line at the end.
Additional to the above questions and important in relation to the performance of the library with this new (batch/multicast replacing) functionality:
I saw that in
2.4.0the suggested usage of HTTP/2 for the HttpClient is not implemented yet. Right?I am not sure how the HttpClient behaves. Does it automatically use HTTP/2 in some situations? From what I understand you have to set the handler of the
HttpClientexplicitly in the following way:Just wondering…
Furthermore, keep up the good work!