You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/notification-hubs/notification-hubs-android-push-notification-google-fcm-get-started.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,5 @@
1
1
---
2
-
title: Send push notifications to Android using Azure Notification Hubs and Firebase Cloud Messaging | Microsoft Docs
2
+
title: Send push notifications to Android using Azure Notification Hubs and Firebase | Microsoft Docs
3
3
description: In this tutorial, you learn how to use Azure Notification Hubs and Google Firebase Cloud Messaging to push notifications to Android devices.
4
4
services: notification-hubs
5
5
documentationcenter: android
@@ -21,7 +21,7 @@ ms.reviewer: jowargo
21
21
ms.lastreviewed: 09/11/2019
22
22
---
23
23
24
-
# Tutorial: Send push notifications to Android devices using Google Firebase Cloud Messaging
24
+
# Tutorial: Send push notifications to Android devices using Firebase
Copy file name to clipboardExpand all lines: articles/notification-hubs/notification-hubs-aspnet-backend-android-xplat-segmented-gcm-push-notification.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,7 +20,7 @@ ms.reviewer: jowargo
20
20
ms.lastreviewed: 01/04/2019
21
21
---
22
22
23
-
# Tutorial: Push notifications to specific Android devices using Azure Notification Hubs and Google Cloud Messaging (deprecated)
23
+
# Tutorial: Send push notifications to specific Android devices using Google Cloud Messaging (deprecated)
24
24
25
25
> [!WARNING]
26
26
> As of April 10, 2018, Google has deprecated Google Cloud Messaging (GCM). The GCM server and client APIs are deprecated and will be removed as soon as May 29, 2019. For more information, see [GCM and FCM Frequently Asked Questions](https://developers.google.com/cloud-messaging/faq).
Copy file name to clipboardExpand all lines: articles/notification-hubs/notification-hubs-aspnet-backend-gcm-android-push-to-user-google-notification.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,7 +20,7 @@ ms.reviewer: jowargo
20
20
ms.lastreviewed: 01/04/2019
21
21
---
22
22
23
-
# Tutorial: Push notification to specific Android application users by using Azure Notification Hubs and Google Cloud Messaging (deprecated)
23
+
# Tutorial: Send push notification to specific Android users using Azure Notification Hubs and Google Cloud Messaging (deprecated)
24
24
25
25
> [!WARNING]
26
26
> As of April 10, 2018, Google has deprecated Google Cloud Messaging (GCM). The GCM server and client APIs are deprecated and will be removed as soon as May 29, 2019. For more information, see [GCM and FCM Frequently Asked Questions](https://developers.google.com/cloud-messaging/faq).
Copy file name to clipboardExpand all lines: articles/notification-hubs/notification-hubs-aspnet-cross-platform-notification.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -19,7 +19,7 @@ ms.reviewer: jowargo
19
19
ms.lastreviewed: 10/02/2019
20
20
---
21
21
22
-
# Send cross-platform notifications to users with Notification Hubs
22
+
# Send cross-platform notifications with Azure Notification Hubs
23
23
24
24
This tutorial builds on the previous tutorial, [Send notifications to specific users by using Azure Notification Hubs]. That tutorial describes how to push notifications to all devices that are registered to a specific authenticated user. That approach required multiple requests to send a notification to each supported client platform. Azure Notification Hubs supports templates, with which you can specify how a specific device wants to receive notifications. This method simplifies sending cross-platform notifications.
Copy file name to clipboardExpand all lines: articles/notification-hubs/notification-hubs-gcm-to-fcm.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,29 +17,29 @@ ms.reviewer: jowargo
17
17
ms.lastreviewed: 04/10/2019
18
18
---
19
19
20
-
# Azure Notification Hubs and the Google Firebase Cloud Messaging (FCM) migration
20
+
# Azure Notification Hubs and Google Firebase Cloud Messaging migration
21
21
22
22
## Current state
23
23
24
24
When Google announced its migration from Google Cloud Messaging (GCM) to Firebase Cloud Messaging (FCM), push services like ours had to adjust how we sent notifications to Android devices to accommodate the change.
25
25
26
26
We updated our service backend, then published updates to our API and SDKs as needed. With our implementation, we made the decision to maintain compatibility with existing GCM notification schemas to minimize customer impact. This means that we currently send notifications to Android devices using FCM in FCM Legacy Mode. Ultimately, we want to add true support for FCM, including the new features and payload format. That is a longer-term change and the current migration is focused on maintaining compatibility with existing applications and SDKs. You can use either the GCM or FCM SDKs in your app (along with our SDK) and we make sure the notification is sent correctly.
27
27
28
-
Some customers recently received an email from Google warning about apps using a GCM endpoint for notifications. This was just a warning, and nothing is broken – your app’s Android notifications are still sent to Google for processing and Google still processes them. Some customers who specified the GCM endpoint explicitly in their service configuration were still using the deprecated endpoint. We had already identified this gap and were working on fixing the issue when Google sent the email.
28
+
Some customers recently received an email from Google warning about apps using a GCM endpoint for notifications. This was just a warning, and nothing is broken – your app's Android notifications are still sent to Google for processing and Google still processes them. Some customers who specified the GCM endpoint explicitly in their service configuration were still using the deprecated endpoint. We had already identified this gap and were working on fixing the issue when Google sent the email.
29
29
30
30
We replaced that deprecated endpoint and the fix is deployed.
31
31
32
32
## Going forward
33
33
34
-
Google’s FCM FAQ says you don't have to do anything. In the [FCM FAQ](https://developers.google.com/cloud-messaging/faq), Google said "client SDKs and GCM tokens will continue to work indefinitely. However, you won't be able to target the latest version of Google Play Services in your Android app unless you migrate to FCM."
34
+
Google's FCM FAQ says you don't have to do anything. In the [FCM FAQ](https://developers.google.com/cloud-messaging/faq), Google said "client SDKs and GCM tokens will continue to work indefinitely. However, you won't be able to target the latest version of Google Play Services in your Android app unless you migrate to FCM."
35
35
36
-
If your app uses the GCM library, go ahead and follow Google’s instructions to upgrade to the FCM library in your app. Our SDK is compatible with either, so you won’t have to update anything in your app on our side (as long as you’re up to date with our SDK version).
36
+
If your app uses the GCM library, go ahead and follow Google's instructions to upgrade to the FCM library in your app. Our SDK is compatible with either, so you won't have to update anything in your app on our side (as long as you're up to date with our SDK version).
37
37
38
38
## Questions and answers
39
39
40
-
Here’s some answers to common questions we’ve heard from customers:
40
+
Here's some answers to common questions we've heard from customers:
41
41
42
-
**Q:** What do I need to do to be compatible by the cutoff date (Google’s current cutoff date is May 29th and may change)?
42
+
**Q:** What do I need to do to be compatible by the cutoff date (Google's current cutoff date is May 29th and may change)?
43
43
44
44
**A:** Nothing. We will maintain compatibility with existing GCM notification schema. Your GCM key will continue to work as normal as will any GCM SDKs and libraries used by your application.
0 commit comments