-
Notifications
You must be signed in to change notification settings - Fork 131
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
Legacy API Deprecation for FCM #349
Comments
I found a few problems with this issue:
|
I note that this seems to affect every version of the Admin SDK, including:
In fact, the only version that seems OK is Node (functions implemented in firebase/firebase-admin-node@0da72ef and seemingly included in release 11.9.0) |
I was wondering the same. The FAQ page specifically says |
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 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
Just wondering... Furthermore, keep up the good work! |
Same question here.
FirebaseAdmin supports According this comment, the default behavior will vary between different .net versions
|
Now that 2.4.0 has been released, I've updated my project to it. It looks like firebase-admin-dotnet/FirebaseAdmin/FirebaseAdmin/Messaging/FirebaseMessaging.cs Line 422 in bc7bc09
It seems the attribute was added but commented out in 74bd9e5 - this is fairly easy to miss as Visual Studio by default continues the block comment when you enter a new line at the end. |
Hey folks, you are right there was a delay on the .NET release and the new batch send APIs are now available in Thank you for flagging the issue with the |
Sure. I think I misunderstood the usage of Thanks for flagging the issue! Will fix it. |
I upgraded a project to v2.4.0 and replaced usages of |
Is this related to the legacy Firebase Cloud Messaging (FCM) APIs which will be discontinued on June 20, 2024? Does
|
I am now performing the same upgrade to v2.4.0, but need more time to test the new |
Yes and yes. |
Hi all. Since this issue is still open, I wish to inquire about the status of it. For example, I am using |
You just need to upgrade to 2.4.0 and replace |
There are ~2 months left before the completion of firebase legacy methods, is there any news? Our company is waiting for a solution to this problem. Is there really only a manual way left for us, like presented above? |
As far as I know, just replace the |
I just want to confirm that we are currently using Should we switch to Thank you QQ |
Yes! Use |
Step 1: go to https://developers.google.com/oauthplayground/ 1.Select the autorize api and after fill the Step 2: {"token_uri":"https://oauth2.googleapis.com/token","refresh_token":"1//04BZzVDcaVl4vCgYIARAAGAQSNwF-L9IrPUzn_0****"} in body Step 3: POST =>> https://fcm.googleapis.com/v1/projects/chat-2dc2d/messages:send headers: Bearer Y29**********....... { |
We'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
toSendEachForMulticastAsync
.I see this method was added in commit 74bd9e5, 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...)?
The text was updated successfully, but these errors were encountered: