This is the second of a four-part tutorial on setting up a mobile backend as a service on Amazon and setting up iOS and Android client applications to enable push notification. If you want to setup Push Notifications for an iOS app refer to Part 3.

If you have done so already, please go to Part One to setup your backend LoopBack application server on Amazon.


This article provides information on creating Android apps that can get push notifications from a LoopBack application.

To enable an Android app to receive LoopBack push notifications:

  • Setup your android client app to use Google Play Services.
  • On app startup, register with GCM servers to obtain a device registration ID (device token) and register the device with the LoopBack server application.
  • Configure your LoopBack application to receive incoming messages from GCM.
  • Process the notifications received.


Before you start developing your application make sure you’ve performed all the prerequisite steps outlined in this section.

Configure Android Development Tools

Now configure Eclipse ADT as follows:

  1. Open Eclipse from the downloaded ADT bundle.
  2. In ADT, choose: Window > Android SDK Manager
  3. Install the following if they are not already installed:


  • Android SDK Platform-tools 18 or newer
  • Android SDK Build-tools 18 or newer</span>

Android 4.3 (API 18)

  • SDK Platform
  • Google APIs


  • Google Play Services
  • Intel x86 Emulator Accelerator (HAXM)

Before you start, make sure you have set up at least one Android virtual device: Choose Window > Android Virtual Device Manager.

Configure the target virtual device as shown in the screenshot below. See AVD Manager for more information.

NOTE: If you are using the virtual device suggested above, you must also install the ARM EABI v7a System Image SDK.

Get your Google Cloud Messaging credentials##

To send push notifications to your Android app, you need to setup a Google API project and enable the Google Cloud Messaging (GCM) service.

Follow the instructions to get your GCM credentials:

  1. Follow steps to create a Google API project and enable the GCM service.

  2. Create an Android API key.
  3. You also have to create a new server API key that will be used by the LoopBack server:
    • Click “Create new key”
    • Select “Server key”
    • Leave the list of allowed IP addresses empty for now.
    • Click “Create”
    • Copy down the API key.  Later you will use this when you configure the LoopBack server application.

Configure GCM push settings in your server application##

Add the following key and value to the push settings of your application in the config.js file:

  gcm: {
    serverApiKey: "server-api-key"

Replace server-api-key with the API key you obtained in the section Get your Google Cloud Messaging credentials.

NOTE: If you want to try a sample client application follow steps in “Install and run LoopBack Push Notification app” OR if you want to enable push notifications for your own android application using the LoopBack SDK follow steps in “Prepare your own Android project”.

Install and run LoopBack Push Notification app##

If you want to use the sample Android client app, download the  Push Notification Example Android app. Then follow these steps to run the app:

a. Open ADT Eclipse.</span> b. Import the push notification application to your workspace:

  • Choose “File > Import”
  • Choose “Android > Existing Android Code into Workspace”
  • Click “Next”
  • Browse to the example Android app you just downloaded.
  • Click “Finish”.
NOTE: ADT does not take long to import the guide app. Don’t be misguided by the progress bar at the bottom of the IDE window: it indicates memory use, not loading status.
  1. Import Google Play Services library project into your workspace. The project is located inside the directory where you have installed the Android SDK.
  • Choose “File > Import”
  • Choose “Android > Existing Android Code into Workspace”
  • Click “Next”
  • Browse to the <android-sdk>/extras/google/google_play_services/libproject/google-play-services_lib directory.
  • Check “Copy projects into workspace”
  • Click “Finish”

See Google Play Services SDK for more details.

  • Add the imported google-play-services_lib as an Android build dependency of the push notification application.
  • In the Package Explorer frame in Eclipse, select the  push notification application. – Choose “File > Properties” – Select “Android” – In the Library frame, click on “Add…” and select google-play-services_lib. – Also under Project Build Target, set the target as Google APIs.

  • Edit src/com/google/android/gcm/demo/app/
  • Set SENDER_ID to the project number from the Google Developers Console you created earlier in Get your Google Cloud Messaging credentials.
  • Go back to the and edit the Android Key to reflect your unique application ID. Set the value of “Android applications” to something like this:

Android applications



  • Set the appName in the server application’s config.js to “”.
  • Edit src/com/google/android/gcm/demo/app/
  • Set adaptor to our server ip. In my case it is:
adapter = new RestAdapter(

Click the green “Run” button in the toolbar to run the application. Run it as an Android application. You will be prompted to select the target on which to run the application. Select the AVD you created earlier.

It may take several minutes to launch your application and the Android virtual device the first time.

Due to a known issue with Google Play Services, you must download and import an older version of Google Play services. 

  • Download
  • Extract the zip file.
  • In Eclipse ADT, right-click on your project and choose Import
  • Choose Existing Android Code into Workspace then click Next.
  • Click Browse
  • Browse to the google-play-services/libproject/google-play-services_lib/ directory created when you extracted the zip file and select it in the dialog box.
  • Click Finish.

You must also update AndroidManifest.xml as follows:

  1. In Eclipse ADT, browse to DemoActivity/AndroidManifest.xml.
  2. Change the line:

<meta-data <a>android:name="</a>" <a>android:value="@integer/google_play_services_version"/</a>>


<meta-data <a>android:name="</a>" <a>android:value="4030500”/</a>>

  1. Save the file.

Prepare your own Android project##

Follow the instructions in Android SDK documentation to add LoopBack Android SDK to your Android project.

Follow the instructions in Google’s Implementing GCM Client guide for setting up Google Play Services in your project.

To use push notifications, you must install a compatible version of the Google APIs platform.  To test your app on the emulator, expand the directory for Android 4.2.2 (API 17) or a higher version, select Google APIs, and install it. Then create a new AVD with Google APIs as the platform target.  You must install the package from the SDK manager.  For more information, see Set Up Google Play Services.

Check for Google Play Services APK##

Applications that rely on the Google Play Services SDK should always check the device for a compatible Google Play services APK before using Google Cloud Messaging.

For example, the following code checks the device for Google Play Services APK by calling checkPlayServices() if  this method returns true, it proceeds with GCM registration. The checkPlayServices() method checks whether the device has the Google Play Services APK. If it doesn’t, it displays a dialog that allows users to download the APK from the Google Play Store or enables it in the device’s system settings.

public void onCreate(final Bundle savedInstanceState) {

    if (checkPlayServices()) {
    } else {
        Log.i(TAG, "No valid Google Play Services APK found.");
private boolean checkPlayServices() {
    int resultCode = GooglePlayServicesUtil.isGooglePlayServicesAvailable(this);
    if (resultCode != ConnectionResult.SUCCESS) {
        if (GooglePlayServicesUtil.isUserRecoverableError(resultCode)) {
            GooglePlayServicesUtil.getErrorDialog(resultCode, this,
        } else {
            Log.i(TAG, "This device is not supported.");
        return false;
    return true;

Create LocalInstallation##

Once you have ensured the device provides Google Play Services, the app can register with GCM and LoopBack (for example, by calling a method such as updateRegistration() as shown below). Rather than register with GCM every time the app starts, simply store and retrieve the registration ID (device token).  The LocalInstallation class in the LoopBack SDK handles these details for you.

The example updateRegistration() method does the following:

  • Lines 3 – 4: get a reference to the shared RestAdapter instance.
  • Line 5: Create an instance of LocalInstallation.
  • Line 13: Subscribe to topics.
  • Lines 15-19: Check if there is a valid GCM registration ID.  If so, then save the installation to the server; if not, get one from GCM and then save the installation.
private void updateRegistration() {

    final DemoApplication app = (DemoApplication) getApplication();
    final RestAdapter adapter = app.getLoopBackAdapter();
    final LocalInstallation installation = new LocalInstallation(context, adapter);

    // Substitute the real ID of the LoopBack application as created by the server

    // Substitute a real ID of the user logged in to the application

    installation.setSubscriptions(new String[] { "all" });

    if (installation.getDeviceToken() != null) {
    } else {

Register with GCM if needed##

In the following code, the application obtains a new registration ID from GCM. Because the register() method is blocking, you must call it on a background thread.

private void registerInBackground(final LocalInstallation installation) {
    new AsyncTask<Void, Void, Exception>() {
        protected Exception doInBackground(final Void... params) {
            try {
                GoogleCloudMessaging gcm = GoogleCloudMessaging.getInstance(this);
                // substitute 12345 with the real Google API Project number 
				final String regid = gcm.register("12345");
                return null;
            } catch (final IOException ex) {
                return ex;
                // If there is an error, don't just keep trying to
                // register.
                // Require the user to click a button again, or perform
                // exponential back-off.
        protected void onPostExecute(final Exception error) {
            if (err != null) {
                Log.e(TAG, "GCM Registration failed.", error);
            } else {
    }.execute(null, null, null);

Register with LoopBack server##

Once you have all Installation properties set, you can register with the LoopBack server. The first run of the application should create a new Installation record, subsequent runs should update this existing record. The LoopBack Android SDK handles the details. Your code just needs to call1save().

void saveInstallation(final LocalInstallation installation) { Model.Callback() {
        public void onSuccess() {
            // Installation was saved.
            // You can access the id assigned by the server via
            //   installation.getId();
        public void onError(final Throwable t) {
            Log.e(TAG, "Cannot save Installation", t);

Handle received notifications##

Android apps handle incoming notifications in the standard way; LoopBack does not require any special changes. For more information, see the section “Receive a message” of Google’s Implementing GCM Client guide.


When running your app in the Eclipse device emulator, you may encounter the following error:

Google Play services, which some of your applications rely on, is not supported by your device. Please contact the manufacturer for assistance.

To resolve this, install a compatible version of the Google APIs platform.

Next Steps##

  • To setup and create an iOS app to receive push notifications go to Part Three
  • To use LoopBack’s swagger REST api and send/receive push notifications on your Android and iOS devices go to Part Four