it would be neat if we could create our own push plugin which would then leverage the native client sdk's for registration.

although,  i'm not sure how "plugin" friendly our libs are since they depend on other things.  and the main point of cordova is to hide the "Native" code.  

so never mind then.   i already committed to writing this out  ;)

On Jul 15, 2013, at 11:23 AM, Lucas Holmquist <> wrote:

On Jul 15, 2013, at 11:20 AM, Matthias Wessendorf <> wrote:

On Mon, Jul 15, 2013 at 5:11 PM, Lucas Holmquist <> wrote:

On Jul 13, 2013, at 10:54 AM, Matthias Wessendorf <> wrote:


today I played with Apache Cordova, the PushPlugin, AeroGear.js (Notifier branch) and our UnifiedPush Server.


These steps from the iOS Tutorial are required for an iOS-Cordova app as well:

  • Apple App ID and SSL Certificate for APNs
  • Apple Provisioning Profile
  • The AeroGear Unified Push Server

TL;DR: You need a new App-ID, a SSL-cert and a provisioning profile (for that APP-ID). On the UnifiedPush Server, you need a PushApplication and an iOS Variant :-)

Cordova stuff


Get the Cordova PushPlugin (there is a downloadable tarball) and extract the tarball to some location.

Cordova App

Creating a Corodva app is simple:

cordova create FolderOfTheApp AppName
cd FolderOfTheApp
cordova platform add ios
cordova plugin add folder_of_PushPlugin-1.3.3

HINT: Make sure your Apple ID matches the above "" value...

  • Install aerogear.js (checkout (and build) the Notifier branch) and jquery.min.js -> I basically copied the files into the "www" folder;

afterwards build the project:

cordova build

Now open the generated Xcode project, and start "hacking".

This all works well. However, I had to do some "hack" to be able to use the registerWithPushServer()function:

var tokenContainer = {};
tokenContainer.channelID = deviceToken;

That is because the JS does expect the token/channelID as the above ".channelID". I am sure that can be made a bit more flexible.

Also, the "metadata" currently is only able to specify the following values:

  • deviceToken
  • alias
  • category

I am sure we can make it more generic here as well.

So again, without too much work, I got it working:

However I had some issues.


I had to copy the ObjC bits by hand. See here.

  • Uncaught TypeError: Cannot read property 'simplePushServerURL' of undefined aerogear.js:955 (anonymous function) aerogear.js:955 (anonymous function)

    • at least in the browser.... However, I could remove it, on the Corodva app .... and the app still seams to work.... So, not sure :-)
  • looks like the Notifier branch requires sockjs Uncaught ReferenceError: SockJS is not defined aerogear.js:942 (anonymous function)

    • But again in the browser...., I could remove that "import" in my Cordova app. So, not sure here too :-)

The (ugly) code is posted on my GH account.

I guess we could convert this into a more "official" guide/tutorial at some point. This email should give some hints on getting started.

Another question:

Perhaps we want to fork the PushPlugin and stick our AeroGear.js bits in there? So that all is ready ? I am not sure, just some idea.

So This plugin is actually part of phone gap build,  Which means people can get it easy.  but at the same time,  these types of plugins aren't as fast to upgrade

They include an example ruby "push server" in the example code.  

Ah :-) So, if there are other plugins, let me know :) I just picked that one for my tests

i've only used that one and thats because you told me about it  ;)


I'm not sure how others feel about it,  but i can be convinced of forking a copy,  and then adding in our stuff,  as well as adding a "FFOS" version that we could maybe contribute back upstream.  

I am also fine with (for now) just having "instructions", that should pretty much do the trick - at least I was also able to use it that way. (Android try-out will follow "soon")

In one of the Phone Gap Day workshops, they are going to be talking about push notifications. so i'll report back.

sweet! I am happy to hear more on what you've learned / heard there.

Thanks for the feedback, Luke!


aerogear-dev mailing list

aerogear-dev mailing list

Matthias Wessendorf

aerogear-dev mailing list

aerogear-dev mailing list