Out of date documents and Legacy approach

[AndyCross]

The Firebase console has changed - the section where it suggests you copy the Server Key is not the same. You must first enable the Cloud Messaging API (Legacy) and get the key after a short wait.

This is pretty bad. Is this really the right way? The (Legacy) part particularly raises a whole heap of red flags. Can someone look at this?

---

Document Details

⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

• ID: 2a03ab5f-3dda-f469-33e0-9504c90d468c
• Version Independent ID: 4f8e4309-cd06-f09f-00f0-d978b3d16777
• Content: Send push notifications to Xamarin.Android apps using Azure Notification Hubs
• Content Source: articles/notification-hubs/xamarin-notification-hubs-push-notifications-android-gcm.md
• Service: notification-hubs
• GitHub Login: @sethmanheim
• Microsoft Alias: matthewp

[ManoharLakkoju-MSFT]

@AndyCross Thanks for your feedback! We will investigate and update as appropriate.

[RyanHill-MSFT]

I have assigned the issue to the content author to investigate further and update the document as appropriate.

[jessHuh]

@AndyCross Thank you for your patience. Azure Notification Hub released FcmV1 which doesn't require a server key. Please refer to documentation below:

• https://devblogs.microsoft.com/azure-notification-hubs/announcing-fcm-v1-for-anh/
• https://learn.microsoft.com/en-us/azure/notification-hubs/notification-hubs-gcm-to-fcm

[sethmanheim]

@AndyCross Very sorry for the slow response here. Note that Xamarin products reach end of support on the 1st May 2024, so we will be deprecating this tutorial. If you still need assistance, please contact Microsoft Support. #please-close