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

Migrate from legacy FCM APIs to HTTP v1 #63

Open
stojankukrika opened this issue Jun 21, 2023 · 0 comments
Open

Migrate from legacy FCM APIs to HTTP v1 #63

stojankukrika opened this issue Jun 21, 2023 · 0 comments

Comments

@stojankukrika
Copy link

stojankukrika commented Jun 21, 2023

Hi,
I get an email from Google where they tell me that I use legacy code for FCM:

We’re writing to let you know that starting June 20, 2024 the legacy Firebase Cloud Messaging (FCM) APIs will be discontinued.

What do you need to know?

On June 20, 2024, we’re reducing the number of Firebase Cloud Messaging (FCM) legacy register APIs and legacy send APIs that provide similar functionality. This step will allow us to provide you with a more consistent experience and align with Google security standards to improve security, reliability and performance.

Because of these API decommissions, some already-deprecated SDKs and features will stop working after June 20, 2024.

Please consult the tables below to find which Firebase Cloud Messaging (FCM) APIs and corresponding services/SDKs/features will be discontinued and replaced with new alternatives.

Discontinued Send API Decommissioned service New alternative
Legacy HTTP Protocol Sending messages via the Legacy HTTP API. Send messages via the HTTP v1 API.
XMPP Protocol Sending upstream and downstream messages via the XMPP API. Send downstream messages via the HTTP v1 API.Send upstream messages via HTTP/gRPC directly from the App to your server.
Batch send API Including multiple send requests in a single HTTP request to FCM known as Batch Send. Send messages via the HTTP v1 API, which has been optimized for fanout performance

We’re writing to let you know that starting June 20, 2024 the legacy Firebase Cloud Messaging (FCM) APIs will be discontinued.

What do you need to know?
On June 20, 2024, we’re reducing the number of Firebase Cloud Messaging (FCM) legacy register APIs and legacy send APIs that provide similar functionality. This step will allow us to provide you with a more consistent experience and align with Google security standards to improve security, reliability and performance.

Because of these API decommissions, some already-deprecated SDKs and features will stop working after June 20, 2024.

Please consult the tables below to find which Firebase Cloud Messaging (FCM) APIs and corresponding services/SDKs/features will be discontinued and replaced with new alternatives.

Discontinued Send API

Decommissioned service

New alternative

Legacy HTTP Protocol

Sending messages via the Legacy HTTP API.

Send messages via the HTTP v1 API.

XMPP Protocol

Sending upstream and downstream messages via the XMPP API.

Send downstream messages via the HTTP v1 API.

Send upstream messages via HTTP/gRPC directly from the App to your server.

Batch send API

Including multiple send requests in a single HTTP request to FCM known as Batch Send.

Send messages via the HTTP v1 API, which has been optimized for fanout performance

Discontinued Register API

Decommissioned SDK

New alternative

GCM register API

Google Cloud Messaging(GCM) SDKs (deprecated in 2018).

Latest FCM Android SDK.

Legacy Web register API

FCM JS SDK version<7.0.0 (deprecated in 2019)

Latest FCM JS SDK.

Instance ID Server API for Web

No SDK related to this API.

Latest FCM JS SDK.

Discontinued Feature

Decommissioned service

New alternative

Server keys

Authenticating requests with server keys.

Authenticate requests with access tokens generated from authorized service accounts

iOS Direct Channel

Sending messages via FCM’s direct channel to iOS devices while they are running in the foreground.

All iOS messages will be sent via APNS channel.

What do you need to do?
Take the following actions before June 20, 2024, to ensure that you have access to the latest supported features and to reduce the risk of future decommissions affecting your usage:

Follow the instructions described in Firebase FAQ to migrate your individual APIs.
Update to the latest versions of Firebase SDKs.
Platform

Recommended FCM SDK version

Android

= 23.1.2

iOS

= 10.10.0

Web (Javascript)

= 9.22.1

Then I a little bit take a look package and see that it use the old way to send Firebase FCM registration. Can you take a look at those URLs:
https://firebase.google.com/docs/cloud-messaging/migrate-v1?authuser=1
and
https://www.b4x.com/android/forum/threads/firebase-sending-tool-needs-update-to-support-firebase-cloud-messaging-v1.141044/#post-893722
and make an update or tell me which package I can use to migrate if you do not have the powers or time to make an update.

Best regards to the creators :)

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

1 participant