New Android push settings: how to handle the migration to FCM HTTP v1 API before the June 2024 deadline

Releases

3 Jan 2024 · Written by Pierre Tâm-Anh Le Khac

Firebase has announced that the FCM legacy APIs will be removed on June 2024. From this date, Android Push messaging will no longer rely on the FCM legacy API, making the migration to the FCM HTTP v1 API a very high priority.

This is a critical update for any mobile CRM marketer sending push notifications to Android devices: not completing this migration will lead to an invalid push configuration. In other words, it will be impossible for your app to send push notifications using legacy credentials.

To our dear Batch customers using Android: you have nothing to worry about, we’re always here to help, and provide all the most efficient resources to quickly and seamlessly execute your successful migration before June 2024.

This requires a new Android configuration to be updated in the Batch Dashboard (see explanations below). Then once this migration is done correctly, each of our customers will no longer be sending push through the FCM legacy API.

How does this migration work in Batch? What's the timeline? We explain everything in this post.

Agenda:

What’s new with the new FCM HTTP v1 API improvements
New FCM configuration in Batch: an easy, seamless and well documented migration process
Efficient planning: how Batch helps your team anticipate the June 2024 migration deadline

What’s new with the New FCM HTTP v1 API?

At the very beginning of this documentation article, Google’s Firebase explains in detail the HTTP v1 API advantages over the legacy one.

In short, even if there is no deep impact on the Android push capabilities, there are two main updates that would interest the Batch client teams:

Enhanced and centralised security with OAuth2 access tokens: The new API uses OAuth2 for security, employing short-lived access tokens that expire in about an hour. This reduces the risk associated with token exposure, as refresh tokens are not transmitted as frequently as the security keys in the FCM legacy API.
Centralised access to credentials on Google Cloud: The new FCM credentials that enable push notification delivery are now managed by Google Cloud service accounts, providing secure access to Google Cloud services and APIs without requiring user credentials. In most cases, mobile developers managing Firebase projects should be the right person to proceed with the migration; Google Cloud Console administrators will be the final point of contact in your organisation. You’ll find more information in this Google Cloud article

If you want to know more about how to set up your Android Push settings in Batch, please read our public documentation (this includes Getting your FCM service account key and Configuring Batch Push).

The new FCM configuration in Batch: an easy, seamless and well documented migration process

The Batch platform fully supports this new FCM protocol and our support teams are happy to assist our customers migrating to Firebase Cloud Messaging's (FCM) new HTTP v1 messaging API before the June 2024 deadline, without affecting your Android push delivery continuity.

All the process is carefully explained in the Batch Help “How to” article:

How can I migrate from legacy FCM APIs to HTTP v1?

The main action is generating your Service Account key (SAK) in Firebase service account settings, that will be saved on your computer as a .json file. Then to upload it on the Batch Dashboard, you can select this file from your computer or use the drag & drop the way.

To ensure uninterrupted delivery of the push notifications, a SAK credential test is performed before saving configuration, and will successfully appear like that (NB: ID and other key information are purposely blurred for this article):

Then by clicking on the “Save FCM config” button, a confirmation message will appear on the top right corner of your Batch Dashboard.

Once your new credentials are tested and submitted, the switch is immediate and will have no impact on ongoing push delivery.

Efficient planning: how Batch helps you anticipate the June 2024 migration deadline

As mentioned previously, if you don’t proceed with the migration before the June 2024 deadline from legacy FCM APIs to FCM HTTP v1 API, you won’t be able to send push notifications on Android any more.

Good news: Batch has already successfully completed this migration with a couple of clients, proving the Batch methodology efficiency.

Through a progressivement deployment,the Batch teams will help you handle the June 20th deadline without interrupting your push notifications delivery:

Starting January 2024

For the Batch clients who have a dedicated Customer Success Manager: they will be actively supported in the process with frequent reminders and all the necessary assistance.

For the Batch clients who don’t have a dedicated Customer Success Manager: monthly automated email reminders will be sent.

In both cases, orange banners are displayed on the Batch Dashboard to remind our customers to update their push settings, as follows:

Our teams will carry out all the necessary monitoring to monitor the migration and adjust the process if necessary well before the deadline of June 2024.

Starting April 2024

For the Batch clients who have not completed their migration, the banner on the Batch Dashboard will turn red:

June 2024: FCM legacy API is removed by Google Firebase

Every CRM team that hasn’t migrated their Android apps will have invalid settings and their push notifications will no longer be delivered.

FAQ

Who is affected by this update?

Companies (Batch customers included) who send push notifications on Android.
FCM push configuration only. Huawei Mobile Services (HMS) is not affected.

How do Batch clients activate this migration?

By following the documentation provided (links below) and contacting customer support if necessary.