[Aerogear-users] Possible bug in Aerogear Push Cordova/iOS implementation but not in the Cordova/Android version

[rob Willett]

Erik,

We have built our own test using a cordova startup, much the same as you 
have outlined below, using our own JS code and it works OK. We get the 
same results.

However when we run our app (with the code from above) we still get the 
same error as before.

So clearly the Aerogear plugin does work and something in our code, or 
in the Ionic framework we are using, is causing a problem specifically 
to IOS. We spent a couple of hours late yesterday going through our code 
trying to see what, if anything was causing the issue but nothing 
positive emerged.

So the problem is ours to solve, we will keep looking at pulling code 
out until it works. We’ll also reproduce the simple test but using the 
Ionic framework to see if thats the problem. Our thinking has to be that 
its our code and theres some sort of race or timing condition we are 
introducing.

Thanks again, sadly we have a lot of work to do today.

Best wishes,

Rob

On 15 Dec 2015, at 10:36, Erik Jan de Wit wrote:

> Hi Rob,
>
> That would be a bug, although I can not reproduce it, to test it this 
> is
> what I've done to test it:
>
> $ > cordova create push-test <my bundle id>
> $ > cordova platform add ios
> $ > cordova plugin add aerogear-cordova-push
>
> copy paste your js code into www/js/index.js onDeviceReady, changed
> pushServerUrl and variant info and changed quotes to " (this is your 
> email
> client no doubt) and changed : into ; after console.log("Success")
>
>
> Attach Safari debugger and send a message when the app is in the 
> foreground
> and get in the console:
>
> HandleAeroGearNotification: event =>
> {"alert":"test","foreground":true,"coldstart":false,"sound":"default","badge":-1,"payload":{}}
>
> I press the home button and send the app to the background send 
> another
> message and 'touch' the message to launch the app:
>
> HandleAeroGearNotification: event =>
> {"alert":"background","foreground":false,"coldstart":false,"sound":"default","badge":-1,"payload":{}}
>
> The I kill the app by pressing home twice and swiping over the app to
> remove it send another message and 'touch' it to launch the app. This 
> kills
> my safari debugger so no way to see the console log, but in this case
> coldstart should be true. To test this better changed the code to 
> alert
> instead of console:
>
> function HandleAeroGearNotification(event) {
> alert("HandleAeroGearNotification: event => " + event.coldstart);
>
> // Stuff cut for clarity
> }
>
> I send another notification 'touch' it to launch the app and see the 
> alert
> box display the text:
>
> HandleAeroGearNotification: event => true
>
> Hope this helps
>
>
>
> On Mon, Dec 14, 2015 at 10:20 PM, Rob Willett <
> rob.aerogear at robertwillett.com> wrote:
>
>> Hi,
>>
>> We think we have found a possible bug in the Aerogear Cordova 2.0.4 
>> push
>> plugin specifically on the iOS side.
>> Summary
>>
>> We have two versions of our app, an Android and an IOS version. Both 
>> use
>> the latest Cordova push plugin 2.0.4. They also both have the latest
>> Cordova platforms, android 4.1.1, ios 3.9.2. Both the iOS and Android
>> versions are compiled at the same time. We are running cordova 5.3.3 
>> with
>> Ionic 1.7.8 (?).
>>
>> 1.
>>
>> We make sure that both apps are NOT started up on each device. We 
>> also
>> check they are NOT in the background.
>> 2.
>>
>> We send the same simple notification to each device. This 
>> notification
>> config is as below, we have anonymised the variants and alias in this 
>> JSON
>> structure, though we can report that the UPS server sends the data
>> correctly. We use the additionalData flag to provide the information
>> necessary to decide which notification has been clicked in the 
>> notification
>> drawer.
>>
>> 'variants' => [‘variant1’,’variant2’ ],
>> 'message' => {
>> 'additionalData' => { 'Disruption_Id' => '107546',
>>                    'EpochTime' => '1450125268'
>>                   },
>> 'alert' => 'Cannon Street (EC4N) (All Directions) at the junction of 
>> King William Street - To facilitate a heavy lift in Cannon Street, 
>> Cannon Street will be closed. Traffic is slow moving on diversion.' 
>> },
>> 'alias' => [ ‘alias1’ ],
>> 'ttl' => 600
>> };
>>
>>
>> 1.
>>
>> Both devices show the message, the Android device stacks the message
>> and the iOS device display an individual message. This looks correct.
>> 2.
>>
>> Clicking on the Android stacked message starts up the app and the
>> Javascript notification handler we have defined, 
>> HandleAeroGearNotification
>> is called
>>
>> HandleAeroGearNotification: event => {"alert":"Cannon Street (EC4N) 
>> (All Directions) at the junction of King William Street - To 
>> facilitate a heavy lift in Cannon Street, Cannon Street will be 
>> closed. Traffic is slow moving on 
>> diversion.","coldstart":true,"foreground":true,"payload":{"alert":"Cannon 
>> Street (EC4N) (All Directions) at the junction of King William Street 
>> - To facilitate a heavy lift in Cannon Street, Cannon Street will be 
>> closed. Traffic is slow moving on diversion.","badge":"-1"}}
>>
>>
>> 1.
>>
>> Clicking on the notification in the notification drawer on the iOS
>> device also starts our app up correctly but the notification handler,
>> HandleAeroGearNotification(), is NOT called. The app starts up as 
>> normal as
>> if the notification had not been clicked. We would expect the 
>> notification
>> handler to be called in iOS as it is in Android.
>> 2.
>>
>> All notifications are cleared on both Android and iOS correctly when
>> the app is started up.
>> 3.
>>
>> We define HandleAeroGearNotification as
>>
>>
>> var aeroGearPushConfig = {
>>   pushServerURL: "https://push-jambuster.rhcloud.com/ag-push/",
>>   ios: {
>>       variantID: “variantid_obscured”,
>>        variantSecret: “variant_secret_obscured”
>>       } ,
>>    android: {
>>           senderID: "variantid_obscured" ,
>>       variantID: "variant_id_obscured" ,
>>       variantSecret: "variant_secret_obscured"
>>    } ,
>>   sendMetricInfo: true,
>>   alias: alias1
>> };
>>
>> function HandleAeroGearNotification(event) {
>>   console.log(“HandleAeroGearNotification: event => “ + 
>> JSON.stringify(event));
>>
>>   // Stuff cut for clarity
>> }
>>
>> // Slightly simplified registration event.
>> push.register(HandleAeroGearNotification , function () {
>>   console.log(“Success”):
>> } , function () {
>>   console.log(“Failure”);
>> } , aeroGearPushConfig);
>>
>> We cannot see any reference to this issue in the JIRA database and
>> wondered if it is a bug or not.
>>
>> If its a bug we are happy to raise it accordingly.
>>
>> Please let us know,
>>
>> Thanks
>>
>> Rob
>>
>> _______________________________________________
>> Aerogear-users mailing list
>> Aerogear-users at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-users
>>
>>
>
>
> -- 
> Cheers,
>  Erik Jan
> _______________________________________________
> Aerogear-users mailing list
> Aerogear-users at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-users