10:32 a.m.
My next round of testing, when is onNotification called, please help me think through the
scenarios
1) Android: when the app is up and in the foreground - yes
2) iOS: when the app is up and in the foreground - yes
3) Android: when the app is not on - yes (user killed the app)
4) iOS: when the app is not on - yes (user killed the app)
5) Android: when device is on its "lock screen"/screen off - yes - android
vibrates
6) * iOS: when device is on its "lock screen"/screen off - sometimes - iOS
displays message on lock screen
7) Android: when app is on but in the background - yes
8) ** iOS: when app is on but in the background - NO
* seems to depend on how long the device has had its screen off
** this one seems to be a problem - as demonstrated in this video
http://screencast.com/t/gtORCvRtNy
It seems to me that the iOS app, in the background, should still have its onNotification
method called to update its UI
My sample project deployed across all devices
https://github.com/burrsutter/hellopush
On Jan 29, 2014, at 9:59 AM, Jay Balunas <jbalunas(a)redhat.com> wrote:
Wow, this is a detailed investigation! Thanks a lot for digging in
like this and the jiras!
I think getting these addressed, and other UX items for getting started is a big priority
for us going forward. As well as how to catch these issues sooner.
On Jan 28, 2014, at 6:05 PM, Burr Sutter <bsutter(a)redhat.com> wrote:
> OK, the real gotcha was...
> https://issues.jboss.org/browse/AGPUSH-525
>
> There were some smaller issues:
> - I found the readme.md to be inaccurate
> - the video is incomplete http://www.youtube.com/watch?v=a7QVWfEkSpc
> i watched it several times last week, pausing, trying to tease out the commands
needed to replicate the experience
> - I believe iOS also requires the console plugin be installed - as device ready was
failing due to the console.log the sample app contains.
> - Hand editing the config.xml to provide the App Name and package/bundleID I wanted
did not seem to "stick" - I was better off using the command line like so:
> cordova create hellopush com.burrsutter.hellopush "Hello Push"
> instead
> cordova create hellopush and editing the config.xml that was generated
>
> on Android 2.3, the app loads but blows up on launch
> https://issues.jboss.org/browse/AGPUSH-526
>
> And there is inconsistency between iOS and Android
> https://issues.jboss.org/browse/AGPUSH-527
>
> And can we "hide" the older UPS docs that focus on curl and bring the ones
that focus on the web UI to the foreground?
> For instance, at the bottom of this page:
> http://aerogear.org/docs/guides/aerogear-push-android/google-setup/
> it links to the curl version - curl is great, but more of an advanced topic
> this is the doc that needs more link love
> http://aerogear.org/docs/guides/AdminConsoleGuide/
>
>
> I attempted to document the complete set of steps in my readme.txt
> https://github.com/burrsutter/hellopush
>
> I suspect I forgot something along the way
>
>
> On Jan 28, 2014, at 1:25 PM, Burr Sutter <bsutter(a)redhat.com> wrote:
>
>> https://github.com/aerogear/aerogear-pushplugin-cordova/
>> My project/notes in the readme.md - it could be that I have missed a step, so I
tried to describe my steps carefully in the readme, everything from the command line right
now - I will attempt JBoss Tools once the command line steps seem to work.
>> https://github.com/burrsutter/hellopush
>>
>> I have also tested with
>> https://github.com/edewit/aerogear-pushplugin-cordova/tree/agdroid-195
>>
>> It only works on Android 4.3, funny enough that was the first device I tried -
perhaps there is some "affinity" for a single device? :-)
>>
>> It fails on:
>> Android 2.3.4
>> Android 4.4.2 (two different devices)
>> iOS 6.1.5
>> iOS 7.0.4
>>
>> Let's define "fail":
>> - the app always deploys but...
>> - the additional devices never register a device token in the UPS console. I
assume I will see "instances" for the various devices
>> - in the case of iOS, the deviceready does not even fire correctly
>> - in the case of Android (all versions), the onError handler is called with
"no value for pushconfig" - including the 4.3 where things do work.
>>
>>
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev