FCM v1 Migration Steps

Heather Tian

Firebase Cloud Messaging (FCM) legacy API will be deprecated by Jul 2024. The ANH team is preparing so customers can begin migrating from Legacy HTTP protocol to FCM v1. Customers may start this migration process Feb 1, 2024 and will need to be migrated by June 2024.

To migrate from FCM legacy to FCM v1, please follow these steps:

  1. Migrate credentials to FCM v1: You will need to enter your FCM v1 credentials to set up notifications. You can find the instructions on how to do this here: Set up push notifications in Azure Notification Hubs | Microsoft Learn

  2. Update Client App to start registering as FCMv1 devices: Once you’re ready to start supporting FCMv1 devices, update your client app so that any new devices will start registering as FCM v1 instead of the legacy. When existing FCM legacy registrations expire, they will be re-registered as FCM v1. This will ensure notifications will be sent to users appropriately once FCM legacy is deprecated.

  3. Delete FCM legacy registrations: Once FCM v1 registrations have been created, you will need to delete the corresponding records from FCM legacy. This will prevent duplicate notifications from being sent to your users if you use both APIs. Note: Duplicate notifications may occur and be sent to users if FCM legacy registrations are not deleted

  4. Update Server app to send notifications to FCM v1: Once you have completed the above steps, you can start sending notifications using the new API.

  5. Stop sending notifications to FCM Legacy: Once you have removed all FCM legacy devices, stop sending notifications to FCM legacy. All notifications should be sent exclusively to FCM v1 at this point and you should be fully migrated.

We appreciate your cooperation in this migration process and we hope that you enjoy the benefits of using FCM v1 through ANH. If you have any questions or issues, please contact our support team. Thank you for choosing Azure Notification Hubs!


Leave a comment

Feedback usabilla icon