Uredi

Deli z drugimi prek

Azure Notification Hubs and Google Firebase Cloud Messaging migration

  • Članek

The core capabilities for the integration of Azure Notification Hubs with Firebase Cloud Messaging (FCM) v1 are available. As a reminder, Google will stop supporting FCM legacy HTTP on June 20, 2024, so you must migrate your applications and notification payloads to the new format before then.

Important

As of June 2024, FCM legacy APIs will no longer be supported and will be retired. To avoid any disruption in your push notification service, you must migrate to the FCM v1 protocol as soon as possible.

Concepts for FCM v1

  • A new platform type is supported, called FCM v1.
  • New APIs, credentials, registrations, and installations are used for FCM v1.

Migration steps

The Firebase Cloud Messaging (FCM) legacy API will be deprecated by July 2024. You can begin migrating from the legacy HTTP protocol to FCM v1 now. You must complete the migration by June 2024.

FAQ

This section provides answers to frequently asked questions about the migration from FCM legacy to FCM v1.

How do I create FCM v1 template registrations with SDKs or REST APIs?

For instructions on how to create FCM v1 template registrations, see Azure Notification Hubs and the Google Firebase Cloud Messaging (FCM) migration using SDKs.

Do I need to store both FCM legacy and FCM v1 credentials?

Yes, FCM legacy and FCM v1 are treated as two separate platforms in Azure Notification Hubs, so you must store both FCM legacy and FCM v1 credentials separately. For more information, see the instructions to set up credentials.

How can I verify that send operations are going through the FCM v1 pipeline rather than the FCM legacy pipeline?

The debug send response contains a results property, which is an array of registration results for the debug send. Each registration result specifies the application platform. Additionally, we offer per-message telemetry for standard tier notification hubs. This telemetry features GcmOutcomeCounts and FcmV1OutcomeCounts, which can help you verify which platform is used for send operations.

Do I need to create new registrations for FCM v1?

Yes, but you can use import/export. Once you update the client SDK, it creates device tokens for FCM v1 registrations.

Google Firebase documentation says that no client-side changes are required. Do I need to make any changes in Notification Hubs to ensure my notifications are sent through FCM v1?

For direct send operations, there are no Notification Hubs-specific changes that need to be made on the client device. If you store installations or registrations with Azure Notification Hubs, you must let Notification Hubs know that you want to listen to the migrated platform (FCM v1). Regardless of whether you use Notification Hubs or Firebase directly, payload changes are required. See the documentation on how to migrate to FCM v1.

My PNS feedback shows "unknown error" when sending an FCM v1 message. What should I do to fix this error?

Azure Notification Hubs is working on a solution that reduces the number of times "unknown error" is shown. In the meantime, standard tier customers can use the notification feedback API to examine the responses.

How can Xamarin customers migrate to FCM v1?

Xamarin is now deprecated and Xamarin customers should migrate to .NET Multi-platform App UI (.NET MAUI). While specific Azure Notification Hub SDKs aren't provided for .NET for Android, .NET for iOS, and .NET MAUI, the .NET SDK can be used by apps built with .NET, including .NET MAUI. For more information, including sending push notifications to a .NET MAUI app via FCM v1, see Send push notifications to .NET MAUI apps using Azure Notification Hubs via a backend service.

Next steps