Localytics Home

Articles in this section

See more

Migrating from GCM to FCM

Google recently announced that it would be deprecating Google Cloud Messaging (GCM) in favor of Firebase Cloud Messaging (FCM). As a result, we are advising all customers to update their Android apps from using GCM to using FCM if necessary.

Determining Which Push Service Your App Uses

Your developers should be able to tell you if your Android app is currently using GCM or FCM.

Alternatively, you can use Rapid Push Verification to see which service your app currently uses. To do this, go to Settings in the Localytics Dashboard, find the app you are interested in and click the blue button that says Test Push Integration. Once you get to Step 3 and scan the QR code, you should see a screen that looks like the image below. The push service your app currently uses can be found in the bottom left corner:

 

RPV_FCM_indicator.png

Keep in mind, Rapid Push Verification only works if you have test mode properly integrated into your app. If you try to use Rapid Push Verification and nothing happens when you scan the QR code in Step 3, then it means your app doesn’t have test mode integrated. Your developer will need to follow the instructions for integrating test mode before you can use Rapid Push Verification.

Migrating to FCM

Generally, Google’s migration guide should be followed. However, we will add a few additional notes to ensure your Localytics integration should still be compliant.

  1. Ensure that your app is integrated with SDK v5 or higher.
  2. Follow steps 1 and 2 of the Google Migration guide.
    1. NOTE: It is vital that you follow Step 2 of Google's instructions—you must select your existing GCM project from the list of existing Google Cloud Projects and add it to Firebase. If you just create a new Firebase project and don't move the GCM project over, you will lose the ability to send pushes to all existing users.
  3. Follow step 3, but please don’t remove the wake lock block as suggested by Google:
<uses-permission android:name "android.permission.WAKE_LOCK" />
  1. Update your push receivers (this step assumes SDK 5+):
    a. Remove the ll_gcm_sender_id key from your localytics.xml.
    b. For customers who use Localytics push receivers and services set ll_fcm_push_services_enabledto true.
    c. For customers who use custom push receivers, update your old receivers to extend the Firebase push services FirebaseInstanceIdService and FirebaseMessagingService.
    Google provides migration guides on these steps here and here.
If your app tags push received manually, make sure you are on SDK 5.2. This version of the SDK adds a convenience method that accepts a Map instead of a Bundle.

This integration covers Native Android integrations, in addition to the React-Native and Cordova wrappers. For Xamarin, please consult Microsoft’s documentation.

Server Integration

Firebase continues to support GCM Server API keys. If you still have an active GCM Server key as provided by Google, that key should continue to work in the Localytics system, and it is not required to upload anything new to the Localytics dashboard.

Testing

Once you have a new build of the app, please take a moment to use Rapid Push Verification to ensure your push integration is behaving properly. Once again, Rapid Push Verification relies on proper test mode integration.