This article details the preparations needed to be carried out in order to prepare your app to Google's migration from GCM to FCM.
As of April 11th, 2019, Google will be deprecating the Google Could Messaging (GCM) service, use in order to send Push notifications to Mobile devices.
Google Cloud Messaging (GCM) is a mobile notification service developed by Google that enables third-party application developers to send notification data or information from developer-run servers to applications that target the Google Android Operating System
As such, this service is used also by third-party push notification services such as, for example, Airship.
In order to continue to be able to send Push Notifications in your app after the above mentioned date, you are required to Migrate GCM apps to Firebase Cloud Messaging (FCM).
Checklist of required elements:
|FCM Server Key|
|Firebase Configuration JSON|
Pre-requisites to Support FCM:
|Applicaster Android SDK||Version 8.0.0 and above|
|Android Urban Airship Plugin||Version 2.0 and above|
Here are the steps that need to be carried out in your Applicaster app:
1) Enter the Firebase Console that corresponds to your account, and click on the relevant Project, to open its' dashboard:
2) Once inside the Dashboard, click on the Settings button , and then on the "Project settings" option from the popup menu:
3) Once inside the "Settings" screen, click on the Cloud "Messaging Tab".
Make sure that your Server Key starts with "AAAA......".
This indicates it supports Firebase Cloud Messaging.
i- If it does, please skip to Step #6
ii- If your Server Key starts with any other prefix (for example "AIza....."), it means that you have an Old GCM Server key that needs to be updated. Please continue to Step #4.
4) Click on the Trash Can icon to the right of the old Server Key.
The following message will popup:
Click on "Delete" to confirm
5) Now, click on the "Add server key" button in order to Generate a New Server Key that supports the FCM standard.
You will now see that you have a New FCM Server Key:
6) Click on the "General" tab in the Settings screen:
7) Scroll down to the "Your apps" section, and make sure your Android App is selected.
8) Click on the "google-services.json" button.
The Firebase Configuration JSON File will now download to your computer.
9) Go to the App Builder (https://zapp.applicaster.com/) and open the Zapp configurations section for your app:
10) Click on the "Edit App" section at the top of the screen:
11) Make sure that your Firebase Sender ID and your Firebase Server Key, correspond to what you have configured in the "Cloud Messaging" section of the Firebase console:
12) Click on "Update App".
13) Return to your Version and click on the "General" option from the version drop-down menu:
14) Scroll down to the "Other Settings" section and upload your Configurations JSON file in the field called "Firebase Configuration.
Click on "Save"
Once uploaded, you will see the field populated with the wording "google-services.json"
15) You can now create a new Android Build of your app version, by clicking on the "Build" button, and following the usual processes.
16) In order to continue sending pushes via Airship -
Send the FCM Server key to the Applicaster Support team, so that they will configure it in your Airship account.
Without this final configuration, pushes will not be able to be sent via the Airship third-party provider.
You're ready to "push"!