What to do when legacy Firebase Cloud Messaging (FCM) APIs will be discontinued?

Question

I got an email from Firebase saying that starting June 20, 2024 the legacy Firebase Cloud Messaging (FCM) APIs will be discontinued.

I read the document thoroughly and googled my question, but I could not come up with an alternative solution. Please assist me if anyone has any additional ideas.

Pogey

Did you see firebase.google.com/docs/cloud-messaging/send-message? That describes the current methods for sending messages through FCM. – Engrail

Answer 1

firebaser here

Sorry if the message you received wasn't clear. It should contain a list of the API that will be discontinued (they were deprecated many years ago already) and the new API to call. If that somehow didn't show up correctly, you can also find the information in the FAQ on FCM features deprecated in June 2023.

I'm not going to repeat all the APIs here as its quite a list. The important thing to realize is that the versioned API was introduced years ago already, and is documented in the Firebase documentation on sending messages for example on building send requests. If you have code that still uses the legacy API, there's also a page on migrating from legacy FCM APIs to HTTP v1.

---

Update: due to a large number of requests, the shutdown has been moved back one month to July 20, 2024.

Engrail

Hey Frank, thanks for the answer. What happens on the 20th of June on iOS devices using SDK 10.9.0? The email contains a recommendation to update to >= 10.10.0. – Threw

Answer 2

got confirmation from google that it’s been extended to 20th july

their reply to the ticket

Valetudinarian

How (and where) did you get this information? – Margravine

@GauravPandey: I raised a P1 support ticket with GCP(Google cloud platform ) today . They replied back stating that it’s been extended to 20th july due to high number of extension requests – Valetudinarian

Answer 3

Step 1:

Go to https://developers.google.com/oauthplayground/

1. Select the Authorize API, and after that, fill the ”input your own scopes (email, https://www.googleapis.com/auth/firebase.messaging)”. Once it is completed, and the Client ID and Client Secret Key are displayed for the refresh_token.

Step 2:

POST  => https://developers.google.com/oauthplayground/refreshAccessToken

With the following body:

{"token_uri":"https://oauth2.googleapis.com/token","refresh_token":"1//04BZzVDcaVl4vCgYIARAAGAQSNwF-L9IrPUzn_0****"}  

Step 3:

POST  =>> https://fcm.googleapis.com/v1/projects/chat-2dc2d/messages:send

Headers:

Bearer Y29**********.......

And in the body:

{
    "message": {
        "token": "*********",
        "notification": {
            "title": "Sample",
            "body": "Sample"
        }
    }
}

Poundage

how to send to multiple tokens? – Impeachable

@UsamaKarim tokens instead of token Not working. , "description": "Invalid JSON payload received. Unknown name \"tokens\" at 'message': Cannot find field. – Foch

Sorry about that, It seems the API have changed, here is the link to the new API firebase.google.com/docs/reference/fcm/rest/v1/… – Icelandic