Minimum AppGyver client versions required:
- Android 4.0.4-edge3
- iOS 4.0.0
N.B. Push Notifications require a real device!
This plugin is for use with AppGyver Supersonic, and allows your application to receive push notifications on both Android and iOS devices. The Android implementation uses Google's GCM (Google Cloud Messaging) service, whereas the iOS version is based on Apple APNS Notifications
Important - Push notifications are intended for real devices. The registration process will fail on the iOS simulator. Notifications can be made to work on the Android Emulator. However, doing so requires installation of some helper libraries, as outlined here, under the section titled "Installing helper libraries and setting up the Emulator".
Deploy your application to the AppGyver Build Service and click "[X] Push Notifications" under "Configuration". Then create a new custom Scanner/AdHoc build. It include this plugin with your certificates.
Please follow the guide for Push Notifications which will help you to create the required Push Notification certificates for Apple APNS and Google GCM API keys.
First, create the plugin instance variable:
var pushNotification;When the deviceready event fires, get the plugin reference:
document.addEventListener("deviceready", function() {
pushNotification = window.plugins.pushNotification;
});Call this to register the device to receive push notifications.
The callback returns the device token (iOS) / registration id (Android)
Those values will typically get posted to your intermediary push server so it knows who it can send notifications to.
senderID (Android only) - The senderID can be defined in the config.android.xml or passed in the API call. This is the Google project ID you need to obtain by registering your application for GCM
// the result contains any error description text returned from the plugin call
function errorHandler (error) {
alert('error = ' + error);
}
function registrationHandler (deviceToken) {
alert('deviceToken = ' + deviceToken);
//save the deviceToken / registration ID to your Push Notification Server
}
pushNotification.register(
registrationHandler,
errorHandler, {
//android options
"senderID":"1234567891011",
//ios options
"badge":"true",
"sound":"true",
"alert":"true"
});Alternatively, you can set the sender ID it in config.android.xml:
<preference name="GCM_SenderId" value="1234567891011" />// result contains any error description text returned from the plugin call
function errorHandler (error) {
alert('error = ' + error);
}
function messageInForegroundHandler (notification) {
//handle the contents of the notification
console.log(notification.message || notification.alert);
if ( event.sound ) {
var snd = new Media(event.sound);
snd.play();
}
if ( event.badge ) {
pushNotification.setApplicationIconBadgeNumber(function(){...}, function(){...}, event.badge);
}
}
pushNotification.onMessageInForeground(
messageInForegroundHandler,
errorHandler);You can use steroids.app.absolutePath to build a file path that works on both platforms iOS and Android
//handle the difference in payload from iOS and Android
var sound = notification.sound || notification.soundname;
var media = new Media(steroids.app.absolutePath + '/' + sound);
media.play();You will need to include the sound file in your Steroids application project. steroids.app.absolutePath points to the internal directory which has the contents of the dist folder of your Steroids application.
// result contains any error description text returned from the plugin call
function errorHandler (error) {
alert('error = ' + error);
}
function messageInBackgroundHandler (notification) {
if (notification.coldstart) {
// ios, this is always true
// the application was started by the user tapping on the notification
}
else {
//this notification was delived while the app was in background
}
//handle the contents of the notification
var message = notification.message || notification.alert;
...
}
pushNotification.onMessageInBackground(
messageInBackgroundHandler,
errorHandler);Also make note of the payload object. Since the Android notification data model is much more flexible than that of iOS, there may be additional elements beyond message, soundname, and msgcnt. You can access those elements and any additional ones via the payload element. This means that if your data model should change in the future, there will be no need to change and recompile the plugin.
You will typically call this when your app is exiting, to cleanup any used resources. Its not strictly necessary to call it, and indeed it may be desireable to NOT call it if you are debugging your intermediarry push server. When you call unregister(), the current token for a particular device will get invalidated, and the next call to register() will return a new token. If you do NOT call unregister(), the last token will remain in effect until it is invalidated for some reason at the GCM side. Since such invalidations are beyond your control, its recommended that, in a production environment, that you have a matching unregister() call, for every call to register(), and that your server updates the devices' records each time.
pushNotification.unregister(successHandler, errorHandler);set the badge count visible when the app is not running
pushNotification.setApplicationIconBadgeNumber(successCallback, errorCallback, badgeCount);badgeCount - an integer indicating what number should show up in the badge. Passing 0 will clear the badge.
For Android, If you have not already done so, you'll need to set up a Google API project, to generate your senderID. Follow these steps to do so. This is described more fully in the Test Environment section below.
In this example, be sure and substitute your own senderID. Get your senderID by signing into to your google dashboard. The senderID is found at Overview->Dashboard->Project Number.
The notification system consists of several interdependent components.
-
The client application which runs on a device and receives notifications.
-
The notification service provider (APNS for Apple, GCM for Google)
-
Intermediary servers that collect device IDs from clients and push notifications through APNS and/or GCM.
This plugin and its target Steroids application comprise the client application.The APNS and GCM infrastructure are maintained by Apple and Google, respectively. In order to send push notifications to your users, you would typically run an intermediary server or employ a 3rd party push service. This is true for both GCM (Android) and APNS (iOS) notifications. However, when testing the notification client applications, it may be desirable to be able to push notifications directly from your desktop, without having to design and build those server's first. There are a number of solutions out there to allow you to push from a desktop machine, sans server. The easiest I've found to work with is a ruby gem called pushmeup. I've only tried this on Mac, but it probably works fine on Windows as well. Here's a rough outline;
Prerequisites.
-
Ruby gems is installed and working.
-
You have successfully built a client with this plugin, on both iOS and Android and have installed them on a device.
1) Get the gem
$ sudo gem install pushmeup
Create the push notification certificate as instructed in the guide and convert the generated aps_development.p12 file as ck.pem file.
a) go the this plugin's Example/server folder and open pushAPNS.rb in the text editor of your choice.
b) set the APNS.pem variable to the path of the ck.pem file you just created
c) set APNS.pass to the password associated with the certificate you just created. (warning this is cleartext, so don't share this file)
d) set device_token to the token for the device you want to send a push to. (you can run the Cordova app / plugin in Xcode and extract the token from the log messages)
e) save your changes.
3) (Android) Follow the AppGyver Push Notification Guide
Do these steps in Google's GCM documentation to generate a project ID and a server based API key.
a) go the this plugin's Example/server folder and open pushGCM.rb in the text editor of your choice.
b) set the GCM.key variable to the API key you just generated.
c) set the destination variable to the Registration ID of the device. (you can run the Cordova app / plugin in on a device via Eclipse and extract the regID from the log messages)
a) cd to the directory containing the two .rb files we just edited.
b) Run the Cordova app / plugin on both the Android and iOS devices you used to obtain the regID / device token, respectively.
c) $ ruby pushGCM.rb
d) $ ruby pushAPNS.rb
If all went well, you should see a notification show up on each device. If not, make sure you are not being blocked by a firewall, and that you have internet access. Check and recheck the token id, the registration ID and the certificate generating process.
In a production environment, your app, upon registration, would send the device id (iOS) or the registration id (Android), to your intermediary push server. For iOS, the push certificate would also be stored there, and would be used to authenticate push requests to the APNS server. When a push request is processed, this information is then used to target specific apps running on individual devices.
f you're not up to building and maintaining your own intermediary push server, there are a number of commercial push services out there which support both APNS and GCM.
Amazon SNS with Push Messaging
If you run this demo using the emulator you will not receive notifications from GCM. You need to run it on an actual device to receive messages or install the proper libraries on your emulator (You can follow this guide under the section titled "Installing helper libraries and setting up the Emulator")
If everything seems right and you are not receiving a registration id response back from Google, try uninstalling and reinstalling your app. That has worked for some devs out there.
While the data model for iOS is somewhat fixed, it should be noted that GCM is far more flexible. The Android implementation in this plugin, for example, assumes the incoming message will contain a 'message' and a 'msgcnt' node. This is reflected in both the plugin (see GCMIntentService.java) as well as in provided example ruby script (pushGCM.rb). Should you employ a commercial service, their data model may differ. As mentioned earlier, this is where you will want to take a look at the payload element of the message event. In addition to the cannonical message and msgcnt elements, any additional elements in the incoming JSON object will be accessible here, obviating the need to edit and recompile the plugin. Many thanks to Tobias Hößl for this functionality!
AppGyver guide for Push Notifications will help you to create the required Push Notification certificates for Apple APNS and Google GCM API keys.
Local and Push Notification Programming Guide (Apple)
Google Cloud Messaging for Android (Android)
Apple Push Notification Services Tutorial: Part 1/2
Apple Push Notification Services Tutorial: Part 2/2
How to Implement Push Notifications for Android
This Plugin is based on Cordova PushPlugin.
Huge thanks to Mark Nutter whose GCM-Cordova plugin forms the basis for the Android side implimentation.
Likewise, the iOS side was inspired by Olivier Louvignes' Cordova PushNotification Plugin (Copyright (c) 2012 Olivier Louvignes) for iOS.
Props to Tobias Hößl, who provided the code to surface the full JSON object up to the JS layer.
The MIT License
Copyright (c) 2014 AppGyver Inc. (c) 2012 Adobe Systems, inc. portions Copyright (c) 2012 Olivier Louvignes
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.