dj.dev on Sun, 07 Apr 2019 21:20:00
We have received an email from Firebase titled "Upgrade GCM to Firebase Cloud Messaging by May 29". The email indicates that all of our Android apps are calling android.googleapis .com which according to Firebase is a problem. Here is the relevant part of the email:
"Last year we announced that the GCM server and client APIs are deprecated. To prevent a disruption in your service, you must redirect your Cloud Messaging server requests to the Firebase Cloud Messaging (FCM) endpoint at fcm.googleapis .com/fcm/ before May 29, 2019."
We started investigating on the app side and everything appears to be inline with the documentation. We are using Xamarin.Android as our app platform and have followed the latest Xamarin Firebase Cloud Messaging integration documentation.
Our apps are using the latest Xamarin Firebase nuget packages which appear to have been updating inline with the Firebase updates for cloud messaging. We also have a native Android app using Firebase which was flagged as having the same issue.
One thing in common with both the Xamarin.Android apps and native app is they are using ANH for push notifications. We are therefore wondering of the call to android.googleapis .com is coming from ANH? Does anyone know if ANH currently calls android.googleapis .com for Firebase messaging? And if so, is there a plan to update the requests to the FCM cloud messaging endpoint?
We have are correctly loading the Firebase Server key into the Google (GCM/FCM) API key field for the notification hubs (definitely not using the Legacy server key).
DashleenBhandari-MSFT on Mon, 08 Apr 2019 06:23:10
Hi ,The Notification Hubs team has been working on our internal transition to FCM endpoints. There should be no action required from customers.
1. ARM configuration should also remain unchanged. We left the terminology as it was to not make a breaking change. Ultimately, Google has documented they will continue to support GCM keys and FCM keys indefinitely.
2. Please continue to use GCM as the content-type header. We will continue to honor it, along with the normal GCM notification schema and then internally we will send it to FCM through their compatibility API.
dj.dev on Tue, 09 Apr 2019 06:17:10
Thank you for your reply.
We have one final question - can you please confirm if ANH is currently making requests to android.googleapis.com?
This was the specific issue raised by Firebase and we need to know if we should keep investigating further, to see if any of our apps or services are making a request to this uri.
Dave_MU on Thu, 18 Apr 2019 12:30:04
I too recently received this same email.
Can you confirm whether this is dependent on what version of the Microsoft.Azure.NotificationHubs Nuget package is being used please? And if so, what version should we be using in order for requests to be made to the required FCM endpoints?
If it's not dependent on the Nuget version and is purely internal at the Notifications Hub end, is there going to be an announcement made to inform people once the internal transition has been completed?
johnwargo on Wed, 24 Apr 2019 17:19:48
That was a temporary glitch, we noticed a problem and were fixing it when Google sent that email. We wrote about it here: https://docs.microsoft.com/en-us/azure/notification-hubs/notification-hubs-gcm-to-fcm. and there's a blog post on the topic going live this morning.
Dave_MU on Wed, 01 May 2019 07:41:33
Excellent, thanks for the update.