Migrate Android SDK to (or later)

Implement GCM behavior for the new specification


Due to changes in the way that Android handles GCM, if you are migrating the Android SDK from an earlier release to (or later), you must make a few changes to the AndroidManifest.xml.

To get started, make sure you have a release of the Android SDK before installed on your app.


Add Job Service
Release included an additional service to support jobs on Android O and later. You will need to integrate that if you're not already on Add the following new service to AndroidManifest.xml:

<service android:name=”co.acoustic.mobile.push.sdk.job.MceJobService” android:permission=”android.permission.BIND_JOB_SERVICE”/>

FCM Users
If you are using FCM and are migrating the Android SDK from an earlier release to (or later), you do not need to make any further changes. The MceJobService service is sufficient.

Cordova Users

If you are migrating the Cordova build from an earlier release to one later than 3.5.0, you must make the changes described in this tutorial when setting up the Android project. For more information, see Getting started with apps developed with Cordova.

For more information about integrating the Mobile App Messaging SDK with your Android app, see Getting started with Mobile App Messaging in Android Apps that use Firebase Cloud Messaging (FCM).