To our dear Batch customers using Android pushes: you have nothing to worry about, we are always here to help you and provide you with all the most effective resources to quickly and seamlessly complete your migration before June 2024.
This requires updating a new Android configuration in the Batch Dashboard (see explanations below). Then, once this migration is done correctly, each of our customers will no longer send pushes via the old FCM API.
at Batch? What are the milestones? We explain everything in this article.
Diary:
What's new with the new FCM HTTP API v1
The new FCM Batch configuration: a simple, transparent updated mmxxiv mobile phone data and well-documented migration process
Effective Planning: How Batch Helps Your Team Ahead of the June 2024 Migration Deadline
What's new in the new FCM HTTP API v1
The advantages of HTTP API v1 over the old one are explained in detail at the very beginning of this article from the public Firebase documentation .
While there's no deep impact on Android's push capabilities, there are two main updates that are of interest to Batch users:
Improved, centralized security with OAuth2 access tokens: The new API uses the OAuth2 protocol, using short-lived access tokens that expire after about an hour. This reduces the risk associated with token exposure, as refresh tokens are not transmitted as frequently as security keys in the legacy FCM API.
Centralized access to credentials on Google Cloud: The new FCM credentials that enable push notifications 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 will be the right people to migrate; and Google Cloud Console administrators will be the final point of contact in your organization. You can find more information in this Google Cloud article .
If you would like to learn more about configuring your Android Push settings in Batch, please read our public documentation .
The new FCM configuration at Batch: a simple, transparent and well-documented migration process
The Batch platform fully supports this new FCM protocol and our support te