324 lines (229 sloc) 13.9 KB


Installation Requirements

Plugin version Cordova CLI Cordova Android Cordova iOS CocoaPods
1.9.0 6.4.0 6.0.0 4.3.0 1.1.1
1.8.0 3.6.3 4.0.0 4.1.0 N/A

To install from the command line:

phonegap plugin add phonegap-plugin-push --variable SENDER_ID="XXXXXXX"


cordova plugin add phonegap-plugin-push --variable SENDER_ID="XXXXXXX"

It is also possible to install via repo url directly ( unstable )

phonegap plugin add --variable SENDER_ID="XXXXXXX"


cordova plugin add --variable SENDER_ID="XXXXXXX"

Where the XXXXXXX in SENDER_ID="XXXXXXX" maps to the project number in the Google Developer Console. To find the project number login to the Google Developer Console, select your project and click the menu item in the screen shot below to display your project number.


If you are not creating an Android application you can put in anything for this value.

Note: if you are using Ionic you may need to specify the SENDER_ID variable in your package.json.

  "cordovaPlugins": [
      "variables": {
        "SENDER_ID": "XXXXXXX"
      "locator": "phonegap-plugin-push"

Note: You need to specify the SENDER_ID variable in your config.xml if you plan on installing/restoring plugins using the prepare method. The prepare method will skip installing the plugin otherwise.

<plugin name="phonegap-plugin-push" spec="1.6.0">
    <param name="SENDER_ID" value="XXXXXXX" />

Android details


As of version 1.3.0 the plugin has been switched to using Gradle/Maven for building.

You will need to ensure that you have installed the following items through the Android SDK Manager:

  • Android Support Library version 23 or greater
  • Local Maven repository for Support Libraries (formerly Android Support Repository) version 20 or greater
  • Google Play Services version 27 or greater
  • Google Repository version 22 or greater

android support library

For more detailed instructions on how to install the Android Support Library visit Google's documentation.

Note: if you are using an IDE to like Eclipse, Xamarin, etc. then the Android SDK installed by those tools may not be the same version as the one used by the Cordova/PhoneGap CLI while building. Please make sure your command line tooling is up to date with the software versions above. An easy way to make sure you up to date is to run the following command:

android update sdk --no-ui --filter "extra"

Co-existing with Facebook Plugin

There are a number of Cordova Facebook Plugins available but the one that we recommend is Jeduan's fork of the original Wizcorp plugin. It is setup to use Gradle/Maven and the latest Facebook SDK properly.

To add to your app:

phonegap plugin add --save cordova-plugin-facebook4 --variable APP_ID="App ID" --variable APP_NAME="App Name"


cordova plugin add --save cordova-plugin-facebook4 --variable APP_ID="App ID" --variable APP_NAME="App Name"

Common errors

minSdkVersion === 14

If you have an issue compiling the app and you are getting an error similar to this:

* What went wrong:
Execution failed for task ':processDebugManifest'.
> Manifest merger failed : uses-sdk:minSdkVersion 14 cannot be smaller than version 15 declared in library .../platforms/android/build/intermediates/exploded-aar/
    Suggestion: use tools:overrideLibrary="com.facebook" to force usage

Then you can add the following entry into your config.xml file in the android platform tag:

<platform name="android">
    <preference name="android-minSdkVersion" value="15"/>

or compile your project using the following command, if the solution above doesn't work for you. Basically add -- --minSdkVersion=15 to the end of the command line (mind the extra --, it's needed):

cordova compile android -- --minSdkVersion=15
cordova build android -- --minSdkVersion=15
cordova run android -- --minSdkVersion=15
cordova emulate android -- --minSdkVersion=15


If you have an issue compiling the app and you're getting an error similar to this ( Multiple dex files define):

UNEXPECTED TOP-LEVEL EXCEPTION: Multiple dex files define Landroid/support/annotation/AnimRes;

Then at least one other plugin you have installed is using an outdated way to declare dependencies such as android-support or play-services-gcm. This causes gradle to fail, and you'll need to identify which plugin is causing it and request an update to the plugin author, so that it uses the proper way to declare dependencies for cordova. See this for the reference on the cordova plugin specification, it'll be usefull to mention it when creating an issue or requesting that plugin to be updated.

Common plugins to suffer from this outdated dependency management are plugins related to facebook, google+, notifications, crosswalk and google maps.

More than one library with package name ''

When some other packages include cordova-google-play-services as a dependency, such as is the case with the cordova-admob and cordova-plugin-analytics plugins, it is impossible to also add the phonegap-plugin-push, for the following error will rise during the build process:

:processDebugResources FAILED
FAILURE: Build failed with an exception.

What went wrong: Execution failed for task ':processDebugResources'. > Error: more than one library with package name ''

Those plugins should be using gradle to include the Google Play Services package but instead they include the play services jar directly or via a plugin dependency. So all of that is bad news. These plugins should be updated to use gradle. Please raise issues on those plugins as the change is not hard to make.

In fact there is a PR open to do just that appfeel/analytics-google#11 for cordova-plugin-analytics. You should bug the team at appfeel to merge that PR.

Alternatively, switch to another plugin that provides the same functionality but uses gradle:

Browser details

Browser quirks

For the time being push support on the browser will only work using the PhoneGap push server.

When you run phonegap serve to test browser push point your browser at http://localhost:3000. The browser push implementation uses the W3C Push Spec's implementation which relies on ServiceWorkers and ServiceWorkers can only be accessed via the https protocol or via http://localhost. Pointing your browser at localhost will be the easiest way to test.

Browser Support

Chrome 49+ Firefox 46+

iOS details


Xcode version 8.0 or greater is required for building this plugin.


If you are running into a problem where the linker is complaining about bit code. For instance:

ld: '<file.o>' does not contain bitcode. You must rebuild it with bitcode enabled (Xcode setting ENABLE_BITCODE), obtain an updated library from the vendor, or disable bitcode for this target. for architecture arm64 clang: error: linker command failed with exit code 1 (use -v to see invocation)

You have two options. The first is to disable bitcode as per this StackOverflow answer or upgrade to cordova-ios 4 or greater.

cordova platform update ios@4.0.0


Required cordova-cli version: 6.4.0

Required cordova-ios version: 4.3.0

Version 1.9.0 (and above) of this plugin supports CocoaPods installation of the Google Cloud Messaging library.

If you are installing this plugin using npm, and you are using version 6.1.0 or greater of the cordova-cli, it will automatically download the right version of this plugin for both your platform and cli.

If you are on a cordova-cli version less than 6.1.0, you will either have to upgrade your cordova-cli version, or install the plugin explicitly:


cordova plugin add phonegap-plugin-push@1.8.1

If you are installing this plugin using a local file reference or a git url, you will have to specify the version of this plugin explicitly (see above) if you don't fulfill the cordova-cli and cordova-ios requirements.

Common CocoaPod Installation issues

If you are attempting to install this plugin and you run into this error:

Installing "phonegap-plugin-push" for ios
Failed to install 'phonegap-plugin-push':Error: pod: Command failed with exit code 1
    at ChildProcess.whenDone (/Users/smacdona/code/push151/platforms/ios/cordova/node_modules/cordova-common/src/superspawn.js:169:23)
    at emitTwo (events.js:87:13)
    at ChildProcess.emit (events.js:172:7)
    at maybeClose (internal/child_process.js:818:16)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:211:5)
Error: pod: Command failed with exit code 1

Please run the command pod repo update and re-install the plugin.

CocoaPod Disk Space

Running pod setup can take over 1 GB of disk space and that can take quite some time to download over a slow internet connection. If you are having issues with disk space/network try this neat hack from @VinceOPS.

git clone --verbose --depth=1 ~/.cocoapods/repos/master
pod setup --verbose

Additional Resources

The push plugin enables you to play sounds and display different icons during push (Android only). These additional resources need to be added to your projects platforms directory in order for them to be included into your final application binary. One way of doing it is to create a hook to do the copying for you on each build.

First create a scripts directory in the root of your project. Next add a file to the scripts directory called copy_resource_files.js. The contents of the file will look something like this:

#!/usr/bin/env node

// each object in the array consists of a key which refers to the source and
// the value which is the destination.
var filestocopy = [{
}, {
}, {
}, ];

var fs = require('fs');
var path = require('path');

// no need to configure below
var rootdir = process.argv[2];

filestocopy.forEach(function(obj) {
    Object.keys(obj).forEach(function(key) {
        var val = obj[key];
        var srcfile = path.join(rootdir, key);
        var destfile = path.join(rootdir, val);
        //console.log("copying "+srcfile+" to "+destfile);
        var destdir = path.dirname(destfile);
        if (fs.existsSync(srcfile) && fs.existsSync(destdir)) {

Obviously, you'll need to modify the filestocopy variable to suit your needs. Pay attention to the destination path on iOS where you will need to replace YourAppName.

Next open up your config.xml file and add the following line:

<hook type="before_build" src="scripts/copy_resource_files.js" />

Now, when you build your app the files will get copied into your platforms directory for you.

If you are using PhoneGap Build check out these instructions on Additional Resources