From scm.blanc at gmail.com  Mon Jun  1 02:01:40 2015
From: scm.blanc at gmail.com (Sebastien Blanc)
Date: Mon, 1 Jun 2015 08:01:40 +0200
Subject: [aerogear-dev] Sndroid Background push notifications not working
In-Reply-To: <1433106128657-11716.post@n5.nabble.com>
References: <1433106128657-11716.post@n5.nabble.com>
Message-ID: <CAD_dpu1zdmuWGy+s3K5tmsP58R2s4G1=pxNvdqWjeKW9XyK3fQ@mail.gmail.com>

Are you using the AeroGear Pushplugin or the "classic" one (pushplugin) ?

Anyway, could you check that this is set in your manifest :
https://github.com/jboss-mobile/unified-push-helloworld/blob/8e8b7fbdae50826265e1c22222d8a1b9a27e0b14/android/app/src/main/AndroidManifest.xml#L63
, that make sure you message arrives even when the app is not started (but
our plugin should set this for you)


On Sun, May 31, 2015 at 11:02 PM, delalis <delalis at gmail.com> wrote:

> Hello, Aerogear is sending android push notifications properly when the app
> is open (foreground) on an android device and the onNotificationGCM()
> function is being called successfully when the app is open.  But it is not
> even putting a notification in the system notification tray when the app is
> in the background or not running at all...
>
> We are using phonegap and pushplugin on the client side and a lot of people
> on google are saying that if the server is not constructing the message
> payload structure properly, then Android devices will not create a
> notification in the android notification tray.
>
> Any suggestions???
>
> here is the link I found during my research suggesting maybe Aerogear isnt
> structuring message payloads properly for background notifications tray
> alerts...(scroll to bottom)
>
>
> http://community.phonegap.com/nitobi/topics/_pushplugin_background_notifications_dont_seem_to_work
>
>
>
>
> --
> View this message in context:
> http://aerogear-dev.1069024.n5.nabble.com/Sndroid-Background-push-notifications-not-working-tp11716.html
> Sent from the aerogear-dev mailing list archive at Nabble.com.
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150601/54284169/attachment.html 

From edewit at redhat.com  Mon Jun  1 04:04:46 2015
From: edewit at redhat.com (Erik Jan de Wit)
Date: Mon, 1 Jun 2015 10:04:46 +0200
Subject: [aerogear-dev] Android Background push notifications not working
In-Reply-To: <1433106639731-11717.post@n5.nabble.com>
References: <1433106128657-11716.post@n5.nabble.com>
	<1433106639731-11717.post@n5.nabble.com>
Message-ID: <CAO2B-fbG=LYposXrMnJ5uLs1qoiv1tOXoP9Q83uixaF2kO6WXw@mail.gmail.com>

This thread on SO seem to be about Apigee and the phonegap push
plugin[1], so not related to AeroGear at all. What is your problem?


[1] https://github.com/phonegap-build/PushPlugin

On Sun, May 31, 2015 at 11:10 PM, delalis <delalis at gmail.com> wrote:
> This post also talks about a "message" variable needing to be present
>
> http://stackoverflow.com/questions/22889969/apigee-push-notifications-on-android-not-delivered-when-app-in-background-phone
>
> we are using Aerogear 1.0.3
>
>
>
> --
> View this message in context: http://aerogear-dev.1069024.n5.nabble.com/Android-Background-push-notifications-not-working-tp11716p11717.html
> Sent from the aerogear-dev mailing list archive at Nabble.com.
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev



-- 
Cheers,
       Erik Jan

From edewit at redhat.com  Mon Jun  1 04:06:57 2015
From: edewit at redhat.com (Erik Jan de Wit)
Date: Mon, 1 Jun 2015 10:06:57 +0200
Subject: [aerogear-dev] Sndroid Background push notifications not working
In-Reply-To: <CAD_dpu1zdmuWGy+s3K5tmsP58R2s4G1=pxNvdqWjeKW9XyK3fQ@mail.gmail.com>
References: <1433106128657-11716.post@n5.nabble.com>
	<CAD_dpu1zdmuWGy+s3K5tmsP58R2s4G1=pxNvdqWjeKW9XyK3fQ@mail.gmail.com>
Message-ID: <CAO2B-fY9U9kiWci0BYpHVO3ZxfhUYuQBv_RYi3Ph=iRK5++T+A@mail.gmail.com>

I would suggest following this guide to setup the client
https://aerogear.org/docs/guides/aerogear-cordova/AerogearCordovaPush/

On Mon, Jun 1, 2015 at 8:01 AM, Sebastien Blanc <scm.blanc at gmail.com> wrote:
> Are you using the AeroGear Pushplugin or the "classic" one (pushplugin) ?
>
> Anyway, could you check that this is set in your manifest :
> https://github.com/jboss-mobile/unified-push-helloworld/blob/8e8b7fbdae50826265e1c22222d8a1b9a27e0b14/android/app/src/main/AndroidManifest.xml#L63
> , that make sure you message arrives even when the app is not started (but
> our plugin should set this for you)
>
>
> On Sun, May 31, 2015 at 11:02 PM, delalis <delalis at gmail.com> wrote:
>>
>> Hello, Aerogear is sending android push notifications properly when the
>> app
>> is open (foreground) on an android device and the onNotificationGCM()
>> function is being called successfully when the app is open.  But it is not
>> even putting a notification in the system notification tray when the app
>> is
>> in the background or not running at all...
>>
>> We are using phonegap and pushplugin on the client side and a lot of
>> people
>> on google are saying that if the server is not constructing the message
>> payload structure properly, then Android devices will not create a
>> notification in the android notification tray.
>>
>> Any suggestions???
>>
>> here is the link I found during my research suggesting maybe Aerogear isnt
>> structuring message payloads properly for background notifications tray
>> alerts...(scroll to bottom)
>>
>>
>> http://community.phonegap.com/nitobi/topics/_pushplugin_background_notifications_dont_seem_to_work
>>
>>
>>
>>
>> --
>> View this message in context:
>> http://aerogear-dev.1069024.n5.nabble.com/Sndroid-Background-push-notifications-not-working-tp11716.html
>> Sent from the aerogear-dev mailing list archive at Nabble.com.
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev



-- 
Cheers,
       Erik Jan

From delalis at gmail.com  Mon Jun  1 09:01:30 2015
From: delalis at gmail.com (delalis)
Date: Mon, 1 Jun 2015 06:01:30 -0700 (MST)
Subject: [aerogear-dev] Sndroid Background push notifications not working
In-Reply-To: <CAO2B-fY9U9kiWci0BYpHVO3ZxfhUYuQBv_RYi3Ph=iRK5++T+A@mail.gmail.com>
References: <1433106128657-11716.post@n5.nabble.com>
	<CAD_dpu1zdmuWGy+s3K5tmsP58R2s4G1=pxNvdqWjeKW9XyK3fQ@mail.gmail.com>
	<CAO2B-fY9U9kiWci0BYpHVO3ZxfhUYuQBv_RYi3Ph=iRK5++T+A@mail.gmail.com>
Message-ID: <1433163690514-11721.post@n5.nabble.com>

Had no idea this plugin existed.  Thanks guys!  I'll let you know if it
works.  @sblanc, thanks for the manifest line, but I think we'll just try
installing the aerogear pushplugin completely just for compatibility sake.



--
View this message in context: http://aerogear-dev.1069024.n5.nabble.com/Android-Background-push-notifications-not-working-tp11716p11721.html
Sent from the aerogear-dev mailing list archive at Nabble.com.

From delalis at gmail.com  Mon Jun  1 10:10:52 2015
From: delalis at gmail.com (delalis)
Date: Mon, 1 Jun 2015 07:10:52 -0700 (MST)
Subject: [aerogear-dev] Sndroid Background push notifications not working
In-Reply-To: <1433163690514-11721.post@n5.nabble.com>
References: <1433106128657-11716.post@n5.nabble.com>
	<CAD_dpu1zdmuWGy+s3K5tmsP58R2s4G1=pxNvdqWjeKW9XyK3fQ@mail.gmail.com>
	<CAO2B-fY9U9kiWci0BYpHVO3ZxfhUYuQBv_RYi3Ph=iRK5++T+A@mail.gmail.com>
	<1433163690514-11721.post@n5.nabble.com>
Message-ID: <1433167852411-11722.post@n5.nabble.com>

I tried installing the aerogear client push plugin using your first option in
that guide:

 cordova plugin add org.jboss.aerogear.cordova.push

and it is giving errors in the manifest.xml saying ACCESS_NETWORK_STATE at 
AndroidManifest.xml:27:5 duplicated with element declared at
AndroidManifest.xml

Googled and found that it is already an issue:

https://issues.jboss.org/browse/AGCORDOVA-72

So, I am going to try installing the "latest and greatest" dev version using
this command instead:

cordova plugin add
https://github.com/aerogear/aerogear-pushplugin-cordova.git



--
View this message in context: http://aerogear-dev.1069024.n5.nabble.com/Android-Background-push-notifications-not-working-tp11716p11722.html
Sent from the aerogear-dev mailing list archive at Nabble.com.

From delalis at gmail.com  Mon Jun  1 10:13:43 2015
From: delalis at gmail.com (delalis)
Date: Mon, 1 Jun 2015 07:13:43 -0700 (MST)
Subject: [aerogear-dev] Sndroid Background push notifications not working
In-Reply-To: <1433167852411-11722.post@n5.nabble.com>
References: <1433106128657-11716.post@n5.nabble.com>
	<CAD_dpu1zdmuWGy+s3K5tmsP58R2s4G1=pxNvdqWjeKW9XyK3fQ@mail.gmail.com>
	<CAO2B-fY9U9kiWci0BYpHVO3ZxfhUYuQBv_RYi3Ph=iRK5++T+A@mail.gmail.com>
	<1433163690514-11721.post@n5.nabble.com>
	<1433167852411-11722.post@n5.nabble.com>
Message-ID: <1433168023446-11723.post@n5.nabble.com>

tried the github version and still receiving the same error on build



--
View this message in context: http://aerogear-dev.1069024.n5.nabble.com/Android-Background-push-notifications-not-working-tp11716p11723.html
Sent from the aerogear-dev mailing list archive at Nabble.com.

From delalis at gmail.com  Mon Jun  1 10:19:14 2015
From: delalis at gmail.com (delalis)
Date: Mon, 1 Jun 2015 07:19:14 -0700 (MST)
Subject: [aerogear-dev] Sndroid Background push notifications not working
In-Reply-To: <1433168023446-11723.post@n5.nabble.com>
References: <1433106128657-11716.post@n5.nabble.com>
	<CAD_dpu1zdmuWGy+s3K5tmsP58R2s4G1=pxNvdqWjeKW9XyK3fQ@mail.gmail.com>
	<CAO2B-fY9U9kiWci0BYpHVO3ZxfhUYuQBv_RYi3Ph=iRK5++T+A@mail.gmail.com>
	<1433163690514-11721.post@n5.nabble.com>
	<1433167852411-11722.post@n5.nabble.com>
	<1433168023446-11723.post@n5.nabble.com>
Message-ID: <1433168354338-11724.post@n5.nabble.com>

We're thinking it could be caused by the network-information plugin already
adding that ACCESS_NETWORK_STATE line to the manifest




--
View this message in context: http://aerogear-dev.1069024.n5.nabble.com/Android-Background-push-notifications-not-working-tp11716p11724.html
Sent from the aerogear-dev mailing list archive at Nabble.com.

From edewit at redhat.com  Mon Jun  1 11:22:41 2015
From: edewit at redhat.com (Erik Jan de Wit)
Date: Mon, 1 Jun 2015 17:22:41 +0200
Subject: [aerogear-dev] Sndroid Background push notifications not working
In-Reply-To: <1433168354338-11724.post@n5.nabble.com>
References: <1433106128657-11716.post@n5.nabble.com>
	<CAD_dpu1zdmuWGy+s3K5tmsP58R2s4G1=pxNvdqWjeKW9XyK3fQ@mail.gmail.com>
	<CAO2B-fY9U9kiWci0BYpHVO3ZxfhUYuQBv_RYi3Ph=iRK5++T+A@mail.gmail.com>
	<1433163690514-11721.post@n5.nabble.com>
	<1433167852411-11722.post@n5.nabble.com>
	<1433168023446-11723.post@n5.nabble.com>
	<1433168354338-11724.post@n5.nabble.com>
Message-ID: <CAO2B-fYtA65vxOV1d8iVnv7AcOmVqo+7tvZFCjq7zWJPyraGvw@mail.gmail.com>

this is introduced by cordova 4 you'll have to open the manifest file
and remove the line by hand. It's been fixed but in an open pr

On Mon, Jun 1, 2015 at 4:19 PM, delalis <delalis at gmail.com> wrote:
> We're thinking it could be caused by the network-information plugin already
> adding that ACCESS_NETWORK_STATE line to the manifest
>
>
>
>
> --
> View this message in context: http://aerogear-dev.1069024.n5.nabble.com/Android-Background-push-notifications-not-working-tp11716p11724.html
> Sent from the aerogear-dev mailing list archive at Nabble.com.
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev



-- 
Cheers,
       Erik Jan

From corinnekrych at gmail.com  Mon Jun  1 11:33:59 2015
From: corinnekrych at gmail.com (Corinne Krych)
Date: Mon, 1 Jun 2015 17:33:59 +0200
Subject: [aerogear-dev] What's new in AeroGear (1st June)
Message-ID: <5194E03B-7D29-48A0-899D-8B61A497B57C@gmail.com>

Hello

This week in AeroGear land, we?ve got a new release in preparation! 
UnifiedPush Server 1.1-Beta2. Beta2 should go out next week and will be the last before 1.1.0-Final Yay ! 

If you want to know more on our client SDKs side, pick your personal flavor:

Android geeks:
Push analytics has been released

iOS lovers:
Since last week, Travis is ready for Swift 1.2, you can read more on http://blog.travis-ci.com/2015-05-26-xcode-63-beta-general-availability/.
We're so pleased to see a green status for our Swift libraires.
Next week, we'll work on ios-push library to simplify configuration and get prepared for UPS 1.1.0.beta.2. You can follow progress on  https://issues.jboss.org/browse/AGPUSH-1430

JavaScripters:
While there is nothing released in JS lib, here are the topics we are paying attention to:
- Polymer 1.0 released - http://googledevelopers.blogspot.co.uk/2015/05/polymer-10-released.html
- Angular 1.4.0 released - http://angularjs.blogspot.com/2015/05/angular-140-jaracimrman-existence.html
- JSON API spec is now at 1.0 http://jsonapi.org
- Node.js and iO.js will be getting back together - https://github.com/nodejs/io.js/issues/978

Windows Phone nerds:
Rejoy 1.1.0.beta.1 release of push sdk has been released with support for metrics.

Cordova developers:
Last week, we had a new security release of our Cordova plugins. If you missed it, please look at https://aerogear.org/news/2015/05/29/aerogear-cordova-security-release/index.html. 
The cookbook examples will be revisited and properly tagged if necessary this week.
 
As always feel free to interact with us on mailing list and stay tuned.

++
Corinne
iOS lover





From mazz0016 at gmail.com  Mon Jun  1 11:52:50 2015
From: mazz0016 at gmail.com (mazz0016)
Date: Mon, 1 Jun 2015 08:52:50 -0700 (MST)
Subject: [aerogear-dev] Sndroid Background push notifications not working
In-Reply-To: <CAO2B-fYtA65vxOV1d8iVnv7AcOmVqo+7tvZFCjq7zWJPyraGvw@mail.gmail.com>
References: <1433106128657-11716.post@n5.nabble.com>
	<CAD_dpu1zdmuWGy+s3K5tmsP58R2s4G1=pxNvdqWjeKW9XyK3fQ@mail.gmail.com>
	<CAO2B-fY9U9kiWci0BYpHVO3ZxfhUYuQBv_RYi3Ph=iRK5++T+A@mail.gmail.com>
	<1433163690514-11721.post@n5.nabble.com>
	<1433167852411-11722.post@n5.nabble.com>
	<1433168023446-11723.post@n5.nabble.com>
	<1433168354338-11724.post@n5.nabble.com>
	<CAO2B-fYtA65vxOV1d8iVnv7AcOmVqo+7tvZFCjq7zWJPyraGvw@mail.gmail.com>
Message-ID: <1433173970945-11727.post@n5.nabble.com>

Hello, I'm working with delalis to get this running and I have tried removing
the line from my manifest file. However the line is added back every time I
execute a build from the command line. And therefore cannot generate a
working APK.

Any suggestions? Have I missed something?



--
View this message in context: http://aerogear-dev.1069024.n5.nabble.com/Android-Background-push-notifications-not-working-tp11716p11727.html
Sent from the aerogear-dev mailing list archive at Nabble.com.

From scm.blanc at gmail.com  Mon Jun  1 12:46:57 2015
From: scm.blanc at gmail.com (Sebastien Blanc)
Date: Mon, 1 Jun 2015 18:46:57 +0200
Subject: [aerogear-dev] Sndroid Background push notifications not working
In-Reply-To: <1433173970945-11727.post@n5.nabble.com>
References: <1433106128657-11716.post@n5.nabble.com>
	<CAD_dpu1zdmuWGy+s3K5tmsP58R2s4G1=pxNvdqWjeKW9XyK3fQ@mail.gmail.com>
	<CAO2B-fY9U9kiWci0BYpHVO3ZxfhUYuQBv_RYi3Ph=iRK5++T+A@mail.gmail.com>
	<1433163690514-11721.post@n5.nabble.com>
	<1433167852411-11722.post@n5.nabble.com>
	<1433168023446-11723.post@n5.nabble.com>
	<1433168354338-11724.post@n5.nabble.com>
	<CAO2B-fYtA65vxOV1d8iVnv7AcOmVqo+7tvZFCjq7zWJPyraGvw@mail.gmail.com>
	<1433173970945-11727.post@n5.nabble.com>
Message-ID: <CAD_dpu3pX00593FLAojD7NzrsXxtFs56b0VHAoFt18g=o6UhEQ@mail.gmail.com>

Try to remove it from the plugin.xml of the plugin
https://github.com/aerogear/aerogear-cordova-push/blob/master/plugin.xml#L32
and not on the generated manifest file of your app.


On Mon, Jun 1, 2015 at 5:52 PM, mazz0016 <mazz0016 at gmail.com> wrote:

> Hello, I'm working with delalis to get this running and I have tried
> removing
> the line from my manifest file. However the line is added back every time I
> execute a build from the command line. And therefore cannot generate a
> working APK.
>
> Any suggestions? Have I missed something?
>
>
>
> --
> View this message in context:
> http://aerogear-dev.1069024.n5.nabble.com/Android-Background-push-notifications-not-working-tp11716p11727.html
> Sent from the aerogear-dev mailing list archive at Nabble.com.
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150601/0f600e82/attachment.html 

From delalis at gmail.com  Mon Jun  1 13:48:47 2015
From: delalis at gmail.com (delalis)
Date: Mon, 1 Jun 2015 10:48:47 -0700 (MST)
Subject: [aerogear-dev] Sndroid Background push notifications not working
In-Reply-To: <CAD_dpu3pX00593FLAojD7NzrsXxtFs56b0VHAoFt18g=o6UhEQ@mail.gmail.com>
References: <1433106128657-11716.post@n5.nabble.com>
	<CAD_dpu1zdmuWGy+s3K5tmsP58R2s4G1=pxNvdqWjeKW9XyK3fQ@mail.gmail.com>
	<CAO2B-fY9U9kiWci0BYpHVO3ZxfhUYuQBv_RYi3Ph=iRK5++T+A@mail.gmail.com>
	<1433163690514-11721.post@n5.nabble.com>
	<1433167852411-11722.post@n5.nabble.com>
	<1433168023446-11723.post@n5.nabble.com>
	<1433168354338-11724.post@n5.nabble.com>
	<CAO2B-fYtA65vxOV1d8iVnv7AcOmVqo+7tvZFCjq7zWJPyraGvw@mail.gmail.com>
	<1433173970945-11727.post@n5.nabble.com>
	<CAD_dpu3pX00593FLAojD7NzrsXxtFs56b0VHAoFt18g=o6UhEQ@mail.gmail.com>
Message-ID: <1433180927073-11729.post@n5.nabble.com>

Hi Sebastien, unfortunately removing the ACCESS_NETWORK_STATE from the
plugin's plugin.xml file does not stop it from adding this line to the
AndroidManifest.xml when running the "phonegap build android" command, and
we also tried "phonegap prepare android", which also added it back into the
manifest file.

Is there somewhere else we need to remove it from in order to stop it from
adding to the Android manifest xml?





--
View this message in context: http://aerogear-dev.1069024.n5.nabble.com/Android-Background-push-notifications-not-working-tp11716p11729.html
Sent from the aerogear-dev mailing list archive at Nabble.com.

From scm.blanc at gmail.com  Mon Jun  1 16:05:41 2015
From: scm.blanc at gmail.com (Sebastien Blanc)
Date: Mon, 1 Jun 2015 22:05:41 +0200
Subject: [aerogear-dev] Sndroid Background push notifications not working
In-Reply-To: <1433180927073-11729.post@n5.nabble.com>
References: <1433106128657-11716.post@n5.nabble.com>
	<CAD_dpu1zdmuWGy+s3K5tmsP58R2s4G1=pxNvdqWjeKW9XyK3fQ@mail.gmail.com>
	<CAO2B-fY9U9kiWci0BYpHVO3ZxfhUYuQBv_RYi3Ph=iRK5++T+A@mail.gmail.com>
	<1433163690514-11721.post@n5.nabble.com>
	<1433167852411-11722.post@n5.nabble.com>
	<1433168023446-11723.post@n5.nabble.com>
	<1433168354338-11724.post@n5.nabble.com>
	<CAO2B-fYtA65vxOV1d8iVnv7AcOmVqo+7tvZFCjq7zWJPyraGvw@mail.gmail.com>
	<1433173970945-11727.post@n5.nabble.com>
	<CAD_dpu3pX00593FLAojD7NzrsXxtFs56b0VHAoFt18g=o6UhEQ@mail.gmail.com>
	<1433180927073-11729.post@n5.nabble.com>
Message-ID: <CAD_dpu3NjfSSGBuDXVex6a5hupvv_TVm3qgrGXvwnvjc5uYrvw@mail.gmail.com>

hum ... strange, maybe Erik has the explanation, some caching stuff on
platform side .... you could try this : remove the plugin, remove the
android platform (phonegap platform rm android), add the plugin again,
change the plugin.xml and add the platform again :)

Otherwise you can't wait for Erik's fix that will be soon PRed (and this
way you can also review it ;) )

Sebi


On Mon, Jun 1, 2015 at 7:48 PM, delalis <delalis at gmail.com> wrote:

> Hi Sebastien, unfortunately removing the ACCESS_NETWORK_STATE from the
> plugin's plugin.xml file does not stop it from adding this line to the
> AndroidManifest.xml when running the "phonegap build android" command, and
> we also tried "phonegap prepare android", which also added it back into the
> manifest file.
>
> Is there somewhere else we need to remove it from in order to stop it from
> adding to the Android manifest xml?
>
>
>
>
>
> --
> View this message in context:
> http://aerogear-dev.1069024.n5.nabble.com/Android-Background-push-notifications-not-working-tp11716p11729.html
> Sent from the aerogear-dev mailing list archive at Nabble.com.
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150601/5c39d368/attachment.html 

From edewit at redhat.com  Tue Jun  2 02:03:51 2015
From: edewit at redhat.com (Erik Jan de Wit)
Date: Tue, 2 Jun 2015 08:03:51 +0200
Subject: [aerogear-dev] Sndroid Background push notifications not working
In-Reply-To: <CAD_dpu3NjfSSGBuDXVex6a5hupvv_TVm3qgrGXvwnvjc5uYrvw@mail.gmail.com>
References: <1433106128657-11716.post@n5.nabble.com>
	<CAD_dpu1zdmuWGy+s3K5tmsP58R2s4G1=pxNvdqWjeKW9XyK3fQ@mail.gmail.com>
	<CAO2B-fY9U9kiWci0BYpHVO3ZxfhUYuQBv_RYi3Ph=iRK5++T+A@mail.gmail.com>
	<1433163690514-11721.post@n5.nabble.com>
	<1433167852411-11722.post@n5.nabble.com>
	<1433168023446-11723.post@n5.nabble.com>
	<1433168354338-11724.post@n5.nabble.com>
	<CAO2B-fYtA65vxOV1d8iVnv7AcOmVqo+7tvZFCjq7zWJPyraGvw@mail.gmail.com>
	<1433173970945-11727.post@n5.nabble.com>
	<CAD_dpu3pX00593FLAojD7NzrsXxtFs56b0VHAoFt18g=o6UhEQ@mail.gmail.com>
	<1433180927073-11729.post@n5.nabble.com>
	<CAD_dpu3NjfSSGBuDXVex6a5hupvv_TVm3qgrGXvwnvjc5uYrvw@mail.gmail.com>
Message-ID: <CAO2B-fakcGpu_hK4YoPvny2ygG4xEtv4XMESeGZw3rQSB_cSww@mail.gmail.com>

all the things above should work, but if you are having a hard time
try and downgrade the android platform.

$> cordova platform add android at 3.6.4



On Mon, Jun 1, 2015 at 10:05 PM, Sebastien Blanc <scm.blanc at gmail.com> wrote:
> hum ... strange, maybe Erik has the explanation, some caching stuff on
> platform side .... you could try this : remove the plugin, remove the
> android platform (phonegap platform rm android), add the plugin again,
> change the plugin.xml and add the platform again :)
>
> Otherwise you can't wait for Erik's fix that will be soon PRed (and this way
> you can also review it ;) )
>
> Sebi
>
>
> On Mon, Jun 1, 2015 at 7:48 PM, delalis <delalis at gmail.com> wrote:
>>
>> Hi Sebastien, unfortunately removing the ACCESS_NETWORK_STATE from the
>> plugin's plugin.xml file does not stop it from adding this line to the
>> AndroidManifest.xml when running the "phonegap build android" command, and
>> we also tried "phonegap prepare android", which also added it back into
>> the
>> manifest file.
>>
>> Is there somewhere else we need to remove it from in order to stop it from
>> adding to the Android manifest xml?
>>
>>
>>
>>
>>
>> --
>> View this message in context:
>> http://aerogear-dev.1069024.n5.nabble.com/Android-Background-push-notifications-not-working-tp11716p11729.html
>> Sent from the aerogear-dev mailing list archive at Nabble.com.
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev



-- 
Cheers,
       Erik Jan

From matzew at apache.org  Tue Jun  2 12:09:56 2015
From: matzew at apache.org (Matthias Wessendorf)
Date: Tue, 2 Jun 2015 18:09:56 +0200
Subject: [aerogear-dev] APNS/UPS: With iOS 8.0 the 'alert' no longer just a
	string
Message-ID: <CAAg5f2Rdb_uFZdNYcw4_JgwzCOFxjBWkP_ncs81PDab0GrPSTA@mail.gmail.com>

Hi,

since iOS 8.0 we have the option for UI actions on the push notification:
http://cdn.iphonehacks.com/wp-content/uploads/2014/06/lock-screen-notifications.jpg

This is supported on java-apns and therefore on the UPS, however this
causes the alert to be an object, and not a String, if the 'action' is
provided.
Another feature that is leveraging this is the support for Safari, there is
a 'title' on the alert object, used by Apple Watch (iOS 8.3) as well.

Sending always an object from the UPS to the APNs cloud breaks the Cordova
code, since it's expecting a string.

On the UPS I could do construct the object only if things like title or
action are actually set. This would fix the issue on Cordova. However, this
means that our Cordova code would not support the 'action', introduced in
iOS 8.0


I can see a few options:
* for 1.1.0 -> do if/else and send object only if present. However, this
would still mean the Cordova plugin has to check if the alert is just a
string, to avoid crahes
* for 1.2.0 (or 1.1.x, if really needed) -> Add Cordova support for alert
being an object (helps for Apple Watch apps and supports the 'action')

Any thoughts or other options?

Thanks,
Matthias


-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150602/0ffecd1b/attachment-0001.html 

From delalis at gmail.com  Tue Jun  2 14:34:23 2015
From: delalis at gmail.com (delalis)
Date: Tue, 2 Jun 2015 11:34:23 -0700 (MST)
Subject: [aerogear-dev] Sndroid Background push notifications not working
In-Reply-To: <CAO2B-fakcGpu_hK4YoPvny2ygG4xEtv4XMESeGZw3rQSB_cSww@mail.gmail.com>
References: <1433163690514-11721.post@n5.nabble.com>
	<1433167852411-11722.post@n5.nabble.com>
	<1433168023446-11723.post@n5.nabble.com>
	<1433168354338-11724.post@n5.nabble.com>
	<CAO2B-fYtA65vxOV1d8iVnv7AcOmVqo+7tvZFCjq7zWJPyraGvw@mail.gmail.com>
	<1433173970945-11727.post@n5.nabble.com>
	<CAD_dpu3pX00593FLAojD7NzrsXxtFs56b0VHAoFt18g=o6UhEQ@mail.gmail.com>
	<1433180927073-11729.post@n5.nabble.com>
	<CAD_dpu3NjfSSGBuDXVex6a5hupvv_TVm3qgrGXvwnvjc5uYrvw@mail.gmail.com>
	<CAO2B-fakcGpu_hK4YoPvny2ygG4xEtv4XMESeGZw3rQSB_cSww@mail.gmail.com>
Message-ID: <1433270063187-11733.post@n5.nabble.com>

That worked thanks Erik.  But now I have to re-code my client to register
using the aerogear way of doing things instead of the generic way I did it
before...

The classic pushplugin doesnt require you to provide a push-config when
calling the register() function...we were able to specify that later in the
success method.  That way we could first register the device in the GCM
cloud, and then get a token, and provide that token to aerogear using the
java sender API.  But this aerogear pushplugin looks like it requires the
variant information upfront when calling register()...which we can provide
but I need to know the URL to expose from the aerogear server and specify it
in the push-config....

this link
https://aerogear.org/docs/guides/aerogear-cordova/AerogearCordovaPush/#_documentation
says to use "pushServerURL": "<pushServerURL e.g http(s)//host:port/context
>", in the push-config.json file...so what would this link actually be?  
http(s)//host:port/context would be  http(s)//host:port/ag-push?  or would
it actually be the word "context"

thanks for your help!





--
View this message in context: http://aerogear-dev.1069024.n5.nabble.com/Android-Background-push-notifications-not-working-tp11716p11733.html
Sent from the aerogear-dev mailing list archive at Nabble.com.

From scm.blanc at gmail.com  Tue Jun  2 15:24:42 2015
From: scm.blanc at gmail.com (Sebastien Blanc)
Date: Tue, 2 Jun 2015 21:24:42 +0200
Subject: [aerogear-dev] Sndroid Background push notifications not working
In-Reply-To: <1433270063187-11733.post@n5.nabble.com>
References: <1433163690514-11721.post@n5.nabble.com>
	<1433167852411-11722.post@n5.nabble.com>
	<1433168023446-11723.post@n5.nabble.com>
	<1433168354338-11724.post@n5.nabble.com>
	<CAO2B-fYtA65vxOV1d8iVnv7AcOmVqo+7tvZFCjq7zWJPyraGvw@mail.gmail.com>
	<1433173970945-11727.post@n5.nabble.com>
	<CAD_dpu3pX00593FLAojD7NzrsXxtFs56b0VHAoFt18g=o6UhEQ@mail.gmail.com>
	<1433180927073-11729.post@n5.nabble.com>
	<CAD_dpu3NjfSSGBuDXVex6a5hupvv_TVm3qgrGXvwnvjc5uYrvw@mail.gmail.com>
	<CAO2B-fakcGpu_hK4YoPvny2ygG4xEtv4XMESeGZw3rQSB_cSww@mail.gmail.com>
	<1433270063187-11733.post@n5.nabble.com>
Message-ID: <CAD_dpu1ZR-YgeajD+6a_fo9iJSuAAsjhNXt12Ed=ga7F6y4Shw@mail.gmail.com>

On Tue, Jun 2, 2015 at 8:34 PM, delalis <delalis at gmail.com> wrote:

> That worked thanks Erik.  But now I have to re-code my client to register
> using the aerogear way of doing things instead of the generic way I did it
> before...
>
> The classic pushplugin doesnt require you to provide a push-config when
> calling the register() function...we were able to specify that later in the
> success method.  That way we could first register the device in the GCM
> cloud, and then get a token, and provide that token to aerogear using the
> java sender API.

? You mean the registration API ? The Java Sender can't do anything with
the token (unless you manually affect it to the "alias"

> But this aerogear pushplugin looks like it requires the
> variant information upfront when calling register()...which we can provide
> but I need to know the URL to expose from the aerogear server and specify
> it
> in the push-config....
>
Well you know the URL, don't you ? How did you do it when using the
phonegap push plugin ?

>
> this link
>
> https://aerogear.org/docs/guides/aerogear-cordova/AerogearCordovaPush/#_documentation
> says to use "pushServerURL": "<pushServerURL e.g http(s)//host:port/context
> >", in the push-config.json file...so what would this link actually be?
> http(s)//host:port/context would be  http(s)//host:port/ag-push?  or would
> it actually be the word "context"
>
not "context" :) , more like  http(s)//host:port/ag-push , basically the
context where your push server is running.
BTW, you can use the push-onfig.json file but you can also directly inline
the configuration in your javascript.

>
> thanks for your help!
>
>
>
>
>
> --
> View this message in context:
> http://aerogear-dev.1069024.n5.nabble.com/Android-Background-push-notifications-not-working-tp11716p11733.html
> Sent from the aerogear-dev mailing list archive at Nabble.com.
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150602/70fca898/attachment.html 

From delalis at gmail.com  Tue Jun  2 15:27:55 2015
From: delalis at gmail.com (delalis)
Date: Tue, 2 Jun 2015 12:27:55 -0700 (MST)
Subject: [aerogear-dev] Sndroid Background push notifications not working
In-Reply-To: <CAD_dpu1ZR-YgeajD+6a_fo9iJSuAAsjhNXt12Ed=ga7F6y4Shw@mail.gmail.com>
References: <1433168023446-11723.post@n5.nabble.com>
	<1433168354338-11724.post@n5.nabble.com>
	<CAO2B-fYtA65vxOV1d8iVnv7AcOmVqo+7tvZFCjq7zWJPyraGvw@mail.gmail.com>
	<1433173970945-11727.post@n5.nabble.com>
	<CAD_dpu3pX00593FLAojD7NzrsXxtFs56b0VHAoFt18g=o6UhEQ@mail.gmail.com>
	<1433180927073-11729.post@n5.nabble.com>
	<CAD_dpu3NjfSSGBuDXVex6a5hupvv_TVm3qgrGXvwnvjc5uYrvw@mail.gmail.com>
	<CAO2B-fakcGpu_hK4YoPvny2ygG4xEtv4XMESeGZw3rQSB_cSww@mail.gmail.com>
	<1433270063187-11733.post@n5.nabble.com>
	<CAD_dpu1ZR-YgeajD+6a_fo9iJSuAAsjhNXt12Ed=ga7F6y4Shw@mail.gmail.com>
Message-ID: <1433273275587-11735.post@n5.nabble.com>

Thanks Sebastien!

heres what I sent to my team to give you a better idea of how we had it set
up to use javascript to register with GCM and then Java to insert into the
Aerogear database:


-	We recently switched from using the ?classic phonegap push plugin? to the
?Aerogear phonegap push plugin? because background Android pushes weren?t
coming through, or the payload was different than the classic push plugin
expected, still not sure about that.  Either way, it was recommended by
Aerogear devs to switch to the Aerogear push plugin.

-	Our Aerogear server is hidden behind the ESB.  

-	The device originally called the Drupal Rest service Leaton created to
register devices

-	We can no longer do that because the Aerogear push plugin requires you to
specify the Aerogear server in a config variable so it can talk DIRECTLY to
the Aerogear service to register the devices.  But since it is behind the
ESB, we can not specify this server from the clients perspective.

-	So I thought maybe we can just call the rest service to register the
devices like we used to, and forego the Aerogear?s ?register()? function all
together.  However, this wont work because calling the ?register()? function
is how the client creates a handler to handle the push notifications ? i.e.
register(onNotificationGCM)

-	Since the classic push plugin didn?t require an Aerogear server URL, we
were able to use it to register the device with Apple/GCM, and then in the
success method we called Leatons REST service to insert it into a database
on the ESB, and eventually it would make it into Aerogear using a JAVA
service (Aerogears Java Sender API) running on the ESB.

-	But the new Aerogear push plugin?s register() method seems to want to
register the device with Apple/GCM AND with the Aerogear server all in one
step.  But since the Aerogear server (ESB) is not accessible to the public,
we are POOCHED.

I?m going to try to call the register() function without specifying the
aerogear server, but I expect it to fail since the Aerogear push plugin API
says it is required?.

What to do?what to do?.




--
View this message in context: http://aerogear-dev.1069024.n5.nabble.com/Android-Background-push-notifications-not-working-tp11716p11735.html
Sent from the aerogear-dev mailing list archive at Nabble.com.


From scm.blanc at gmail.com  Tue Jun  2 15:40:55 2015
From: scm.blanc at gmail.com (Sebastien Blanc)
Date: Tue, 2 Jun 2015 21:40:55 +0200
Subject: [aerogear-dev] Sndroid Background push notifications not working
In-Reply-To: <1433273275587-11735.post@n5.nabble.com>
References: <1433168023446-11723.post@n5.nabble.com>
	<1433168354338-11724.post@n5.nabble.com>
	<CAO2B-fYtA65vxOV1d8iVnv7AcOmVqo+7tvZFCjq7zWJPyraGvw@mail.gmail.com>
	<1433173970945-11727.post@n5.nabble.com>
	<CAD_dpu3pX00593FLAojD7NzrsXxtFs56b0VHAoFt18g=o6UhEQ@mail.gmail.com>
	<1433180927073-11729.post@n5.nabble.com>
	<CAD_dpu3NjfSSGBuDXVex6a5hupvv_TVm3qgrGXvwnvjc5uYrvw@mail.gmail.com>
	<CAO2B-fakcGpu_hK4YoPvny2ygG4xEtv4XMESeGZw3rQSB_cSww@mail.gmail.com>
	<1433270063187-11733.post@n5.nabble.com>
	<CAD_dpu1ZR-YgeajD+6a_fo9iJSuAAsjhNXt12Ed=ga7F6y4Shw@mail.gmail.com>
	<1433273275587-11735.post@n5.nabble.com>
Message-ID: <CAD_dpu0XPix6qH3CFc82ugkL5ki9b2eJb+4g9NfNzim1YS_=pw@mail.gmail.com>

Ah ok, The Push Server is hidden behind a ESB, hum ... interesting :)
Can't your "Leatons" REST Service  proxy the register request to the push
server ?

Or maybe just let Leaton accept the register request made by the aerogear
plugin and store the json payload, later a service can submit that to the
UnifiedPush Server. You can find the definition of this endpoint here :
https://aerogear.org/docs/specs/aerogear-unifiedpush-rest-1.0.x/registry/device/index.html


And I still don't see why you mention the AeroGear Java Sender API, do you
mean this https://github.com/aerogear/aerogear-unifiedpush-java-client ?
This unrelated to the registration and used to send push notification.

Hope that helps.

Seb

On Tue, Jun 2, 2015 at 9:27 PM, delalis <delalis at gmail.com> wrote:

> Thanks Sebastien!
>
> heres what I sent to my team to give you a better idea of how we had it set
> up to use javascript to register with GCM and then Java to insert into the
> Aerogear database:
>
>
> -       We recently switched from using the ?classic phonegap push plugin?
> to the
> ?Aerogear phonegap push plugin? because background Android pushes weren?t
> coming through, or the payload was different than the classic push plugin
> expected, still not sure about that.  Either way, it was recommended by
> Aerogear devs to switch to the Aerogear push plugin.
>
> -       Our Aerogear server is hidden behind the ESB.
>
> -       The device originally called the Drupal Rest service Leaton
> created to
> register devices
>
> -       We can no longer do that because the Aerogear push plugin requires
> you to
> specify the Aerogear server in a config variable so it can talk DIRECTLY to
> the Aerogear service to register the devices.  But since it is behind the
> ESB, we can not specify this server from the clients perspective.
>
> -       So I thought maybe we can just call the rest service to register
> the
> devices like we used to, and forego the Aerogear?s ?register()? function
> all
> together.  However, this wont work because calling the ?register()?
> function
> is how the client creates a handler to handle the push notifications ? i.e.
> register(onNotificationGCM)
>
> -       Since the classic push plugin didn?t require an Aerogear server
> URL, we
> were able to use it to register the device with Apple/GCM, and then in the
> success method we called Leatons REST service to insert it into a database
> on the ESB, and eventually it would make it into Aerogear using a JAVA
> service (Aerogears Java Sender API) running on the ESB.
>
> -       But the new Aerogear push plugin?s register() method seems to want
> to
> register the device with Apple/GCM AND with the Aerogear server all in one
> step.  But since the Aerogear server (ESB) is not accessible to the public,
> we are POOCHED.
>
> I?m going to try to call the register() function without specifying the
> aerogear server, but I expect it to fail since the Aerogear push plugin API
> says it is required?.
>
> What to do?what to do?.
>
>
>
>
> --
> View this message in context:
> http://aerogear-dev.1069024.n5.nabble.com/Android-Background-push-notifications-not-working-tp11716p11735.html
> Sent from the aerogear-dev mailing list archive at Nabble.com.
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150602/8ec1dd92/attachment.html 

From delalis at gmail.com  Tue Jun  2 15:51:33 2015
From: delalis at gmail.com (delalis)
Date: Tue, 2 Jun 2015 12:51:33 -0700 (MST)
Subject: [aerogear-dev] Sndroid Background push notifications not working
In-Reply-To: <CAD_dpu0XPix6qH3CFc82ugkL5ki9b2eJb+4g9NfNzim1YS_=pw@mail.gmail.com>
References: <CAO2B-fYtA65vxOV1d8iVnv7AcOmVqo+7tvZFCjq7zWJPyraGvw@mail.gmail.com>
	<1433173970945-11727.post@n5.nabble.com>
	<CAD_dpu3pX00593FLAojD7NzrsXxtFs56b0VHAoFt18g=o6UhEQ@mail.gmail.com>
	<1433180927073-11729.post@n5.nabble.com>
	<CAD_dpu3NjfSSGBuDXVex6a5hupvv_TVm3qgrGXvwnvjc5uYrvw@mail.gmail.com>
	<CAO2B-fakcGpu_hK4YoPvny2ygG4xEtv4XMESeGZw3rQSB_cSww@mail.gmail.com>
	<1433270063187-11733.post@n5.nabble.com>
	<CAD_dpu1ZR-YgeajD+6a_fo9iJSuAAsjhNXt12Ed=ga7F6y4Shw@mail.gmail.com>
	<1433273275587-11735.post@n5.nabble.com>
	<CAD_dpu0XPix6qH3CFc82ugkL5ki9b2eJb+4g9NfNzim1YS_=pw@mail.gmail.com>
Message-ID: <1433274693890-11737.post@n5.nabble.com>

Thanks for writing back so quickly!

1) Can't your "Leatons" REST Service  proxy the register request to the push
server ?

---Yes that is what we were doing before, the classic push plugin called
register() which simply registered the token with APNS/GCM, and in the
onSuccess function we would then send an AJAX call to Leatons REST service
which would then put the device token we got back from the register() call
into the Aerogear database using whatever methods Aerogears API exposed
(sorry, I think that is what I meant by the Sender API)... so if you suggest
using the REST service as a proxy to the push server and bypass the
register() function altogether, how would we hook up the client
onNotification() handler?

2) Or maybe just let Leaton accept the register request made by the aerogear
plugin and store the json payload, later a service can submit that to the
UnifiedPush Server. 
---Again, how would we hook up the phonegap client onNotification() handler
if we arent calling register from the clients javascript code??



--
View this message in context: http://aerogear-dev.1069024.n5.nabble.com/Android-Background-push-notifications-not-working-tp11716p11737.html
Sent from the aerogear-dev mailing list archive at Nabble.com.

From delalis at gmail.com  Tue Jun  2 16:02:08 2015
From: delalis at gmail.com (delalis)
Date: Tue, 2 Jun 2015 13:02:08 -0700 (MST)
Subject: [aerogear-dev] Sndroid Background push notifications not working
In-Reply-To: <1433274693890-11737.post@n5.nabble.com>
References: <1433173970945-11727.post@n5.nabble.com>
	<CAD_dpu3pX00593FLAojD7NzrsXxtFs56b0VHAoFt18g=o6UhEQ@mail.gmail.com>
	<1433180927073-11729.post@n5.nabble.com>
	<CAD_dpu3NjfSSGBuDXVex6a5hupvv_TVm3qgrGXvwnvjc5uYrvw@mail.gmail.com>
	<CAO2B-fakcGpu_hK4YoPvny2ygG4xEtv4XMESeGZw3rQSB_cSww@mail.gmail.com>
	<1433270063187-11733.post@n5.nabble.com>
	<CAD_dpu1ZR-YgeajD+6a_fo9iJSuAAsjhNXt12Ed=ga7F6y4Shw@mail.gmail.com>
	<1433273275587-11735.post@n5.nabble.com>
	<CAD_dpu0XPix6qH3CFc82ugkL5ki9b2eJb+4g9NfNzim1YS_=pw@mail.gmail.com>
	<1433274693890-11737.post@n5.nabble.com>
Message-ID: <1433275328512-11738.post@n5.nabble.com>

Im wondering if this is a case of "were doing it wrong" and we should find a
new place for the UPS to live that can be contacted directly by the devices
with the push-config json info pointing right to it....



--
View this message in context: http://aerogear-dev.1069024.n5.nabble.com/Android-Background-push-notifications-not-working-tp11716p11738.html
Sent from the aerogear-dev mailing list archive at Nabble.com.

From scm.blanc at gmail.com  Tue Jun  2 16:11:00 2015
From: scm.blanc at gmail.com (Sebastien Blanc)
Date: Tue, 2 Jun 2015 22:11:00 +0200
Subject: [aerogear-dev] Sndroid Background push notifications not working
In-Reply-To: <1433274693890-11737.post@n5.nabble.com>
References: <CAO2B-fYtA65vxOV1d8iVnv7AcOmVqo+7tvZFCjq7zWJPyraGvw@mail.gmail.com>
	<1433173970945-11727.post@n5.nabble.com>
	<CAD_dpu3pX00593FLAojD7NzrsXxtFs56b0VHAoFt18g=o6UhEQ@mail.gmail.com>
	<1433180927073-11729.post@n5.nabble.com>
	<CAD_dpu3NjfSSGBuDXVex6a5hupvv_TVm3qgrGXvwnvjc5uYrvw@mail.gmail.com>
	<CAO2B-fakcGpu_hK4YoPvny2ygG4xEtv4XMESeGZw3rQSB_cSww@mail.gmail.com>
	<1433270063187-11733.post@n5.nabble.com>
	<CAD_dpu1ZR-YgeajD+6a_fo9iJSuAAsjhNXt12Ed=ga7F6y4Shw@mail.gmail.com>
	<1433273275587-11735.post@n5.nabble.com>
	<CAD_dpu0XPix6qH3CFc82ugkL5ki9b2eJb+4g9NfNzim1YS_=pw@mail.gmail.com>
	<1433274693890-11737.post@n5.nabble.com>
Message-ID: <CAD_dpu3mLbFdKz9eQY25tQEoA1RO_ThfipNAPX6AowQqGpTbOA@mail.gmail.com>

On Tue, Jun 2, 2015 at 9:51 PM, delalis <delalis at gmail.com> wrote:

> Thanks for writing back so quickly!
>
> 1) Can't your "Leatons" REST Service  proxy the register request to the
> push
> server ?
>
> ---Yes that is what we were doing before, the classic push plugin called
> register() which simply registered the token with APNS/GCM, and in the
> onSuccess function we would then send an AJAX call to Leatons REST service
> which would then put the device token we got back from the register() call
> into the Aerogear database using whatever methods Aerogears API exposed
> (sorry, I think that is what I meant by the Sender API)... so if you
> suggest
> using the REST service as a proxy to the push server and bypass the
> register() function altogether, how would we hook up the client
> onNotification() handler?
>
> 2) Or maybe just let Leaton accept the register request made by the
> aerogear
> plugin and store the json payload, later a service can submit that to the
> UnifiedPush Server.
> ---Again, how would we hook up the phonegap client onNotification() handler
> if we arent calling register from the clients javascript code??
>

I meant  : you still use the plugin javascript code register() but just
make sure that your backend API (Leaton or whatever) accept the path and
the json payload so :

POST http//myleatonservice/rest/registry/device  + JSON Payload

You just point to "http//myleatonservice/rest" in you push-config,
"/registry/device" will be added automatically by the plugin.

Could sound hacky but worth to explore.

This way you still hookup your onNotification() handler

>
>
>
> --
> View this message in context:
> http://aerogear-dev.1069024.n5.nabble.com/Android-Background-push-notifications-not-working-tp11716p11737.html
> Sent from the aerogear-dev mailing list archive at Nabble.com.
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150602/222f62f4/attachment.html 

From scm.blanc at gmail.com  Tue Jun  2 16:12:35 2015
From: scm.blanc at gmail.com (Sebastien Blanc)
Date: Tue, 2 Jun 2015 22:12:35 +0200
Subject: [aerogear-dev] Sndroid Background push notifications not working
In-Reply-To: <1433275328512-11738.post@n5.nabble.com>
References: <1433173970945-11727.post@n5.nabble.com>
	<CAD_dpu3pX00593FLAojD7NzrsXxtFs56b0VHAoFt18g=o6UhEQ@mail.gmail.com>
	<1433180927073-11729.post@n5.nabble.com>
	<CAD_dpu3NjfSSGBuDXVex6a5hupvv_TVm3qgrGXvwnvjc5uYrvw@mail.gmail.com>
	<CAO2B-fakcGpu_hK4YoPvny2ygG4xEtv4XMESeGZw3rQSB_cSww@mail.gmail.com>
	<1433270063187-11733.post@n5.nabble.com>
	<CAD_dpu1ZR-YgeajD+6a_fo9iJSuAAsjhNXt12Ed=ga7F6y4Shw@mail.gmail.com>
	<1433273275587-11735.post@n5.nabble.com>
	<CAD_dpu0XPix6qH3CFc82ugkL5ki9b2eJb+4g9NfNzim1YS_=pw@mail.gmail.com>
	<1433274693890-11737.post@n5.nabble.com>
	<1433275328512-11738.post@n5.nabble.com>
Message-ID: <CAD_dpu0MpbgdgHJSfK3CxFCLx+CnjR22Rd+jmKGAK43tXHnGzQ@mail.gmail.com>

On Tue, Jun 2, 2015 at 10:02 PM, delalis <delalis at gmail.com> wrote:

> Im wondering if this is a case of "were doing it wrong" and we should find
> a
> new place for the UPS to live that can be contacted directly by the devices
> with the push-config json info pointing right to it....
>
Well you have maybe a valid use case/architecture choice to not want to
expose UPS but indeed if it can be exposed you can avoid some hacky stuff I
suggested in my previous emails ;)

>
>
>
> --
> View this message in context:
> http://aerogear-dev.1069024.n5.nabble.com/Android-Background-push-notifications-not-working-tp11716p11738.html
> Sent from the aerogear-dev mailing list archive at Nabble.com.
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150602/c08ac693/attachment.html 

From delalis at gmail.com  Tue Jun  2 16:16:36 2015
From: delalis at gmail.com (delalis)
Date: Tue, 2 Jun 2015 13:16:36 -0700 (MST)
Subject: [aerogear-dev] Sndroid Background push notifications not working
In-Reply-To: <CAD_dpu3mLbFdKz9eQY25tQEoA1RO_ThfipNAPX6AowQqGpTbOA@mail.gmail.com>
References: <CAD_dpu3pX00593FLAojD7NzrsXxtFs56b0VHAoFt18g=o6UhEQ@mail.gmail.com>
	<1433180927073-11729.post@n5.nabble.com>
	<CAD_dpu3NjfSSGBuDXVex6a5hupvv_TVm3qgrGXvwnvjc5uYrvw@mail.gmail.com>
	<CAO2B-fakcGpu_hK4YoPvny2ygG4xEtv4XMESeGZw3rQSB_cSww@mail.gmail.com>
	<1433270063187-11733.post@n5.nabble.com>
	<CAD_dpu1ZR-YgeajD+6a_fo9iJSuAAsjhNXt12Ed=ga7F6y4Shw@mail.gmail.com>
	<1433273275587-11735.post@n5.nabble.com>
	<CAD_dpu0XPix6qH3CFc82ugkL5ki9b2eJb+4g9NfNzim1YS_=pw@mail.gmail.com>
	<1433274693890-11737.post@n5.nabble.com>
	<CAD_dpu3mLbFdKz9eQY25tQEoA1RO_ThfipNAPX6AowQqGpTbOA@mail.gmail.com>
Message-ID: <CAPfhyfdGW=6kMzNjpS5NYbjCK3KAAecpR7e6xe6LTJ7dhn0F0w@mail.gmail.com>

ah okay.  I didnt think of putting the REST service in the config.  But
then what would we pass to the REST service as the device token to pass to
aerogear in the subsequent Java call?  in the classic push plugin, the
onsuccess(event) came back with a device token that we would then send to
the REST service to register with Aerogear using a Java call.

On Tue, Jun 2, 2015 at 4:11 PM, Sebastien Blanc [via aerogear-dev] <
ml-node+s1069024n11739h82 at n5.nabble.com> wrote:

>
>
> On Tue, Jun 2, 2015 at 9:51 PM, delalis <[hidden email]
> <http:///user/SendEmail.jtp?type=node&node=11739&i=0>> wrote:
>
>> Thanks for writing back so quickly!
>>
>> 1) Can't your "Leatons" REST Service  proxy the register request to the
>> push
>> server ?
>>
>> ---Yes that is what we were doing before, the classic push plugin called
>> register() which simply registered the token with APNS/GCM, and in the
>> onSuccess function we would then send an AJAX call to Leatons REST service
>> which would then put the device token we got back from the register() call
>> into the Aerogear database using whatever methods Aerogears API exposed
>> (sorry, I think that is what I meant by the Sender API)... so if you
>> suggest
>> using the REST service as a proxy to the push server and bypass the
>> register() function altogether, how would we hook up the client
>> onNotification() handler?
>>
>> 2) Or maybe just let Leaton accept the register request made by the
>> aerogear
>> plugin and store the json payload, later a service can submit that to the
>> UnifiedPush Server.
>> ---Again, how would we hook up the phonegap client onNotification()
>> handler
>> if we arent calling register from the clients javascript code??
>>
>
> I meant  : you still use the plugin javascript code register() but just
> make sure that your backend API (Leaton or whatever) accept the path and
> the json payload so :
>
> POST http//myleatonservice/rest/registry/device  + JSON Payload
>
> You just point to "http//myleatonservice/rest" in you push-config,
> "/registry/device" will be added automatically by the plugin.
>
> Could sound hacky but worth to explore.
>
> This way you still hookup your onNotification() handler
>
>>
>>
>>
>> --
>> View this message in context:
>> http://aerogear-dev.1069024.n5.nabble.com/Android-Background-push-notifications-not-working-tp11716p11737.html
>> Sent from the aerogear-dev mailing list archive at Nabble.com.
>> _______________________________________________
>> aerogear-dev mailing list
>> [hidden email] <http:///user/SendEmail.jtp?type=node&node=11739&i=1>
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
> _______________________________________________
> aerogear-dev mailing list
> [hidden email] <http:///user/SendEmail.jtp?type=node&node=11739&i=2>
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
> ------------------------------
>  If you reply to this email, your message will be added to the discussion
> below:
>
> http://aerogear-dev.1069024.n5.nabble.com/Android-Background-push-notifications-not-working-tp11716p11739.html
>  To unsubscribe from Android Background push notifications not working, click
> here
> <http://aerogear-dev.1069024.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=11716&code=ZGVsYWxpc0BnbWFpbC5jb218MTE3MTZ8LTIxNTA2NTE0MQ==>
> .
> NAML
> <http://aerogear-dev.1069024.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>




--
View this message in context: http://aerogear-dev.1069024.n5.nabble.com/Android-Background-push-notifications-not-working-tp11716p11741.html
Sent from the aerogear-dev mailing list archive at Nabble.com.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150602/af33f768/attachment-0001.html 

From delalis at gmail.com  Tue Jun  2 16:19:17 2015
From: delalis at gmail.com (Chris Delalis)
Date: Tue, 2 Jun 2015 16:19:17 -0400
Subject: [aerogear-dev] Sndroid Background push notifications not working
In-Reply-To: <CAPfhyfdGW=6kMzNjpS5NYbjCK3KAAecpR7e6xe6LTJ7dhn0F0w@mail.gmail.com>
References: <CAD_dpu3pX00593FLAojD7NzrsXxtFs56b0VHAoFt18g=o6UhEQ@mail.gmail.com>
	<1433180927073-11729.post@n5.nabble.com>
	<CAD_dpu3NjfSSGBuDXVex6a5hupvv_TVm3qgrGXvwnvjc5uYrvw@mail.gmail.com>
	<CAO2B-fakcGpu_hK4YoPvny2ygG4xEtv4XMESeGZw3rQSB_cSww@mail.gmail.com>
	<1433270063187-11733.post@n5.nabble.com>
	<CAD_dpu1ZR-YgeajD+6a_fo9iJSuAAsjhNXt12Ed=ga7F6y4Shw@mail.gmail.com>
	<1433273275587-11735.post@n5.nabble.com>
	<CAD_dpu0XPix6qH3CFc82ugkL5ki9b2eJb+4g9NfNzim1YS_=pw@mail.gmail.com>
	<1433274693890-11737.post@n5.nabble.com>
	<CAD_dpu3mLbFdKz9eQY25tQEoA1RO_ThfipNAPX6AowQqGpTbOA@mail.gmail.com>
	<CAPfhyfdGW=6kMzNjpS5NYbjCK3KAAecpR7e6xe6LTJ7dhn0F0w@mail.gmail.com>
Message-ID: <CAPfhyffcWuqYBXA2FcksPPrx3FkJMMZM81c7cCo4+2XTDgu-cQ@mail.gmail.com>

does Aerogear push plugin's way of implementing the onNotification(e) give
you back a device token for registration purposes after calling register()?
 if so, then we can make a second call to the REST service after the
onNotification is called...

On Tue, Jun 2, 2015 at 4:16 PM, delalis <delalis at gmail.com> wrote:

> ah okay.  I didnt think of putting the REST service in the config.  But
> then what would we pass to the REST service as the device token to pass to
> aerogear in the subsequent Java call?  in the classic push plugin, the
> onsuccess(event) came back with a device token that we would then send to
> the REST service to register with Aerogear using a Java call.
>
> On Tue, Jun 2, 2015 at 4:11 PM, Sebastien Blanc [via aerogear-dev] <[hidden
> email] <http:///user/SendEmail.jtp?type=node&node=11741&i=0>> wrote:
>
>>
>>
>> On Tue, Jun 2, 2015 at 9:51 PM, delalis <[hidden email]
>> <http:///user/SendEmail.jtp?type=node&node=11739&i=0>> wrote:
>>
>>> Thanks for writing back so quickly!
>>>
>>> 1) Can't your "Leatons" REST Service  proxy the register request to the
>>> push
>>> server ?
>>>
>>> ---Yes that is what we were doing before, the classic push plugin called
>>> register() which simply registered the token with APNS/GCM, and in the
>>> onSuccess function we would then send an AJAX call to Leatons REST
>>> service
>>> which would then put the device token we got back from the register()
>>> call
>>> into the Aerogear database using whatever methods Aerogears API exposed
>>> (sorry, I think that is what I meant by the Sender API)... so if you
>>> suggest
>>> using the REST service as a proxy to the push server and bypass the
>>> register() function altogether, how would we hook up the client
>>> onNotification() handler?
>>>
>>> 2) Or maybe just let Leaton accept the register request made by the
>>> aerogear
>>> plugin and store the json payload, later a service can submit that to the
>>> UnifiedPush Server.
>>> ---Again, how would we hook up the phonegap client onNotification()
>>> handler
>>> if we arent calling register from the clients javascript code??
>>>
>>
>> I meant  : you still use the plugin javascript code register() but just
>> make sure that your backend API (Leaton or whatever) accept the path and
>> the json payload so :
>>
>> POST http//myleatonservice/rest/registry/device  + JSON Payload
>>
>> You just point to "http//myleatonservice/rest" in you push-config,
>> "/registry/device" will be added automatically by the plugin.
>>
>> Could sound hacky but worth to explore.
>>
>> This way you still hookup your onNotification() handler
>>
>>>
>>>
>>>
>>> --
>>> View this message in context:
>>> http://aerogear-dev.1069024.n5.nabble.com/Android-Background-push-notifications-not-working-tp11716p11737.html
>>> Sent from the aerogear-dev mailing list archive at Nabble.com.
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> [hidden email] <http:///user/SendEmail.jtp?type=node&node=11739&i=1>
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> [hidden email] <http:///user/SendEmail.jtp?type=node&node=11739&i=2>
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>> ------------------------------
>>  If you reply to this email, your message will be added to the
>> discussion below:
>>
>> http://aerogear-dev.1069024.n5.nabble.com/Android-Background-push-notifications-not-working-tp11716p11739.html
>>  To unsubscribe from Android Background push notifications not working, click
>> here.
>> NAML
>> <http://aerogear-dev.1069024.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>>
>
>
> ------------------------------
> View this message in context: Re: [aerogear-dev] Sndroid Background push
> notifications not working
> <http://aerogear-dev.1069024.n5.nabble.com/Android-Background-push-notifications-not-working-tp11716p11741.html>
>
> Sent from the aerogear-dev mailing list archive
> <http://aerogear-dev.1069024.n5.nabble.com/> at Nabble.com.
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150602/ebb62f2d/attachment.html 

From scm.blanc at gmail.com  Tue Jun  2 16:19:46 2015
From: scm.blanc at gmail.com (Sebastien Blanc)
Date: Tue, 2 Jun 2015 22:19:46 +0200
Subject: [aerogear-dev] Sndroid Background push notifications not working
In-Reply-To: <CAPfhyfdGW=6kMzNjpS5NYbjCK3KAAecpR7e6xe6LTJ7dhn0F0w@mail.gmail.com>
References: <CAD_dpu3pX00593FLAojD7NzrsXxtFs56b0VHAoFt18g=o6UhEQ@mail.gmail.com>
	<1433180927073-11729.post@n5.nabble.com>
	<CAD_dpu3NjfSSGBuDXVex6a5hupvv_TVm3qgrGXvwnvjc5uYrvw@mail.gmail.com>
	<CAO2B-fakcGpu_hK4YoPvny2ygG4xEtv4XMESeGZw3rQSB_cSww@mail.gmail.com>
	<1433270063187-11733.post@n5.nabble.com>
	<CAD_dpu1ZR-YgeajD+6a_fo9iJSuAAsjhNXt12Ed=ga7F6y4Shw@mail.gmail.com>
	<1433273275587-11735.post@n5.nabble.com>
	<CAD_dpu0XPix6qH3CFc82ugkL5ki9b2eJb+4g9NfNzim1YS_=pw@mail.gmail.com>
	<1433274693890-11737.post@n5.nabble.com>
	<CAD_dpu3mLbFdKz9eQY25tQEoA1RO_ThfipNAPX6AowQqGpTbOA@mail.gmail.com>
	<CAPfhyfdGW=6kMzNjpS5NYbjCK3KAAecpR7e6xe6LTJ7dhn0F0w@mail.gmail.com>
Message-ID: <CAD_dpu2NvgmebGHOHFy5BV4cbwm0NcG0iMffk6b+PD1FA2+n8g@mail.gmail.com>

You don't have to worry about that :) the AeroGear push plugin will already
include the device token in the payload, in fact you don't have to worry at
all about the payload, just call register()

On Tue, Jun 2, 2015 at 10:16 PM, delalis <delalis at gmail.com> wrote:

> ah okay.  I didnt think of putting the REST service in the config.  But
> then what would we pass to the REST service as the device token to pass to
> aerogear in the subsequent Java call?  in the classic push plugin, the
> onsuccess(event) came back with a device token that we would then send to
> the REST service to register with Aerogear using a Java call.
>
> On Tue, Jun 2, 2015 at 4:11 PM, Sebastien Blanc [via aerogear-dev] <[hidden
> email] <http:///user/SendEmail.jtp?type=node&node=11741&i=0>> wrote:
>
>>
>>
>> On Tue, Jun 2, 2015 at 9:51 PM, delalis <[hidden email]
>> <http:///user/SendEmail.jtp?type=node&node=11739&i=0>> wrote:
>>
>>> Thanks for writing back so quickly!
>>>
>>> 1) Can't your "Leatons" REST Service  proxy the register request to the
>>> push
>>> server ?
>>>
>>> ---Yes that is what we were doing before, the classic push plugin called
>>> register() which simply registered the token with APNS/GCM, and in the
>>> onSuccess function we would then send an AJAX call to Leatons REST
>>> service
>>> which would then put the device token we got back from the register()
>>> call
>>> into the Aerogear database using whatever methods Aerogears API exposed
>>> (sorry, I think that is what I meant by the Sender API)... so if you
>>> suggest
>>> using the REST service as a proxy to the push server and bypass the
>>> register() function altogether, how would we hook up the client
>>> onNotification() handler?
>>>
>>> 2) Or maybe just let Leaton accept the register request made by the
>>> aerogear
>>> plugin and store the json payload, later a service can submit that to the
>>> UnifiedPush Server.
>>> ---Again, how would we hook up the phonegap client onNotification()
>>> handler
>>> if we arent calling register from the clients javascript code??
>>>
>>
>> I meant  : you still use the plugin javascript code register() but just
>> make sure that your backend API (Leaton or whatever) accept the path and
>> the json payload so :
>>
>> POST http//myleatonservice/rest/registry/device  + JSON Payload
>>
>> You just point to "http//myleatonservice/rest" in you push-config,
>> "/registry/device" will be added automatically by the plugin.
>>
>> Could sound hacky but worth to explore.
>>
>> This way you still hookup your onNotification() handler
>>
>>>
>>>
>>>
>>> --
>>> View this message in context:
>>> http://aerogear-dev.1069024.n5.nabble.com/Android-Background-push-notifications-not-working-tp11716p11737.html
>>> Sent from the aerogear-dev mailing list archive at Nabble.com.
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> [hidden email] <http:///user/SendEmail.jtp?type=node&node=11739&i=1>
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> [hidden email] <http:///user/SendEmail.jtp?type=node&node=11739&i=2>
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>> ------------------------------
>>  If you reply to this email, your message will be added to the
>> discussion below:
>>
>> http://aerogear-dev.1069024.n5.nabble.com/Android-Background-push-notifications-not-working-tp11716p11739.html
>>  To unsubscribe from Android Background push notifications not working, click
>> here.
>> NAML
>> <http://aerogear-dev.1069024.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>>
>
>
> ------------------------------
> View this message in context: Re: [aerogear-dev] Sndroid Background push
> notifications not working
> <http://aerogear-dev.1069024.n5.nabble.com/Android-Background-push-notifications-not-working-tp11716p11741.html>
>
> Sent from the aerogear-dev mailing list archive
> <http://aerogear-dev.1069024.n5.nabble.com/> at Nabble.com.
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150602/afc79991/attachment-0001.html 

From delalis at gmail.com  Tue Jun  2 16:24:56 2015
From: delalis at gmail.com (delalis)
Date: Tue, 2 Jun 2015 13:24:56 -0700 (MST)
Subject: [aerogear-dev] Sndroid Background push notifications not working
In-Reply-To: <CAD_dpu2NvgmebGHOHFy5BV4cbwm0NcG0iMffk6b+PD1FA2+n8g@mail.gmail.com>
References: <CAD_dpu3NjfSSGBuDXVex6a5hupvv_TVm3qgrGXvwnvjc5uYrvw@mail.gmail.com>
	<CAO2B-fakcGpu_hK4YoPvny2ygG4xEtv4XMESeGZw3rQSB_cSww@mail.gmail.com>
	<1433270063187-11733.post@n5.nabble.com>
	<CAD_dpu1ZR-YgeajD+6a_fo9iJSuAAsjhNXt12Ed=ga7F6y4Shw@mail.gmail.com>
	<1433273275587-11735.post@n5.nabble.com>
	<CAD_dpu0XPix6qH3CFc82ugkL5ki9b2eJb+4g9NfNzim1YS_=pw@mail.gmail.com>
	<1433274693890-11737.post@n5.nabble.com>
	<CAD_dpu3mLbFdKz9eQY25tQEoA1RO_ThfipNAPX6AowQqGpTbOA@mail.gmail.com>
	<CAPfhyfdGW=6kMzNjpS5NYbjCK3KAAecpR7e6xe6LTJ7dhn0F0w@mail.gmail.com>
	<CAD_dpu2NvgmebGHOHFy5BV4cbwm0NcG0iMffk6b+PD1FA2+n8g@mail.gmail.com>
Message-ID: <CAPfhyfdxmNNrTLiMPUUkDtBk=So=QFq3685C1qovkwpV8zmioQ@mail.gmail.com>

So please correct me if I am wrong...

  if we call register() and set our Java REST service in the config, we
will need to take the payload passed into the REST service, parse out the
device token (which you said is sent there automatically), and send that to
Aerogear using the method we are already currently using to register device
tokens with Aerogear in the Service? (since the REST service can talk to
the UPS)

is this correct??

On Tue, Jun 2, 2015 at 4:20 PM, Sebastien Blanc [via aerogear-dev] <
ml-node+s1069024n11743h6 at n5.nabble.com> wrote:

> You don't have to worry about that :) the AeroGear push plugin will
> already include the device token in the payload, in fact you don't have to
> worry at all about the payload, just call register()
>
> On Tue, Jun 2, 2015 at 10:16 PM, delalis <[hidden email]
> <http:///user/SendEmail.jtp?type=node&node=11743&i=0>> wrote:
>
>> ah okay.  I didnt think of putting the REST service in the config.  But
>> then what would we pass to the REST service as the device token to pass to
>> aerogear in the subsequent Java call?  in the classic push plugin, the
>> onsuccess(event) came back with a device token that we would then send to
>> the REST service to register with Aerogear using a Java call.
>>
>> On Tue, Jun 2, 2015 at 4:11 PM, Sebastien Blanc [via aerogear-dev] <[hidden
>> email] <http:///user/SendEmail.jtp?type=node&node=11741&i=0>> wrote:
>>
>>>
>>>
>>> On Tue, Jun 2, 2015 at 9:51 PM, delalis <[hidden email]
>>> <http:///user/SendEmail.jtp?type=node&node=11739&i=0>> wrote:
>>>
>>>> Thanks for writing back so quickly!
>>>>
>>>> 1) Can't your "Leatons" REST Service  proxy the register request to the
>>>> push
>>>> server ?
>>>>
>>>> ---Yes that is what we were doing before, the classic push plugin called
>>>> register() which simply registered the token with APNS/GCM, and in the
>>>> onSuccess function we would then send an AJAX call to Leatons REST
>>>> service
>>>> which would then put the device token we got back from the register()
>>>> call
>>>> into the Aerogear database using whatever methods Aerogears API exposed
>>>> (sorry, I think that is what I meant by the Sender API)... so if you
>>>> suggest
>>>> using the REST service as a proxy to the push server and bypass the
>>>> register() function altogether, how would we hook up the client
>>>> onNotification() handler?
>>>>
>>>> 2) Or maybe just let Leaton accept the register request made by the
>>>> aerogear
>>>> plugin and store the json payload, later a service can submit that to
>>>> the
>>>> UnifiedPush Server.
>>>> ---Again, how would we hook up the phonegap client onNotification()
>>>> handler
>>>> if we arent calling register from the clients javascript code??
>>>>
>>>
>>> I meant  : you still use the plugin javascript code register() but just
>>> make sure that your backend API (Leaton or whatever) accept the path and
>>> the json payload so :
>>>
>>> POST http//myleatonservice/rest/registry/device  + JSON Payload
>>>
>>> You just point to "http//myleatonservice/rest" in you push-config,
>>> "/registry/device" will be added automatically by the plugin.
>>>
>>> Could sound hacky but worth to explore.
>>>
>>> This way you still hookup your onNotification() handler
>>>
>>>>
>>>>
>>>>
>>>> --
>>>> View this message in context:
>>>> http://aerogear-dev.1069024.n5.nabble.com/Android-Background-push-notifications-not-working-tp11716p11737.html
>>>> Sent from the aerogear-dev mailing list archive at Nabble.com.
>>>> _______________________________________________
>>>> aerogear-dev mailing list
>>>> [hidden email] <http:///user/SendEmail.jtp?type=node&node=11739&i=1>
>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>
>>>
>>>
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> [hidden email] <http:///user/SendEmail.jtp?type=node&node=11739&i=2>
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>> ------------------------------
>>>  If you reply to this email, your message will be added to the
>>> discussion below:
>>>
>>> http://aerogear-dev.1069024.n5.nabble.com/Android-Background-push-notifications-not-working-tp11716p11739.html
>>>  To unsubscribe from Android Background push notifications not working, click
>>> here.
>>> NAML
>>> <http://aerogear-dev.1069024.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>>>
>>
>>
>> ------------------------------
>> View this message in context: Re: [aerogear-dev] Sndroid Background push
>> notifications not working
>> <http://aerogear-dev.1069024.n5.nabble.com/Android-Background-push-notifications-not-working-tp11716p11741.html>
>>
>> Sent from the aerogear-dev mailing list archive
>> <http://aerogear-dev.1069024.n5.nabble.com/> at Nabble.com.
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> [hidden email] <http:///user/SendEmail.jtp?type=node&node=11743&i=1>
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
> _______________________________________________
> aerogear-dev mailing list
> [hidden email] <http:///user/SendEmail.jtp?type=node&node=11743&i=2>
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
> ------------------------------
>  If you reply to this email, your message will be added to the discussion
> below:
>
> http://aerogear-dev.1069024.n5.nabble.com/Android-Background-push-notifications-not-working-tp11716p11743.html
>  To unsubscribe from Android Background push notifications not working, click
> here
> <http://aerogear-dev.1069024.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=11716&code=ZGVsYWxpc0BnbWFpbC5jb218MTE3MTZ8LTIxNTA2NTE0MQ==>
> .
> NAML
> <http://aerogear-dev.1069024.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>




--
View this message in context: http://aerogear-dev.1069024.n5.nabble.com/Android-Background-push-notifications-not-working-tp11716p11744.html
Sent from the aerogear-dev mailing list archive at Nabble.com.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150602/ae7a0b10/attachment.html 

From scm.blanc at gmail.com  Tue Jun  2 16:36:04 2015
From: scm.blanc at gmail.com (Sebastien Blanc)
Date: Tue, 2 Jun 2015 22:36:04 +0200
Subject: [aerogear-dev] Sndroid Background push notifications not working
In-Reply-To: <CAPfhyfdxmNNrTLiMPUUkDtBk=So=QFq3685C1qovkwpV8zmioQ@mail.gmail.com>
References: <CAD_dpu3NjfSSGBuDXVex6a5hupvv_TVm3qgrGXvwnvjc5uYrvw@mail.gmail.com>
	<CAO2B-fakcGpu_hK4YoPvny2ygG4xEtv4XMESeGZw3rQSB_cSww@mail.gmail.com>
	<1433270063187-11733.post@n5.nabble.com>
	<CAD_dpu1ZR-YgeajD+6a_fo9iJSuAAsjhNXt12Ed=ga7F6y4Shw@mail.gmail.com>
	<1433273275587-11735.post@n5.nabble.com>
	<CAD_dpu0XPix6qH3CFc82ugkL5ki9b2eJb+4g9NfNzim1YS_=pw@mail.gmail.com>
	<1433274693890-11737.post@n5.nabble.com>
	<CAD_dpu3mLbFdKz9eQY25tQEoA1RO_ThfipNAPX6AowQqGpTbOA@mail.gmail.com>
	<CAPfhyfdGW=6kMzNjpS5NYbjCK3KAAecpR7e6xe6LTJ7dhn0F0w@mail.gmail.com>
	<CAD_dpu2NvgmebGHOHFy5BV4cbwm0NcG0iMffk6b+PD1FA2+n8g@mail.gmail.com>
	<CAPfhyfdxmNNrTLiMPUUkDtBk=So=QFq3685C1qovkwpV8zmioQ@mail.gmail.com>
Message-ID: <CAD_dpu2bwxYarrt_hHiPjciMaXd9HdT7rKijQ-dM6922X0vizw@mail.gmail.com>

On Tue, Jun 2, 2015 at 10:24 PM, delalis <delalis at gmail.com> wrote:

> So please correct me if I am wrong...
>
>   if we call register() and set our Java REST service in the config, we
> will need to take the payload passed into the REST service, parse out the
> device token (which you said is sent there automatically), and send that to
> Aerogear using the method we are already currently using to register device
> tokens with Aerogear in the Service? (since the REST service can talk to
> the UPS)
>
> is this correct??
>
Yes :)
But you can also keep the payload as is and just pass it to the UPS
endpoint (since it's already the payload he expects)

>
> On Tue, Jun 2, 2015 at 4:20 PM, Sebastien Blanc [via aerogear-dev] <[hidden
> email] <http:///user/SendEmail.jtp?type=node&node=11744&i=0>> wrote:
>
>> You don't have to worry about that :) the AeroGear push plugin will
>> already include the device token in the payload, in fact you don't have to
>> worry at all about the payload, just call register()
>>
>> On Tue, Jun 2, 2015 at 10:16 PM, delalis <[hidden email]
>> <http:///user/SendEmail.jtp?type=node&node=11743&i=0>> wrote:
>>
>>> ah okay.  I didnt think of putting the REST service in the config.  But
>>> then what would we pass to the REST service as the device token to pass to
>>> aerogear in the subsequent Java call?  in the classic push plugin, the
>>> onsuccess(event) came back with a device token that we would then send to
>>> the REST service to register with Aerogear using a Java call.
>>>
>>> On Tue, Jun 2, 2015 at 4:11 PM, Sebastien Blanc [via aerogear-dev] <[hidden
>>> email] <http:///user/SendEmail.jtp?type=node&node=11741&i=0>> wrote:
>>>
>>>>
>>>>
>>>> On Tue, Jun 2, 2015 at 9:51 PM, delalis <[hidden email]
>>>> <http:///user/SendEmail.jtp?type=node&node=11739&i=0>> wrote:
>>>>
>>>>> Thanks for writing back so quickly!
>>>>>
>>>>> 1) Can't your "Leatons" REST Service  proxy the register request to
>>>>> the push
>>>>> server ?
>>>>>
>>>>> ---Yes that is what we were doing before, the classic push plugin
>>>>> called
>>>>> register() which simply registered the token with APNS/GCM, and in the
>>>>> onSuccess function we would then send an AJAX call to Leatons REST
>>>>> service
>>>>> which would then put the device token we got back from the register()
>>>>> call
>>>>> into the Aerogear database using whatever methods Aerogears API exposed
>>>>> (sorry, I think that is what I meant by the Sender API)... so if you
>>>>> suggest
>>>>> using the REST service as a proxy to the push server and bypass the
>>>>> register() function altogether, how would we hook up the client
>>>>> onNotification() handler?
>>>>>
>>>>> 2) Or maybe just let Leaton accept the register request made by the
>>>>> aerogear
>>>>> plugin and store the json payload, later a service can submit that to
>>>>> the
>>>>> UnifiedPush Server.
>>>>> ---Again, how would we hook up the phonegap client onNotification()
>>>>> handler
>>>>> if we arent calling register from the clients javascript code??
>>>>>
>>>>
>>>> I meant  : you still use the plugin javascript code register() but just
>>>> make sure that your backend API (Leaton or whatever) accept the path and
>>>> the json payload so :
>>>>
>>>> POST http//myleatonservice/rest/registry/device  + JSON Payload
>>>>
>>>> You just point to "http//myleatonservice/rest" in you push-config,
>>>> "/registry/device" will be added automatically by the plugin.
>>>>
>>>> Could sound hacky but worth to explore.
>>>>
>>>> This way you still hookup your onNotification() handler
>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> View this message in context:
>>>>> http://aerogear-dev.1069024.n5.nabble.com/Android-Background-push-notifications-not-working-tp11716p11737.html
>>>>> Sent from the aerogear-dev mailing list archive at Nabble.com.
>>>>> _______________________________________________
>>>>> aerogear-dev mailing list
>>>>> [hidden email] <http:///user/SendEmail.jtp?type=node&node=11739&i=1>
>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> aerogear-dev mailing list
>>>> [hidden email] <http:///user/SendEmail.jtp?type=node&node=11739&i=2>
>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>
>>>> ------------------------------
>>>>  If you reply to this email, your message will be added to the
>>>> discussion below:
>>>>
>>>> http://aerogear-dev.1069024.n5.nabble.com/Android-Background-push-notifications-not-working-tp11716p11739.html
>>>>  To unsubscribe from Android Background push notifications not working, click
>>>> here.
>>>> NAML
>>>> <http://aerogear-dev.1069024.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>>>>
>>>
>>>
>>> ------------------------------
>>> View this message in context: Re: [aerogear-dev] Sndroid Background
>>> push notifications not working
>>> <http://aerogear-dev.1069024.n5.nabble.com/Android-Background-push-notifications-not-working-tp11716p11741.html>
>>>
>>> Sent from the aerogear-dev mailing list archive
>>> <http://aerogear-dev.1069024.n5.nabble.com/> at Nabble.com.
>>>
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> [hidden email] <http:///user/SendEmail.jtp?type=node&node=11743&i=1>
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> [hidden email] <http:///user/SendEmail.jtp?type=node&node=11743&i=2>
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>> ------------------------------
>>  If you reply to this email, your message will be added to the
>> discussion below:
>>
>> http://aerogear-dev.1069024.n5.nabble.com/Android-Background-push-notifications-not-working-tp11716p11743.html
>>  To unsubscribe from Android Background push notifications not working, click
>> here.
>> NAML
>> <http://aerogear-dev.1069024.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>>
>
>
> ------------------------------
> View this message in context: Re: [aerogear-dev] Sndroid Background push
> notifications not working
> <http://aerogear-dev.1069024.n5.nabble.com/Android-Background-push-notifications-not-working-tp11716p11744.html>
> Sent from the aerogear-dev mailing list archive
> <http://aerogear-dev.1069024.n5.nabble.com/> at Nabble.com.
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150602/49524cee/attachment-0001.html 

From delalis at gmail.com  Tue Jun  2 16:37:26 2015
From: delalis at gmail.com (Chris Delalis)
Date: Tue, 2 Jun 2015 16:37:26 -0400
Subject: [aerogear-dev] Sndroid Background push notifications not working
In-Reply-To: <CAD_dpu2bwxYarrt_hHiPjciMaXd9HdT7rKijQ-dM6922X0vizw@mail.gmail.com>
References: <CAD_dpu3NjfSSGBuDXVex6a5hupvv_TVm3qgrGXvwnvjc5uYrvw@mail.gmail.com>
	<CAO2B-fakcGpu_hK4YoPvny2ygG4xEtv4XMESeGZw3rQSB_cSww@mail.gmail.com>
	<1433270063187-11733.post@n5.nabble.com>
	<CAD_dpu1ZR-YgeajD+6a_fo9iJSuAAsjhNXt12Ed=ga7F6y4Shw@mail.gmail.com>
	<1433273275587-11735.post@n5.nabble.com>
	<CAD_dpu0XPix6qH3CFc82ugkL5ki9b2eJb+4g9NfNzim1YS_=pw@mail.gmail.com>
	<1433274693890-11737.post@n5.nabble.com>
	<CAD_dpu3mLbFdKz9eQY25tQEoA1RO_ThfipNAPX6AowQqGpTbOA@mail.gmail.com>
	<CAPfhyfdGW=6kMzNjpS5NYbjCK3KAAecpR7e6xe6LTJ7dhn0F0w@mail.gmail.com>
	<CAD_dpu2NvgmebGHOHFy5BV4cbwm0NcG0iMffk6b+PD1FA2+n8g@mail.gmail.com>
	<CAPfhyfdxmNNrTLiMPUUkDtBk=So=QFq3685C1qovkwpV8zmioQ@mail.gmail.com>
	<CAD_dpu2bwxYarrt_hHiPjciMaXd9HdT7rKijQ-dM6922X0vizw@mail.gmail.com>
Message-ID: <CAPfhyfdeHWWV5apUgg3cjEiKXKAiop7heO-L5K2saQOLcukdjw@mail.gmail.com>

Sounds good!  I will work on this tomorrow.  Again, I really appreciate
your help!!!

On Tue, Jun 2, 2015 at 4:36 PM, Sebastien Blanc <scm.blanc at gmail.com> wrote:

>
>
> On Tue, Jun 2, 2015 at 10:24 PM, delalis <delalis at gmail.com> wrote:
>
>> So please correct me if I am wrong...
>>
>>   if we call register() and set our Java REST service in the config, we
>> will need to take the payload passed into the REST service, parse out the
>> device token (which you said is sent there automatically), and send that to
>> Aerogear using the method we are already currently using to register device
>> tokens with Aerogear in the Service? (since the REST service can talk to
>> the UPS)
>>
>> is this correct??
>>
> Yes :)
> But you can also keep the payload as is and just pass it to the UPS
> endpoint (since it's already the payload he expects)
>
>>
>> On Tue, Jun 2, 2015 at 4:20 PM, Sebastien Blanc [via aerogear-dev] <[hidden
>> email] <http:///user/SendEmail.jtp?type=node&node=11744&i=0>> wrote:
>>
>>> You don't have to worry about that :) the AeroGear push plugin will
>>> already include the device token in the payload, in fact you don't have to
>>> worry at all about the payload, just call register()
>>>
>>> On Tue, Jun 2, 2015 at 10:16 PM, delalis <[hidden email]
>>> <http:///user/SendEmail.jtp?type=node&node=11743&i=0>> wrote:
>>>
>>>> ah okay.  I didnt think of putting the REST service in the config.  But
>>>> then what would we pass to the REST service as the device token to pass to
>>>> aerogear in the subsequent Java call?  in the classic push plugin, the
>>>> onsuccess(event) came back with a device token that we would then send to
>>>> the REST service to register with Aerogear using a Java call.
>>>>
>>>> On Tue, Jun 2, 2015 at 4:11 PM, Sebastien Blanc [via aerogear-dev] <[hidden
>>>> email] <http:///user/SendEmail.jtp?type=node&node=11741&i=0>> wrote:
>>>>
>>>>>
>>>>>
>>>>> On Tue, Jun 2, 2015 at 9:51 PM, delalis <[hidden email]
>>>>> <http:///user/SendEmail.jtp?type=node&node=11739&i=0>> wrote:
>>>>>
>>>>>> Thanks for writing back so quickly!
>>>>>>
>>>>>> 1) Can't your "Leatons" REST Service  proxy the register request to
>>>>>> the push
>>>>>> server ?
>>>>>>
>>>>>> ---Yes that is what we were doing before, the classic push plugin
>>>>>> called
>>>>>> register() which simply registered the token with APNS/GCM, and in the
>>>>>> onSuccess function we would then send an AJAX call to Leatons REST
>>>>>> service
>>>>>> which would then put the device token we got back from the register()
>>>>>> call
>>>>>> into the Aerogear database using whatever methods Aerogears API
>>>>>> exposed
>>>>>> (sorry, I think that is what I meant by the Sender API)... so if you
>>>>>> suggest
>>>>>> using the REST service as a proxy to the push server and bypass the
>>>>>> register() function altogether, how would we hook up the client
>>>>>> onNotification() handler?
>>>>>>
>>>>>> 2) Or maybe just let Leaton accept the register request made by the
>>>>>> aerogear
>>>>>> plugin and store the json payload, later a service can submit that to
>>>>>> the
>>>>>> UnifiedPush Server.
>>>>>> ---Again, how would we hook up the phonegap client onNotification()
>>>>>> handler
>>>>>> if we arent calling register from the clients javascript code??
>>>>>>
>>>>>
>>>>> I meant  : you still use the plugin javascript code register() but
>>>>> just make sure that your backend API (Leaton or whatever) accept the path
>>>>> and the json payload so :
>>>>>
>>>>> POST http//myleatonservice/rest/registry/device  + JSON Payload
>>>>>
>>>>> You just point to "http//myleatonservice/rest" in you push-config,
>>>>> "/registry/device" will be added automatically by the plugin.
>>>>>
>>>>> Could sound hacky but worth to explore.
>>>>>
>>>>> This way you still hookup your onNotification() handler
>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> View this message in context:
>>>>>> http://aerogear-dev.1069024.n5.nabble.com/Android-Background-push-notifications-not-working-tp11716p11737.html
>>>>>> Sent from the aerogear-dev mailing list archive at Nabble.com.
>>>>>> _______________________________________________
>>>>>> aerogear-dev mailing list
>>>>>> [hidden email] <http:///user/SendEmail.jtp?type=node&node=11739&i=1>
>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>>>
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> aerogear-dev mailing list
>>>>> [hidden email] <http:///user/SendEmail.jtp?type=node&node=11739&i=2>
>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>>
>>>>> ------------------------------
>>>>>  If you reply to this email, your message will be added to the
>>>>> discussion below:
>>>>>
>>>>> http://aerogear-dev.1069024.n5.nabble.com/Android-Background-push-notifications-not-working-tp11716p11739.html
>>>>>  To unsubscribe from Android Background push notifications not
>>>>> working, click here.
>>>>> NAML
>>>>> <http://aerogear-dev.1069024.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>>>>>
>>>>
>>>>
>>>> ------------------------------
>>>> View this message in context: Re: [aerogear-dev] Sndroid Background
>>>> push notifications not working
>>>> <http://aerogear-dev.1069024.n5.nabble.com/Android-Background-push-notifications-not-working-tp11716p11741.html>
>>>>
>>>> Sent from the aerogear-dev mailing list archive
>>>> <http://aerogear-dev.1069024.n5.nabble.com/> at Nabble.com.
>>>>
>>>> _______________________________________________
>>>> aerogear-dev mailing list
>>>> [hidden email] <http:///user/SendEmail.jtp?type=node&node=11743&i=1>
>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>
>>>
>>>
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> [hidden email] <http:///user/SendEmail.jtp?type=node&node=11743&i=2>
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>> ------------------------------
>>>  If you reply to this email, your message will be added to the
>>> discussion below:
>>>
>>> http://aerogear-dev.1069024.n5.nabble.com/Android-Background-push-notifications-not-working-tp11716p11743.html
>>>  To unsubscribe from Android Background push notifications not working, click
>>> here.
>>> NAML
>>> <http://aerogear-dev.1069024.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>>>
>>
>>
>> ------------------------------
>> View this message in context: Re: [aerogear-dev] Sndroid Background push
>> notifications not working
>> <http://aerogear-dev.1069024.n5.nabble.com/Android-Background-push-notifications-not-working-tp11716p11744.html>
>> Sent from the aerogear-dev mailing list archive
>> <http://aerogear-dev.1069024.n5.nabble.com/> at Nabble.com.
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150602/aa12ba2e/attachment.html 

From corinnekrych at gmail.com  Wed Jun  3 02:37:23 2015
From: corinnekrych at gmail.com (Corinne Krych)
Date: Wed, 3 Jun 2015 08:37:23 +0200
Subject: [aerogear-dev] APNS/UPS: With iOS 8.0 the 'alert' no longer
 just a string
In-Reply-To: <CAAg5f2Rdb_uFZdNYcw4_JgwzCOFxjBWkP_ncs81PDab0GrPSTA@mail.gmail.com>
References: <CAAg5f2Rdb_uFZdNYcw4_JgwzCOFxjBWkP_ncs81PDab0GrPSTA@mail.gmail.com>
Message-ID: <CAL8vO=dNWCi1bLZ-WjgLEFoxyYVJUFo5C6L3HyO7+qrfOyU0SA@mail.gmail.com>

Is there an option to move this payload from under alert to a dedicated
"ios" section as we have the "windows" one explained in UPS guide [1]?
With this option Cordova will still have to deal with extended ios features
for alert and we will have a new payload version.

Out of all options, I think a Cordova support need to be done anyway.

++
Corinne
[1] https://aerogear.org/docs/unifiedpush/push-message-format-dev/

On 2 June 2015 at 18:09, Matthias Wessendorf <matzew at apache.org> wrote:

> Hi,
>
> since iOS 8.0 we have the option for UI actions on the push notification:
>
> http://cdn.iphonehacks.com/wp-content/uploads/2014/06/lock-screen-notifications.jpg
>
> This is supported on java-apns and therefore on the UPS, however this
> causes the alert to be an object, and not a String, if the 'action' is
> provided.
> Another feature that is leveraging this is the support for Safari, there
> is a 'title' on the alert object, used by Apple Watch (iOS 8.3) as well.
>
> Sending always an object from the UPS to the APNs cloud breaks the Cordova
> code, since it's expecting a string.
>
> On the UPS I could do construct the object only if things like title or
> action are actually set. This would fix the issue on Cordova. However, this
> means that our Cordova code would not support the 'action', introduced in
> iOS 8.0
>
>
> I can see a few options:
> * for 1.1.0 -> do if/else and send object only if present. However, this
> would still mean the Cordova plugin has to check if the alert is just a
> string, to avoid crahes
> * for 1.2.0 (or 1.1.x, if really needed) -> Add Cordova support for alert
> being an object (helps for Apple Watch apps and supports the 'action')
>
> Any thoughts or other options?
>
> Thanks,
> Matthias
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150603/75e74c7d/attachment-0001.html 

From scm.blanc at gmail.com  Wed Jun  3 02:52:35 2015
From: scm.blanc at gmail.com (Sebastien Blanc)
Date: Wed, 3 Jun 2015 08:52:35 +0200
Subject: [aerogear-dev] APNS/UPS: With iOS 8.0 the 'alert' no longer
 just a string
In-Reply-To: <CAL8vO=dNWCi1bLZ-WjgLEFoxyYVJUFo5C6L3HyO7+qrfOyU0SA@mail.gmail.com>
References: <CAAg5f2Rdb_uFZdNYcw4_JgwzCOFxjBWkP_ncs81PDab0GrPSTA@mail.gmail.com>
	<CAL8vO=dNWCi1bLZ-WjgLEFoxyYVJUFo5C6L3HyO7+qrfOyU0SA@mail.gmail.com>
Message-ID: <CAD_dpu06hiF2YjCcL4LgqO5V1=HLSJM1m9RBb41JAGwyPJ7Pzg@mail.gmail.com>

On Wed, Jun 3, 2015 at 8:37 AM, Corinne Krych <corinnekrych at gmail.com>
wrote:

> Is there an option to move this payload from under alert to a dedicated
> "ios" section as we have the "windows" one explained in UPS guide [1]?
> With this option Cordova will still have to deal with extended ios
> features for alert and we will have a new payload version.
>
We have already an APNs section in our message format ;) [1] , "alert" is
not part of it since we use it for the other platforms as well.
However, even moving it there won't change anything since we are speaking
here about the payload the push network sent to the device not about our
UnifiedPush Message Format.
[1]
https://github.com/aerogear/aerogear-unifiedpush-java-client/blob/master/src/main/java/org/jboss/aerogear/unifiedpush/message/UnifiedMessage.java#L518

>
> Out of all options, I think a Cordova support need to be done anyway.
>
+1

>
> ++
> Corinne
> [1] https://aerogear.org/docs/unifiedpush/push-message-format-dev/
>
> On 2 June 2015 at 18:09, Matthias Wessendorf <matzew at apache.org> wrote:
>
>> Hi,
>>
>> since iOS 8.0 we have the option for UI actions on the push notification:
>>
>> http://cdn.iphonehacks.com/wp-content/uploads/2014/06/lock-screen-notifications.jpg
>>
>> This is supported on java-apns and therefore on the UPS, however this
>> causes the alert to be an object, and not a String, if the 'action' is
>> provided.
>> Another feature that is leveraging this is the support for Safari, there
>> is a 'title' on the alert object, used by Apple Watch (iOS 8.3) as well.
>>
>> Sending always an object from the UPS to the APNs cloud breaks the
>> Cordova code, since it's expecting a string.
>>
>> On the UPS I could do construct the object only if things like title or
>> action are actually set. This would fix the issue on Cordova. However, this
>> means that our Cordova code would not support the 'action', introduced in
>> iOS 8.0
>>
>>
>> I can see a few options:
>> * for 1.1.0 -> do if/else and send object only if present. However, this
>> would still mean the Cordova plugin has to check if the alert is just a
>> string, to avoid crahes
>> * for 1.2.0 (or 1.1.x, if really needed) -> Add Cordova support for alert
>> being an object (helps for Apple Watch apps and supports the 'action')
>>
>> Any thoughts or other options?
>>
>> Thanks,
>> Matthias
>>
>>
>> --
>> Matthias Wessendorf
>>
>> blog: http://matthiaswessendorf.wordpress.com/
>> sessions: http://www.slideshare.net/mwessendorf
>> twitter: http://twitter.com/mwessendorf
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150603/28f36f0e/attachment.html 

From matzew at apache.org  Wed Jun  3 03:45:21 2015
From: matzew at apache.org (Matthias Wessendorf)
Date: Wed, 3 Jun 2015 09:45:21 +0200
Subject: [aerogear-dev] APNS/UPS: With iOS 8.0 the 'alert' no longer
 just a string
In-Reply-To: <CAL8vO=dNWCi1bLZ-WjgLEFoxyYVJUFo5C6L3HyO7+qrfOyU0SA@mail.gmail.com>
References: <CAAg5f2Rdb_uFZdNYcw4_JgwzCOFxjBWkP_ncs81PDab0GrPSTA@mail.gmail.com>
	<CAL8vO=dNWCi1bLZ-WjgLEFoxyYVJUFo5C6L3HyO7+qrfOyU0SA@mail.gmail.com>
Message-ID: <CAAg5f2RcKmUfanB=8avwRiPgfXsjyc+=ca0k3teA3CVgoAeqOw@mail.gmail.com>

On Wed, Jun 3, 2015 at 8:37 AM, Corinne Krych <corinnekrych at gmail.com>
wrote:

> Is there an option to move this payload from under alert to a dedicated
> "ios" section as we have the "windows" one explained in UPS guide [1]?
> With this option Cordova will still have to deal with extended ios
> features for alert and we will have a new payload version.
>

right, since Cordova_iOS boils down to be... iOS :-)


> Out of all options, I think a Cordova support need to be done anyway.
>

I think so too


>
> ++
> Corinne
> [1] https://aerogear.org/docs/unifiedpush/push-message-format-dev/
>
> On 2 June 2015 at 18:09, Matthias Wessendorf <matzew at apache.org> wrote:
>
>> Hi,
>>
>> since iOS 8.0 we have the option for UI actions on the push notification:
>>
>> http://cdn.iphonehacks.com/wp-content/uploads/2014/06/lock-screen-notifications.jpg
>>
>> This is supported on java-apns and therefore on the UPS, however this
>> causes the alert to be an object, and not a String, if the 'action' is
>> provided.
>> Another feature that is leveraging this is the support for Safari, there
>> is a 'title' on the alert object, used by Apple Watch (iOS 8.3) as well.
>>
>> Sending always an object from the UPS to the APNs cloud breaks the
>> Cordova code, since it's expecting a string.
>>
>> On the UPS I could do construct the object only if things like title or
>> action are actually set. This would fix the issue on Cordova. However, this
>> means that our Cordova code would not support the 'action', introduced in
>> iOS 8.0
>>
>>
>> I can see a few options:
>> * for 1.1.0 -> do if/else and send object only if present. However, this
>> would still mean the Cordova plugin has to check if the alert is just a
>> string, to avoid crahes
>> * for 1.2.0 (or 1.1.x, if really needed) -> Add Cordova support for alert
>> being an object (helps for Apple Watch apps and supports the 'action')
>>
>> Any thoughts or other options?
>>
>> Thanks,
>> Matthias
>>
>>
>> --
>> Matthias Wessendorf
>>
>> blog: http://matthiaswessendorf.wordpress.com/
>> sessions: http://www.slideshare.net/mwessendorf
>> twitter: http://twitter.com/mwessendorf
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150603/1b74516f/attachment.html 

From edewit at redhat.com  Wed Jun  3 04:04:07 2015
From: edewit at redhat.com (Erik Jan de Wit)
Date: Wed, 3 Jun 2015 10:04:07 +0200
Subject: [aerogear-dev] APNS/UPS: With iOS 8.0 the 'alert' no longer
 just a string
In-Reply-To: <CAAg5f2RcKmUfanB=8avwRiPgfXsjyc+=ca0k3teA3CVgoAeqOw@mail.gmail.com>
References: <CAAg5f2Rdb_uFZdNYcw4_JgwzCOFxjBWkP_ncs81PDab0GrPSTA@mail.gmail.com>
	<CAL8vO=dNWCi1bLZ-WjgLEFoxyYVJUFo5C6L3HyO7+qrfOyU0SA@mail.gmail.com>
	<CAAg5f2RcKmUfanB=8avwRiPgfXsjyc+=ca0k3teA3CVgoAeqOw@mail.gmail.com>
Message-ID: <CAO2B-fauH82Ybv2GNbzVKp8UCW2jfju7o+pk8L_EaoEy85GsPg@mail.gmail.com>

So what the cordova plugin does now is take the payload it received
create a json from this and call the js interface. So as a 3rd option
we could also remove all the properties from the alert and leave only
the body in all cases. This only question is does one need to know the
title and action settings in the js or is can one suffice with the
alert text?

If needed the plugin can move these things to a ios specific object, I
would like to keep it as unified as possible the whole idea of our own
plugin was to eliminate the need for platform aware js code.

On Wed, Jun 3, 2015 at 9:45 AM, Matthias Wessendorf <matzew at apache.org> wrote:
>
>
> On Wed, Jun 3, 2015 at 8:37 AM, Corinne Krych <corinnekrych at gmail.com>
> wrote:
>>
>> Is there an option to move this payload from under alert to a dedicated
>> "ios" section as we have the "windows" one explained in UPS guide [1]?
>> With this option Cordova will still have to deal with extended ios
>> features for alert and we will have a new payload version.
>
>
> right, since Cordova_iOS boils down to be... iOS :-)
>
>>
>> Out of all options, I think a Cordova support need to be done anyway.
>
>
> I think so too
>
>>
>>
>> ++
>> Corinne
>> [1] https://aerogear.org/docs/unifiedpush/push-message-format-dev/
>>
>> On 2 June 2015 at 18:09, Matthias Wessendorf <matzew at apache.org> wrote:
>>>
>>> Hi,
>>>
>>> since iOS 8.0 we have the option for UI actions on the push notification:
>>>
>>> http://cdn.iphonehacks.com/wp-content/uploads/2014/06/lock-screen-notifications.jpg
>>>
>>> This is supported on java-apns and therefore on the UPS, however this
>>> causes the alert to be an object, and not a String, if the 'action' is
>>> provided.
>>> Another feature that is leveraging this is the support for Safari, there
>>> is a 'title' on the alert object, used by Apple Watch (iOS 8.3) as well.
>>>
>>> Sending always an object from the UPS to the APNs cloud breaks the
>>> Cordova code, since it's expecting a string.
>>>
>>> On the UPS I could do construct the object only if things like title or
>>> action are actually set. This would fix the issue on Cordova. However, this
>>> means that our Cordova code would not support the 'action', introduced in
>>> iOS 8.0
>>>
>>>
>>> I can see a few options:
>>> * for 1.1.0 -> do if/else and send object only if present. However, this
>>> would still mean the Cordova plugin has to check if the alert is just a
>>> string, to avoid crahes
>>> * for 1.2.0 (or 1.1.x, if really needed) -> Add Cordova support for alert
>>> being an object (helps for Apple Watch apps and supports the 'action')
>>>
>>> Any thoughts or other options?
>>>
>>> Thanks,
>>> Matthias
>>>
>>>
>>> --
>>> Matthias Wessendorf
>>>
>>> blog: http://matthiaswessendorf.wordpress.com/
>>> sessions: http://www.slideshare.net/mwessendorf
>>> twitter: http://twitter.com/mwessendorf
>>>
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>>
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev



-- 
Cheers,
       Erik Jan

From matzew at apache.org  Wed Jun  3 04:13:34 2015
From: matzew at apache.org (Matthias Wessendorf)
Date: Wed, 3 Jun 2015 10:13:34 +0200
Subject: [aerogear-dev] APNS/UPS: With iOS 8.0 the 'alert' no longer
 just a string
In-Reply-To: <CAO2B-fauH82Ybv2GNbzVKp8UCW2jfju7o+pk8L_EaoEy85GsPg@mail.gmail.com>
References: <CAAg5f2Rdb_uFZdNYcw4_JgwzCOFxjBWkP_ncs81PDab0GrPSTA@mail.gmail.com>
	<CAL8vO=dNWCi1bLZ-WjgLEFoxyYVJUFo5C6L3HyO7+qrfOyU0SA@mail.gmail.com>
	<CAAg5f2RcKmUfanB=8avwRiPgfXsjyc+=ca0k3teA3CVgoAeqOw@mail.gmail.com>
	<CAO2B-fauH82Ybv2GNbzVKp8UCW2jfju7o+pk8L_EaoEy85GsPg@mail.gmail.com>
Message-ID: <CAAg5f2RVx1RE9kCNUJHn0bhs6fHVLsfEx9sHjE5cruzN2NBViA@mail.gmail.com>

On Wed, Jun 3, 2015 at 10:04 AM, Erik Jan de Wit <edewit at redhat.com> wrote:

> So what the cordova plugin does now is take the payload it received
> create a json from this and call the js interface. So as a 3rd option
> we could also remove all the properties from the alert and leave only
> the body in all cases.


I think that's fine for now.


> This only question is does one need to know the
> title and action settings in the js or is can one suffice with the
> alert text?
>

@action: not sure, perhaps Corinne knows more.
@title: nope


>
> If needed the plugin can move these things to a ios specific object, I
> would like to keep it as unified as possible the whole idea of our own
> plugin was to eliminate the need for platform aware js code.
>
> On Wed, Jun 3, 2015 at 9:45 AM, Matthias Wessendorf <matzew at apache.org>
> wrote:
> >
> >
> > On Wed, Jun 3, 2015 at 8:37 AM, Corinne Krych <corinnekrych at gmail.com>
> > wrote:
> >>
> >> Is there an option to move this payload from under alert to a dedicated
> >> "ios" section as we have the "windows" one explained in UPS guide [1]?
> >> With this option Cordova will still have to deal with extended ios
> >> features for alert and we will have a new payload version.
> >
> >
> > right, since Cordova_iOS boils down to be... iOS :-)
> >
> >>
> >> Out of all options, I think a Cordova support need to be done anyway.
> >
> >
> > I think so too
> >
> >>
> >>
> >> ++
> >> Corinne
> >> [1] https://aerogear.org/docs/unifiedpush/push-message-format-dev/
> >>
> >> On 2 June 2015 at 18:09, Matthias Wessendorf <matzew at apache.org> wrote:
> >>>
> >>> Hi,
> >>>
> >>> since iOS 8.0 we have the option for UI actions on the push
> notification:
> >>>
> >>>
> http://cdn.iphonehacks.com/wp-content/uploads/2014/06/lock-screen-notifications.jpg
> >>>
> >>> This is supported on java-apns and therefore on the UPS, however this
> >>> causes the alert to be an object, and not a String, if the 'action' is
> >>> provided.
> >>> Another feature that is leveraging this is the support for Safari,
> there
> >>> is a 'title' on the alert object, used by Apple Watch (iOS 8.3) as
> well.
> >>>
> >>> Sending always an object from the UPS to the APNs cloud breaks the
> >>> Cordova code, since it's expecting a string.
> >>>
> >>> On the UPS I could do construct the object only if things like title or
> >>> action are actually set. This would fix the issue on Cordova. However,
> this
> >>> means that our Cordova code would not support the 'action', introduced
> in
> >>> iOS 8.0
> >>>
> >>>
> >>> I can see a few options:
> >>> * for 1.1.0 -> do if/else and send object only if present. However,
> this
> >>> would still mean the Cordova plugin has to check if the alert is just a
> >>> string, to avoid crahes
> >>> * for 1.2.0 (or 1.1.x, if really needed) -> Add Cordova support for
> alert
> >>> being an object (helps for Apple Watch apps and supports the 'action')
> >>>
> >>> Any thoughts or other options?
> >>>
> >>> Thanks,
> >>> Matthias
> >>>
> >>>
> >>> --
> >>> Matthias Wessendorf
> >>>
> >>> blog: http://matthiaswessendorf.wordpress.com/
> >>> sessions: http://www.slideshare.net/mwessendorf
> >>> twitter: http://twitter.com/mwessendorf
> >>>
> >>> _______________________________________________
> >>> aerogear-dev mailing list
> >>> aerogear-dev at lists.jboss.org
> >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >>
> >>
> >>
> >> _______________________________________________
> >> aerogear-dev mailing list
> >> aerogear-dev at lists.jboss.org
> >> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >
> >
> >
> >
> > --
> > Matthias Wessendorf
> >
> > blog: http://matthiaswessendorf.wordpress.com/
> > sessions: http://www.slideshare.net/mwessendorf
> > twitter: http://twitter.com/mwessendorf
> >
> > _______________________________________________
> > aerogear-dev mailing list
> > aerogear-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
>
> --
> Cheers,
>        Erik Jan
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150603/af19e41f/attachment-0001.html 

From matzew at apache.org  Wed Jun  3 05:18:07 2015
From: matzew at apache.org (Matthias Wessendorf)
Date: Wed, 3 Jun 2015 11:18:07 +0200
Subject: [aerogear-dev] FYI: Direct grants on KC
Message-ID: <CAAg5f2QGQVMh33_DGZinU_xb3CySD9j5BR4Yyr5AM9ZQY+GGPw@mail.gmail.com>

http://lists.jboss.org/pipermail/keycloak-dev/2015-June/004587.html

I think not only our QE team likes that proposal :)

-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150603/a26047c2/attachment.html 

From edewit at redhat.com  Wed Jun  3 05:55:37 2015
From: edewit at redhat.com (Erik Jan de Wit)
Date: Wed, 3 Jun 2015 11:55:37 +0200
Subject: [aerogear-dev] FYI: Direct grants on KC
In-Reply-To: <CAAg5f2QGQVMh33_DGZinU_xb3CySD9j5BR4Yyr5AM9ZQY+GGPw@mail.gmail.com>
References: <CAAg5f2QGQVMh33_DGZinU_xb3CySD9j5BR4Yyr5AM9ZQY+GGPw@mail.gmail.com>
Message-ID: <CAO2B-fZQJxwcCbJuU470iKDhUbXdySWoLxp3TYR2zuegYuq14A@mail.gmail.com>

why is having it on all the time is a problem?

On Wed, Jun 3, 2015 at 11:18 AM, Matthias Wessendorf <matzew at apache.org> wrote:
> http://lists.jboss.org/pipermail/keycloak-dev/2015-June/004587.html
>
> I think not only our QE team likes that proposal :)
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev



-- 
Cheers,
       Erik Jan

From matzew at apache.org  Wed Jun  3 06:36:46 2015
From: matzew at apache.org (Matthias Wessendorf)
Date: Wed, 3 Jun 2015 12:36:46 +0200
Subject: [aerogear-dev] FYI: Direct grants on KC
In-Reply-To: <CAO2B-fZQJxwcCbJuU470iKDhUbXdySWoLxp3TYR2zuegYuq14A@mail.gmail.com>
References: <CAAg5f2QGQVMh33_DGZinU_xb3CySD9j5BR4Yyr5AM9ZQY+GGPw@mail.gmail.com>
	<CAO2B-fZQJxwcCbJuU470iKDhUbXdySWoLxp3TYR2zuegYuq14A@mail.gmail.com>
Message-ID: <CAAg5f2Rf2kpX7VZKJMVYQn=QVGss-GiGFbQAfd25yGh0GeYo6w@mail.gmail.com>

Actually, I am happy to see that this will be always on, and I don't have a
problem w/ having them enabled all the time.
According to Stian this lands at KC 1.3,

\o/

Also, I am fine in changing that for 1.1.0 of UPS as well



On Wed, Jun 3, 2015 at 11:55 AM, Erik Jan de Wit <edewit at redhat.com> wrote:

> why is having it on all the time is a problem?
>
> On Wed, Jun 3, 2015 at 11:18 AM, Matthias Wessendorf <matzew at apache.org>
> wrote:
> > http://lists.jboss.org/pipermail/keycloak-dev/2015-June/004587.html
> >
> > I think not only our QE team likes that proposal :)
> >
> > --
> > Matthias Wessendorf
> >
> > blog: http://matthiaswessendorf.wordpress.com/
> > sessions: http://www.slideshare.net/mwessendorf
> > twitter: http://twitter.com/mwessendorf
> >
> > _______________________________________________
> > aerogear-dev mailing list
> > aerogear-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
>
> --
> Cheers,
>        Erik Jan
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150603/c7b60bd7/attachment.html 

From delalis at gmail.com  Wed Jun  3 16:22:14 2015
From: delalis at gmail.com (delalis)
Date: Wed, 3 Jun 2015 13:22:14 -0700 (MST)
Subject: [aerogear-dev] Sndroid Background push notifications not working
In-Reply-To: <CAPfhyfdeHWWV5apUgg3cjEiKXKAiop7heO-L5K2saQOLcukdjw@mail.gmail.com>
References: <CAD_dpu1ZR-YgeajD+6a_fo9iJSuAAsjhNXt12Ed=ga7F6y4Shw@mail.gmail.com>
	<1433273275587-11735.post@n5.nabble.com>
	<CAD_dpu0XPix6qH3CFc82ugkL5ki9b2eJb+4g9NfNzim1YS_=pw@mail.gmail.com>
	<1433274693890-11737.post@n5.nabble.com>
	<CAD_dpu3mLbFdKz9eQY25tQEoA1RO_ThfipNAPX6AowQqGpTbOA@mail.gmail.com>
	<CAPfhyfdGW=6kMzNjpS5NYbjCK3KAAecpR7e6xe6LTJ7dhn0F0w@mail.gmail.com>
	<CAD_dpu2NvgmebGHOHFy5BV4cbwm0NcG0iMffk6b+PD1FA2+n8g@mail.gmail.com>
	<CAPfhyfdxmNNrTLiMPUUkDtBk=So=QFq3685C1qovkwpV8zmioQ@mail.gmail.com>
	<CAD_dpu2bwxYarrt_hHiPjciMaXd9HdT7rKijQ-dM6922X0vizw@mail.gmail.com>
	<CAPfhyfdeHWWV5apUgg3cjEiKXKAiop7heO-L5K2saQOLcukdjw@mail.gmail.com>
Message-ID: <1433362934281-11755.post@n5.nabble.com>

Hi Sebastien, I tried to post to my REST server using the push.register()
function.  My PHP REST server receiving the call, but it doesnt look like
the JSON payload is in either the _GET or _POST params.

is there anything I am doing wrong?

var pushConfig = {
	pushServerURL: window.localStorage.getItem("site_path")+"/register_device",
	alias: "test",
	android: {
	senderID: "46901159####",
		          variantID: "test",
		          variantSecret: "test"
	}
};
		
push.register(onNotification, testSuccessHandler, testErrorHandler,
pushConfig);
-----------------------------------------------------------------------------------

Then on the PHP server I am doing this:
$allVals = "";
	
foreach ($_GET as $key => $value) {
		$allVals.= $key."=>".$value.", ";
}	
foreach ($_POST as $key2 => $value2) {
		$allVals.= $key2."=>".$value2.", ";
}	
watchdog('mobile_handler', 'all params passed:'.$allVals);
print($allVals);
---------------------------

My service is logging the transaction, but I am not getting any JSON payload
in either the GET or POST params containing a device token being sent to my
service.  

This is what it is logging (drupal site logs): all params
passed:q=>register_device/rest/registry/device,

So you were correct that it is tacking on /registry/device, but where is the
JSON payload??

thoughts?




--
View this message in context: http://aerogear-dev.1069024.n5.nabble.com/Android-Background-push-notifications-not-working-tp11716p11755.html
Sent from the aerogear-dev mailing list archive at Nabble.com.

From scm.blanc at gmail.com  Thu Jun  4 03:23:34 2015
From: scm.blanc at gmail.com (Sebastien Blanc)
Date: Thu, 4 Jun 2015 09:23:34 +0200
Subject: [aerogear-dev] Sndroid Background push notifications not working
In-Reply-To: <1433362934281-11755.post@n5.nabble.com>
References: <CAD_dpu1ZR-YgeajD+6a_fo9iJSuAAsjhNXt12Ed=ga7F6y4Shw@mail.gmail.com>
	<1433273275587-11735.post@n5.nabble.com>
	<CAD_dpu0XPix6qH3CFc82ugkL5ki9b2eJb+4g9NfNzim1YS_=pw@mail.gmail.com>
	<1433274693890-11737.post@n5.nabble.com>
	<CAD_dpu3mLbFdKz9eQY25tQEoA1RO_ThfipNAPX6AowQqGpTbOA@mail.gmail.com>
	<CAPfhyfdGW=6kMzNjpS5NYbjCK3KAAecpR7e6xe6LTJ7dhn0F0w@mail.gmail.com>
	<CAD_dpu2NvgmebGHOHFy5BV4cbwm0NcG0iMffk6b+PD1FA2+n8g@mail.gmail.com>
	<CAPfhyfdxmNNrTLiMPUUkDtBk=So=QFq3685C1qovkwpV8zmioQ@mail.gmail.com>
	<CAD_dpu2bwxYarrt_hHiPjciMaXd9HdT7rKijQ-dM6922X0vizw@mail.gmail.com>
	<CAPfhyfdeHWWV5apUgg3cjEiKXKAiop7heO-L5K2saQOLcukdjw@mail.gmail.com>
	<1433362934281-11755.post@n5.nabble.com>
Message-ID: <CAD_dpu0u0MJLKBZTZc7EqTx6XuWZ7wYBCrJJAh9sPu8TuCT3NA@mail.gmail.com>

Your config looks good, if think it's on the server side that you do
something wrong. I'm really rusty on the PHP side, haven't touched that for
10 years :) but make sure you read the body of your POST request , they are
no GET requests nor params. Looking on google, looks like you have to use
http://php.net/manual/en/function.http-get-request-body.php or something
like that.


On Wed, Jun 3, 2015 at 10:22 PM, delalis <delalis at gmail.com> wrote:

> Hi Sebastien, I tried to post to my REST server using the push.register()
> function.  My PHP REST server receiving the call, but it doesnt look like
> the JSON payload is in either the _GET or _POST params.
>
> is there anything I am doing wrong?
>
> var pushConfig = {
>         pushServerURL:
> window.localStorage.getItem("site_path")+"/register_device",
>         alias: "test",
>         android: {
>         senderID: "46901159####",
>                           variantID: "test",
>                           variantSecret: "test"
>         }
> };
>
> push.register(onNotification, testSuccessHandler, testErrorHandler,
> pushConfig);
>
> -----------------------------------------------------------------------------------
>
> Then on the PHP server I am doing this:
> $allVals = "";
>
> foreach ($_GET as $key => $value) {
>                 $allVals.= $key."=>".$value.", ";
> }
> foreach ($_POST as $key2 => $value2) {
>                 $allVals.= $key2."=>".$value2.", ";
> }
> watchdog('mobile_handler', 'all params passed:'.$allVals);
> print($allVals);
> ---------------------------
>
> My service is logging the transaction, but I am not getting any JSON
> payload
> in either the GET or POST params containing a device token being sent to my
> service.
>
> This is what it is logging (drupal site logs): all params
> passed:q=>register_device/rest/registry/device,
>
> So you were correct that it is tacking on /registry/device, but where is
> the
> JSON payload??
>
> thoughts?
>
>
>
>
> --
> View this message in context:
> http://aerogear-dev.1069024.n5.nabble.com/Android-Background-push-notifications-not-working-tp11716p11755.html
> Sent from the aerogear-dev mailing list archive at Nabble.com.
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150604/7878ae8f/attachment.html 

From delalis at gmail.com  Thu Jun  4 10:15:05 2015
From: delalis at gmail.com (delalis)
Date: Thu, 4 Jun 2015 07:15:05 -0700 (MST)
Subject: [aerogear-dev] Sndroid Background push notifications not working
In-Reply-To: <CAD_dpu0u0MJLKBZTZc7EqTx6XuWZ7wYBCrJJAh9sPu8TuCT3NA@mail.gmail.com>
References: <CAD_dpu0XPix6qH3CFc82ugkL5ki9b2eJb+4g9NfNzim1YS_=pw@mail.gmail.com>
	<1433274693890-11737.post@n5.nabble.com>
	<CAD_dpu3mLbFdKz9eQY25tQEoA1RO_ThfipNAPX6AowQqGpTbOA@mail.gmail.com>
	<CAPfhyfdGW=6kMzNjpS5NYbjCK3KAAecpR7e6xe6LTJ7dhn0F0w@mail.gmail.com>
	<CAD_dpu2NvgmebGHOHFy5BV4cbwm0NcG0iMffk6b+PD1FA2+n8g@mail.gmail.com>
	<CAPfhyfdxmNNrTLiMPUUkDtBk=So=QFq3685C1qovkwpV8zmioQ@mail.gmail.com>
	<CAD_dpu2bwxYarrt_hHiPjciMaXd9HdT7rKijQ-dM6922X0vizw@mail.gmail.com>
	<CAPfhyfdeHWWV5apUgg3cjEiKXKAiop7heO-L5K2saQOLcukdjw@mail.gmail.com>
	<1433362934281-11755.post@n5.nabble.com>
	<CAD_dpu0u0MJLKBZTZc7EqTx6XuWZ7wYBCrJJAh9sPu8TuCT3NA@mail.gmail.com>
Message-ID: <1433427305274-11757.post@n5.nabble.com>

That worked!  Well, Not the php function you referenced because you need an
HTTP extension installed on the server to use that function.  Instead we did
this:

parse_str(file_get_contents('php://input'), $_PUT);

foreach ($_PUT as $key => $value) {
	$allVals.= $key."=>".$value.", ";
}

$allVals="requestBody=>".$allVals;
print($allVals);

And it printed :
requestBody=>{"alias":"test","deviceToken":"APA91bEHALC9aRDBlJH-EeOHXgmxL_R750ur_6xoYng7FPlEJazeJ2F5DNWhlbwzzjipANhh3luFCVA07NtAi14zRxLO-n_GJ2xbicTve056NPkmAOGttNncXbG8A6_4PciRjsdjWoXx","deviceType":"ANDROID","operatingSystem":"android","osVersion":"5_0_2"}


So now we can send that to Aerogear.  Thanks for your help Sebi!



--
View this message in context: http://aerogear-dev.1069024.n5.nabble.com/Android-Background-push-notifications-not-working-tp11716p11757.html
Sent from the aerogear-dev mailing list archive at Nabble.com.

From matzew at apache.org  Fri Jun  5 10:58:41 2015
From: matzew at apache.org (Matthias Wessendorf)
Date: Fri, 5 Jun 2015 16:58:41 +0200
Subject: [aerogear-dev] Staging of UPS 1.1.0-beta.2
Message-ID: <CAAg5f2RymAcHAo2MhDtrBVbPx8xOaz+mDc5Hw+6LKUjfkGQRtw@mail.gmail.com>

Hi team,

here is the second beta release for the UPS 1.1.0. It contains more
features and improvements around UI, Keycloak_1.2.0 (w/ enabled direct
access grant) and a lot of other stuff:
https://issues.jboss.org/browse/AGPUSH/fixforversion/12326578

Please test the staged release:
https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-5745/

Like w/ the previous beta, please make sure you use a full profile WildFly
or EAP server for tests, since we now have JMS hooks ;-)
(See README for details)

On Wednesday I'd like to press the button to release it to the wild.

PS: For this beta release we won't yet be updating our Openshift cartridge
- that will stay on 1.0.3 (stable) for a little longer time. For the next
FINAL release in a few weeks we will get to this Openshift as well.

-Matthias

-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150605/ee0458b1/attachment-0001.html 

From matzew at apache.org  Mon Jun  8 04:44:01 2015
From: matzew at apache.org (Matthias Wessendorf)
Date: Mon, 8 Jun 2015 10:44:01 +0200
Subject: [aerogear-dev] Code freeze (was: Re: Staging of UPS 1.1.0-beta.2)
Message-ID: <CAAg5f2SGcYjtg+Ceu3DT2YB5xwzkCUx7Q0104aNht9b1Fncutw@mail.gmail.com>

Hi,

until we get the release out, there won't be any commit coming to master,
since we do a code freeze here, like we did in the past

On Fri, Jun 5, 2015 at 4:58 PM, Matthias Wessendorf <matzew at apache.org>
wrote:

> Hi team,
>
> here is the second beta release for the UPS 1.1.0. It contains more
> features and improvements around UI, Keycloak_1.2.0 (w/ enabled direct
> access grant) and a lot of other stuff:
> https://issues.jboss.org/browse/AGPUSH/fixforversion/12326578
>
> Please test the staged release:
>
> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-5745/
>
> Like w/ the previous beta, please make sure you use a full profile WildFly
> or EAP server for tests, since we now have JMS hooks ;-)
> (See README for details)
>
> On Wednesday I'd like to press the button to release it to the wild.
>
> PS: For this beta release we won't yet be updating our Openshift cartridge
> - that will stay on 1.0.3 (stable) for a little longer time. For the next
> FINAL release in a few weeks we will get to this Openshift as well.
>
> -Matthias
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>



-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150608/35e18cc1/attachment.html 

From bruno at abstractj.org  Mon Jun  8 09:43:46 2015
From: bruno at abstractj.org (Bruno Oliveira)
Date: Mon, 8 Jun 2015 10:43:46 -0300
Subject: [aerogear-dev] Code freeze (was: Re: Staging of UPS
	1.1.0-beta.2)
In-Reply-To: <CAAg5f2SGcYjtg+Ceu3DT2YB5xwzkCUx7Q0104aNht9b1Fncutw@mail.gmail.com>
References: <CAAg5f2SGcYjtg+Ceu3DT2YB5xwzkCUx7Q0104aNht9b1Fncutw@mail.gmail.com>
Message-ID: <CAM5SUC5ZY3LttZ2ttoFyS-Z9fnwOoTR9Vpc=7tmiKEAEP=DOVQ@mail.gmail.com>

Go ahead

+1

On Mon, Jun 8, 2015 at 5:44 AM, Matthias Wessendorf <matzew at apache.org>
wrote:

> Hi,
>
> until we get the release out, there won't be any commit coming to master,
> since we do a code freeze here, like we did in the past
>
> On Fri, Jun 5, 2015 at 4:58 PM, Matthias Wessendorf <matzew at apache.org>
> wrote:
>
>> Hi team,
>>
>> here is the second beta release for the UPS 1.1.0. It contains more
>> features and improvements around UI, Keycloak_1.2.0 (w/ enabled direct
>> access grant) and a lot of other stuff:
>> https://issues.jboss.org/browse/AGPUSH/fixforversion/12326578
>>
>> Please test the staged release:
>>
>> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-5745/
>>
>> Like w/ the previous beta, please make sure you use a full profile
>> WildFly or EAP server for tests, since we now have JMS hooks ;-)
>> (See README for details)
>>
>> On Wednesday I'd like to press the button to release it to the wild.
>>
>> PS: For this beta release we won't yet be updating our Openshift
>> cartridge - that will stay on 1.0.3 (stable) for a little longer time. For
>> the next FINAL release in a few weeks we will get to this Openshift as
>> well.
>>
>> -Matthias
>>
>> --
>> Matthias Wessendorf
>>
>> blog: http://matthiaswessendorf.wordpress.com/
>> sessions: http://www.slideshare.net/mwessendorf
>> twitter: http://twitter.com/mwessendorf
>>
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 

-- 
"The measure of a man is what he does with power" - Plato
-
@abstractj
-
Volenti Nihil Difficile
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150608/d0b43972/attachment.html 

From dpassos at redhat.com  Mon Jun  8 10:33:28 2015
From: dpassos at redhat.com (Daniel Passos)
Date: Mon, 8 Jun 2015 11:33:28 -0300
Subject: [aerogear-dev] What's new in AeroGear (6th June)
Message-ID: <CADF=h2uauMjcb8U-LxyPK9-MiSGkSFxOqoXy0e-KSDnPYZHUWw@mail.gmail.com>

Hey Guys,

This is our highlight for this week
Android

We decided to postpone the 2.2.0 release to add push configuration from
JSON. You can track it here <https://issues.jboss.org/browse/AGPUSH-1431>
iOS

Last week we implemented a plist based configuration file for ios-push
library. This week lots of news should come out of WWDC event. You can
expect some blog post and comments on the event for next week newsletter.
UPS

Beta.2 release candidate is on staging repo for tests:
http://lists.jboss.org/pipermail/aerogear-dev/2015-June/011659.html

Work on 1.1.0.Final will continue, after the beta.2 release is published
and the code-freeze time is over
?
-- 
-- Passos
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150608/d055bd51/attachment.html 

From matzew at apache.org  Wed Jun 10 10:45:19 2015
From: matzew at apache.org (Matthias Wessendorf)
Date: Wed, 10 Jun 2015 16:45:19 +0200
Subject: [aerogear-dev] Staging of UPS 1.1.0-beta.2
In-Reply-To: <CAAg5f2RymAcHAo2MhDtrBVbPx8xOaz+mDc5Hw+6LKUjfkGQRtw@mail.gmail.com>
References: <CAAg5f2RymAcHAo2MhDtrBVbPx8xOaz+mDc5Hw+6LKUjfkGQRtw@mail.gmail.com>
Message-ID: <CAAg5f2SOWY=EOwat8DJzReM00j9WE9uQesrMqbbMkhU6WFLhqw@mail.gmail.com>

Hi,

Stefan from our QE ask if we can delay the release to tomorrow,
test have been updated to beta.2 but he wants to web console and run some
demos.

IMO this is fine

On Fri, Jun 5, 2015 at 4:58 PM, Matthias Wessendorf <matzew at apache.org>
wrote:

> Hi team,
>
> here is the second beta release for the UPS 1.1.0. It contains more
> features and improvements around UI, Keycloak_1.2.0 (w/ enabled direct
> access grant) and a lot of other stuff:
> https://issues.jboss.org/browse/AGPUSH/fixforversion/12326578
>
> Please test the staged release:
>
> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-5745/
>
> Like w/ the previous beta, please make sure you use a full profile WildFly
> or EAP server for tests, since we now have JMS hooks ;-)
> (See README for details)
>
> On Wednesday I'd like to press the button to release it to the wild.
>
> PS: For this beta release we won't yet be updating our Openshift cartridge
> - that will stay on 1.0.3 (stable) for a little longer time. For the next
> FINAL release in a few weeks we will get to this Openshift as well.
>
> -Matthias
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>



-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150610/f5c53c6d/attachment.html 

From scm.blanc at gmail.com  Wed Jun 10 10:46:15 2015
From: scm.blanc at gmail.com (Sebastien Blanc)
Date: Wed, 10 Jun 2015 16:46:15 +0200
Subject: [aerogear-dev] Staging of UPS 1.1.0-beta.2
In-Reply-To: <CAAg5f2SOWY=EOwat8DJzReM00j9WE9uQesrMqbbMkhU6WFLhqw@mail.gmail.com>
References: <CAAg5f2RymAcHAo2MhDtrBVbPx8xOaz+mDc5Hw+6LKUjfkGQRtw@mail.gmail.com>
	<CAAg5f2SOWY=EOwat8DJzReM00j9WE9uQesrMqbbMkhU6WFLhqw@mail.gmail.com>
Message-ID: <CAD_dpu04U4pCfbD=hVej3F7px+LYuh6yDwrzLs6fPXnm+iSUhA@mail.gmail.com>

+1

On Wed, Jun 10, 2015 at 4:45 PM, Matthias Wessendorf <matzew at apache.org>
wrote:

> Hi,
>
> Stefan from our QE ask if we can delay the release to tomorrow,
> test have been updated to beta.2 but he wants to web console and run some
> demos.
>
> IMO this is fine
>
> On Fri, Jun 5, 2015 at 4:58 PM, Matthias Wessendorf <matzew at apache.org>
> wrote:
>
>> Hi team,
>>
>> here is the second beta release for the UPS 1.1.0. It contains more
>> features and improvements around UI, Keycloak_1.2.0 (w/ enabled direct
>> access grant) and a lot of other stuff:
>> https://issues.jboss.org/browse/AGPUSH/fixforversion/12326578
>>
>> Please test the staged release:
>>
>> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-5745/
>>
>> Like w/ the previous beta, please make sure you use a full profile
>> WildFly or EAP server for tests, since we now have JMS hooks ;-)
>> (See README for details)
>>
>> On Wednesday I'd like to press the button to release it to the wild.
>>
>> PS: For this beta release we won't yet be updating our Openshift
>> cartridge - that will stay on 1.0.3 (stable) for a little longer time. For
>> the next FINAL release in a few weeks we will get to this Openshift as
>> well.
>>
>> -Matthias
>>
>> --
>> Matthias Wessendorf
>>
>> blog: http://matthiaswessendorf.wordpress.com/
>> sessions: http://www.slideshare.net/mwessendorf
>> twitter: http://twitter.com/mwessendorf
>>
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150610/5805a84f/attachment-0001.html 

From matzew at apache.org  Wed Jun 10 12:09:02 2015
From: matzew at apache.org (Matthias Wessendorf)
Date: Wed, 10 Jun 2015 18:09:02 +0200
Subject: [aerogear-dev] Keycloak 1.3.0 (for UPS 1.1.0.Final)
Message-ID: <CAAg5f2S9V9BpqRk00LLgjNup5_fOSJnpA46u0RtUv4FvRkTbxw@mail.gmail.com>

Hi,

FYI I started looking at KC 1.3.0 support for UPS. On EAP 6.4.0 there is a
bug w/ the existing 1.3.0-SNAPSHOT. For details please check [1]

[1] https://issues.jboss.org/browse/AGPUSH-1447

-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150610/0bba6123/attachment.html 

From smikloso at redhat.com  Wed Jun 10 23:01:53 2015
From: smikloso at redhat.com (Stefan Miklosovic)
Date: Thu, 11 Jun 2015 05:01:53 +0200
Subject: [aerogear-dev] Staging of UPS 1.1.0-beta.2
In-Reply-To: <CAD_dpu04U4pCfbD=hVej3F7px+LYuh6yDwrzLs6fPXnm+iSUhA@mail.gmail.com>
References: <CAAg5f2RymAcHAo2MhDtrBVbPx8xOaz+mDc5Hw+6LKUjfkGQRtw@mail.gmail.com>
	<CAAg5f2SOWY=EOwat8DJzReM00j9WE9uQesrMqbbMkhU6WFLhqw@mail.gmail.com>
	<CAD_dpu04U4pCfbD=hVej3F7px+LYuh6yDwrzLs6fPXnm+iSUhA@mail.gmail.com>
Message-ID: <CALiy7HduwK3LVKBT9dLicbBxpenkQZFnyhAVZ483e9E=QR3Ttg@mail.gmail.com>

Hi,

I am mostly tracking what Tadeas found for Beta1 release.

1. While sending push notification from the browser, there is "No
variants" in variant selection by default. When I do not select any
variant, the message is sent to all variants. It should be renamed to
"All variants" instead "No variants" or it should be said that when
nothing is chosen, by default it will be sent everywhere.
2. For some reason there is a lot of space in the bottom and I can
scroll away all the content - minor issue.
3. In the last release, according to Tadeas, hovering over ? icons in
analytics panel did nothing - this is now repaired and works correctly
4. In the variant list, it was showing 0 delivered when something was
already sent and delivered. This is now repaired and it displays
numbers correctly.
5. In Sender API tab there was always Set up Java UPS on top of the
other sender platform. This is now repaired and it displays right
titles for every API.
6. Search in PushApplication list does not work (and I am not sure if
it is necessary as there should not be that many apps) - this was
removed, I do not see any search field anymore hence resolved.

Bugs:

1. After adding variant for simple push in the wizard, all links on
that variant page are dead - they do not do anything.

UI/UX Quirks

1. repaired - Variant creation dialog wraps text when there is a lot
of space [1]
2. repaired - The area between number of devices and edit button shows
the hand cursor, but it is not clickable. I would suggest to make it
clickable and the action would be expanding/collapsing the variant
detail -
3. dummy warnings are not there anymore
4. This is not changed in beta 2 and I agree with Tadeas about it -
When hitting the Edit variant button, it shows a dialog where I can
change only the name of the variant. However when I click the Change
network options button, I am presented with the possibility to change
both the name of the variant and the network specific configuration. I
would therefore suggest to not show the name field in the Change
network options dialog as it is not considered a good practise to have
two ways of doing the same thing in UI.
5. repaired, links are opened in new tab - Links to Android, Chrome,
iOS, Cordova etc. in variant detail should open the documentation in a
new tab like the rest of documentation links. Now it opens in the same
app which is not good because the user wants to stay in the Admin UI.

I tried helloworld quickstart on Android tablet, pushes arrived
without problems, I reinstalled my notebook few days ago so you can
imagine that the bootstraping of all development tools and compilation
of all libs was not so straighforward however I have to say that it
was overall smooth experience and I did it at the first shot.

Admin UI is very nice and responsive as well and I like it as Tadeas
does. Whoever made the decision to migrate to new visual look&feel did
a good job. I excersised UI quite a lot and I do not encounter any
usability nor performance issue.

I am overall satisfied with this release and I do not raise any
significant objections which would prevent the release of 1.1.0-beta.2
of UPS.

I would like to see the release of UPS Java client 1.0.0.Beta2 as
well. Right now there is not any beta2-aligned sender to UPS
1.1.0-beta.2. Beta1 sender is using unifiedpush-push-model of version
1.0.0-alpha2 so I expect that Java client will use parent 0.2.15 and
all bits will be aligned properly.

Regards

Stefan

On Wed, Jun 10, 2015 at 4:46 PM, Sebastien Blanc <scm.blanc at gmail.com> wrote:
> +1
>
> On Wed, Jun 10, 2015 at 4:45 PM, Matthias Wessendorf <matzew at apache.org>
> wrote:
>>
>> Hi,
>>
>> Stefan from our QE ask if we can delay the release to tomorrow,
>> test have been updated to beta.2 but he wants to web console and run some
>> demos.
>>
>> IMO this is fine
>>
>> On Fri, Jun 5, 2015 at 4:58 PM, Matthias Wessendorf <matzew at apache.org>
>> wrote:
>>>
>>> Hi team,
>>>
>>> here is the second beta release for the UPS 1.1.0. It contains more
>>> features and improvements around UI, Keycloak_1.2.0 (w/ enabled direct
>>> access grant) and a lot of other stuff:
>>> https://issues.jboss.org/browse/AGPUSH/fixforversion/12326578
>>>
>>> Please test the staged release:
>>>
>>> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-5745/
>>>
>>> Like w/ the previous beta, please make sure you use a full profile
>>> WildFly or EAP server for tests, since we now have JMS hooks ;-)
>>> (See README for details)
>>>
>>> On Wednesday I'd like to press the button to release it to the wild.
>>>
>>> PS: For this beta release we won't yet be updating our Openshift
>>> cartridge - that will stay on 1.0.3 (stable) for a little longer time. For
>>> the next FINAL release in a few weeks we will get to this Openshift as well.
>>>
>>> -Matthias
>>>
>>> --
>>> Matthias Wessendorf
>>>
>>> blog: http://matthiaswessendorf.wordpress.com/
>>> sessions: http://www.slideshare.net/mwessendorf
>>> twitter: http://twitter.com/mwessendorf
>>
>>
>>
>>
>> --
>> Matthias Wessendorf
>>
>> blog: http://matthiaswessendorf.wordpress.com/
>> sessions: http://www.slideshare.net/mwessendorf
>> twitter: http://twitter.com/mwessendorf
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev



-- 
Stefan Miklosovic
Red Hat Brno - JBoss Mobile Platform

e-mail: smikloso at redhat.com
irc: smikloso

From edewit at redhat.com  Thu Jun 11 02:13:58 2015
From: edewit at redhat.com (Erik Jan de Wit)
Date: Thu, 11 Jun 2015 08:13:58 +0200
Subject: [aerogear-dev] Version automatic update plugin
Message-ID: <CAO2B-fY8jOZb4D_UT7gxsuKbWaLH9X5rt1fT2rQN7=uceMLVGw@mail.gmail.com>

Hi,

As you know we have a open ticket creating a test application you can
push or pull new app content to easily test your app. This idea got me
thinking why not do that for production apps, instead of going through
the release process, of apple for instance, you could have the app
update itself on startup. It would need to be configured where to
check the version number and where to fetch the content. The content
could be a zip file or a git repo even, in the last case a release
could be as simple as a push to the production branch.

WDYT?

-- 
Cheers,
       Erik Jan

From matzew at apache.org  Thu Jun 11 02:44:43 2015
From: matzew at apache.org (Matthias Wessendorf)
Date: Thu, 11 Jun 2015 08:44:43 +0200
Subject: [aerogear-dev] Version automatic update plugin
In-Reply-To: <CAO2B-fY8jOZb4D_UT7gxsuKbWaLH9X5rt1fT2rQN7=uceMLVGw@mail.gmail.com>
References: <CAO2B-fY8jOZb4D_UT7gxsuKbWaLH9X5rt1fT2rQN7=uceMLVGw@mail.gmail.com>
Message-ID: <CAAg5f2QxzrWr9f9KLraf=kLsF7bHVgbCWZenFj6PC5HWfnLU6A@mail.gmail.com>

On Thu, Jun 11, 2015 at 8:13 AM, Erik Jan de Wit <edewit at redhat.com> wrote:

> Hi,
>
> As you know we have a open ticket creating a test application you can
> push or pull new app content to easily test your app.


which JIRA ticket exactly ?



> This idea got me
> thinking why not do that for production apps, instead of going through
> the release process, of apple for instance, you could have the app
> update itself on startup.


This works only for JavaScript - native code is not allowed to download and
execute code (Apple)


> It would need to be configured where to
> check the version number and where to fetch the content. The content
> could be a zip file or a git repo even, in the last case a release
> could be as simple as a push to the production branch.
>
> WDYT?
>

yeah, sounds reasonable, but I am not sure for what ticket we would need
this


>
> --
> Cheers,
>        Erik Jan
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150611/c8fff0b2/attachment.html 

From edewit at redhat.com  Thu Jun 11 02:57:46 2015
From: edewit at redhat.com (Erik Jan de Wit)
Date: Thu, 11 Jun 2015 08:57:46 +0200
Subject: [aerogear-dev] Version automatic update plugin
In-Reply-To: <CAAg5f2QxzrWr9f9KLraf=kLsF7bHVgbCWZenFj6PC5HWfnLU6A@mail.gmail.com>
References: <CAO2B-fY8jOZb4D_UT7gxsuKbWaLH9X5rt1fT2rQN7=uceMLVGw@mail.gmail.com>
	<CAAg5f2QxzrWr9f9KLraf=kLsF7bHVgbCWZenFj6PC5HWfnLU6A@mail.gmail.com>
Message-ID: <CAO2B-fatPE4F+LP2KLMMV2nuYvTsmEMYh2KOhKU0xkWguPz9sw@mail.gmail.com>

> which JIRA ticket exactly ?

https://issues.jboss.org/browse/AGCORDOVA-13

> This works only for JavaScript - native code is not allowed to download and
> execute code (Apple)

A cordova application is only html css and javascript so it could
update itself and apple will allow it.

From matzew at apache.org  Thu Jun 11 02:59:51 2015
From: matzew at apache.org (Matthias Wessendorf)
Date: Thu, 11 Jun 2015 08:59:51 +0200
Subject: [aerogear-dev] Version automatic update plugin
In-Reply-To: <CAO2B-fatPE4F+LP2KLMMV2nuYvTsmEMYh2KOhKU0xkWguPz9sw@mail.gmail.com>
References: <CAO2B-fY8jOZb4D_UT7gxsuKbWaLH9X5rt1fT2rQN7=uceMLVGw@mail.gmail.com>
	<CAAg5f2QxzrWr9f9KLraf=kLsF7bHVgbCWZenFj6PC5HWfnLU6A@mail.gmail.com>
	<CAO2B-fatPE4F+LP2KLMMV2nuYvTsmEMYh2KOhKU0xkWguPz9sw@mail.gmail.com>
Message-ID: <CAAg5f2Q+CsF3qVZ1JXUEj8Cdeeu20Q_pu_KE0i33Z4f7_z1_8A@mail.gmail.com>

On Thu, Jun 11, 2015 at 8:57 AM, Erik Jan de Wit <edewit at redhat.com> wrote:

> > which JIRA ticket exactly ?
>
> https://issues.jboss.org/browse/AGCORDOVA-13
>
> > This works only for JavaScript - native code is not allowed to download
> and
> > execute code (Apple)
>
> A cordova application is only html css and javascript so it could
> update itself and apple will allow it.
>

Correct, but I now really see this mail is just about Cordova :-)

Yeah, I like this auto update approach


> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150611/8624b9db/attachment.html 

From hrupp at redhat.com  Thu Jun 11 03:20:57 2015
From: hrupp at redhat.com (Heiko W.Rupp)
Date: Thu, 11 Jun 2015 09:20:57 +0200
Subject: [aerogear-dev] Version automatic update plugin
In-Reply-To: <CAO2B-fY8jOZb4D_UT7gxsuKbWaLH9X5rt1fT2rQN7=uceMLVGw@mail.gmail.com>
References: <CAO2B-fY8jOZb4D_UT7gxsuKbWaLH9X5rt1fT2rQN7=uceMLVGw@mail.gmail.com>
Message-ID: <E4050652-C40E-4179-905B-680267973901@redhat.com>

On 11 Jun 2015, at 8:13, Erik Jan de Wit wrote:

> the release process, of apple for instance, you could have the app
> update itself on startup. It would need to be configured where to

You mean something like $0 in-app purchases?
Would such an app pass the initial clearance for the
various stores given that especially Apple was in the past
very reserved wrt apps that loaded code from "the internet"

From lukas.fryc at gmail.com  Thu Jun 11 04:18:06 2015
From: lukas.fryc at gmail.com (=?UTF-8?B?THVrw6HFoSBGcnnEjQ==?=)
Date: Thu, 11 Jun 2015 08:18:06 +0000
Subject: [aerogear-dev] Version automatic update plugin
In-Reply-To: <E4050652-C40E-4179-905B-680267973901@redhat.com>
References: <CAO2B-fY8jOZb4D_UT7gxsuKbWaLH9X5rt1fT2rQN7=uceMLVGw@mail.gmail.com>
	<E4050652-C40E-4179-905B-680267973901@redhat.com>
Message-ID: <CAEroY361EkYZA55vStW8K1Cn4ieciVbuGqz=4UiXjGwpLTAkWw@mail.gmail.com>

If we limit ourselves to Cordova

there already solutions flowing arounds this idea,

Ionic even got it available for their offering few days ago:
http://blog.ionic.io/announcing-ionic-deploy-alpha-update-your-app-without-waiting/

You can get similar functionality from a Cordova ContentSync plugin:
http://slides.com/simonmacdonald/deck#/51

Apple allows self-updating WebKit apps as an exception:
http://slides.com/simonmacdonald/deck#/53
and long as you don't change purpose of the app.

?t 11. 6. 2015 v 9:21 odes?latel Heiko W.Rupp <hrupp at redhat.com> napsal:

> On 11 Jun 2015, at 8:13, Erik Jan de Wit wrote:
>
> > the release process, of apple for instance, you could have the app
> > update itself on startup. It would need to be configured where to
>
> You mean something like $0 in-app purchases?
> Would such an app pass the initial clearance for the
> various stores given that especially Apple was in the past
> very reserved wrt apps that loaded code from "the internet"
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150611/43d5d14b/attachment.html 

From idel.pivnitskiy at gmail.com  Thu Jun 11 04:38:29 2015
From: idel.pivnitskiy at gmail.com (Idel Pivnitskiy)
Date: Thu, 11 Jun 2015 11:38:29 +0300
Subject: [aerogear-dev] Question about next version of
	draft-thomson-webpush-protocol-00
Message-ID: <CAN+BUJr5y6fcYcfw1GAKpFHnXdBetAqap8nr+vCjMHrA44GO0A@mail.gmail.com>

Hello Martin, Elio and Brian,

Thanks for the great work on WebPush protocol!

I'm a student of NRNU MEPhI and this year I take part in GSoC [1] with
AeroGear team [2]. I'm working on experimental project, which is called
"Aerogear WebPush Server" [3].
I'm watching for updates of WebPush protocol and discussions in this
mailing list and I will update our project to support the latest version.
I want to know about your current plans, when do you plan to release a new
draft? Maybe you know an approximate month?

Best regards,
Idel Pivnitskiy

[1] https://www.google-melange.com/gsoc/homepage/google/gsoc2015
[2] https://aerogear.org/
[3] https://github.com/aerogear/aerogear-webpush-server
-- 
E-mail: Idel.Pivnitskiy at gmail.com
Twitter: @idelpivnitskiy <https://twitter.com/idelpivnitskiy>
GitHub: @idelpivnitskiy <https://github.com/idelpivnitskiy>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150611/c1a5776b/attachment.html 

From edewit at redhat.com  Thu Jun 11 04:42:25 2015
From: edewit at redhat.com (Erik Jan de Wit)
Date: Thu, 11 Jun 2015 10:42:25 +0200
Subject: [aerogear-dev] Version automatic update plugin
In-Reply-To: <CAEroY361EkYZA55vStW8K1Cn4ieciVbuGqz=4UiXjGwpLTAkWw@mail.gmail.com>
References: <CAO2B-fY8jOZb4D_UT7gxsuKbWaLH9X5rt1fT2rQN7=uceMLVGw@mail.gmail.com>
	<E4050652-C40E-4179-905B-680267973901@redhat.com>
	<CAEroY361EkYZA55vStW8K1Cn4ieciVbuGqz=4UiXjGwpLTAkWw@mail.gmail.com>
Message-ID: <CAO2B-fZkRPN8Depx5Kn8f+wbya3uqi6Yz5swcF0XyUs8ReDKUQ@mail.gmail.com>

Why do others keep stealing my ideas ;) I did a quick search but
couldn't find this plugin, well if it's already there it doesn't make
sense to build it.

On Thu, Jun 11, 2015 at 10:18 AM, Luk?? Fry? <lukas.fryc at gmail.com> wrote:
> If we limit ourselves to Cordova
>
> there already solutions flowing arounds this idea,
>
> Ionic even got it available for their offering few days ago:
> http://blog.ionic.io/announcing-ionic-deploy-alpha-update-your-app-without-waiting/
>
> You can get similar functionality from a Cordova ContentSync plugin:
> http://slides.com/simonmacdonald/deck#/51
>
> Apple allows self-updating WebKit apps as an exception:
> http://slides.com/simonmacdonald/deck#/53
> and long as you don't change purpose of the app.
>
> ?t 11. 6. 2015 v 9:21 odes?latel Heiko W.Rupp <hrupp at redhat.com> napsal:
>>
>> On 11 Jun 2015, at 8:13, Erik Jan de Wit wrote:
>>
>> > the release process, of apple for instance, you could have the app
>> > update itself on startup. It would need to be configured where to
>>
>> You mean something like $0 in-app purchases?
>> Would such an app pass the initial clearance for the
>> various stores given that especially Apple was in the past
>> very reserved wrt apps that loaded code from "the internet"
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev



-- 
Cheers,
       Erik Jan


From lukas.fryc at gmail.com  Thu Jun 11 04:57:46 2015
From: lukas.fryc at gmail.com (=?UTF-8?B?THVrw6HFoSBGcnnEjQ==?=)
Date: Thu, 11 Jun 2015 08:57:46 +0000
Subject: [aerogear-dev] Version automatic update plugin
In-Reply-To: <CAO2B-fZkRPN8Depx5Kn8f+wbya3uqi6Yz5swcF0XyUs8ReDKUQ@mail.gmail.com>
References: <CAO2B-fY8jOZb4D_UT7gxsuKbWaLH9X5rt1fT2rQN7=uceMLVGw@mail.gmail.com>
	<E4050652-C40E-4179-905B-680267973901@redhat.com>
	<CAEroY361EkYZA55vStW8K1Cn4ieciVbuGqz=4UiXjGwpLTAkWw@mail.gmail.com>
	<CAO2B-fZkRPN8Depx5Kn8f+wbya3uqi6Yz5swcF0XyUs8ReDKUQ@mail.gmail.com>
Message-ID: <CAEroY35AQEBBpnboJcEq807NiimxAs=fEa=Lw39LFkp4rVMjyA@mail.gmail.com>

Self updating is great selling point of Cordova based apps, lets make sure
to mention that in the presentations. I have to try this ContentSync myself.

Btw it some something what ServiceWorkers will allow us soon to do. :-)
On Thu 11 Jun 2015 at 10:42 Erik Jan de Wit <edewit at redhat.com> wrote:

> Why do others keep stealing my ideas ;) I did a quick search but
> couldn't find this plugin, well if it's already there it doesn't make
> sense to build it.
>
> On Thu, Jun 11, 2015 at 10:18 AM, Luk?? Fry? <lukas.fryc at gmail.com> wrote:
> > If we limit ourselves to Cordova
> >
> > there already solutions flowing arounds this idea,
> >
> > Ionic even got it available for their offering few days ago:
> >
> http://blog.ionic.io/announcing-ionic-deploy-alpha-update-your-app-without-waiting/
> >
> > You can get similar functionality from a Cordova ContentSync plugin:
> > http://slides.com/simonmacdonald/deck#/51
> >
> > Apple allows self-updating WebKit apps as an exception:
> > http://slides.com/simonmacdonald/deck#/53
> > and long as you don't change purpose of the app.
> >
> > ?t 11. 6. 2015 v 9:21 odes?latel Heiko W.Rupp <hrupp at redhat.com> napsal:
> >>
> >> On 11 Jun 2015, at 8:13, Erik Jan de Wit wrote:
> >>
> >> > the release process, of apple for instance, you could have the app
> >> > update itself on startup. It would need to be configured where to
> >>
> >> You mean something like $0 in-app purchases?
> >> Would such an app pass the initial clearance for the
> >> various stores given that especially Apple was in the past
> >> very reserved wrt apps that loaded code from "the internet"
> >> _______________________________________________
> >> aerogear-dev mailing list
> >> aerogear-dev at lists.jboss.org
> >> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >
> >
> > _______________________________________________
> > aerogear-dev mailing list
> > aerogear-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
>
> --
> Cheers,
>        Erik Jan
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150611/9c5606d1/attachment.html 

From matzew at apache.org  Thu Jun 11 05:24:41 2015
From: matzew at apache.org (Matthias Wessendorf)
Date: Thu, 11 Jun 2015 11:24:41 +0200
Subject: [aerogear-dev] Staging of UPS 1.1.0-beta.2
In-Reply-To: <CALiy7HduwK3LVKBT9dLicbBxpenkQZFnyhAVZ483e9E=QR3Ttg@mail.gmail.com>
References: <CAAg5f2RymAcHAo2MhDtrBVbPx8xOaz+mDc5Hw+6LKUjfkGQRtw@mail.gmail.com>
	<CAAg5f2SOWY=EOwat8DJzReM00j9WE9uQesrMqbbMkhU6WFLhqw@mail.gmail.com>
	<CAD_dpu04U4pCfbD=hVej3F7px+LYuh6yDwrzLs6fPXnm+iSUhA@mail.gmail.com>
	<CALiy7HduwK3LVKBT9dLicbBxpenkQZFnyhAVZ483e9E=QR3Ttg@mail.gmail.com>
Message-ID: <CAAg5f2Sc6Cs=-Dx7M1WHZFXYnnaHQbJ7K9dzF7e45tWxKeybsg@mail.gmail.com>

Hi Stefan,

thanks for the tests!


On Thu, Jun 11, 2015 at 5:01 AM, Stefan Miklosovic <smikloso at redhat.com>
wrote:

> Hi,
>
> I am mostly tracking what Tadeas found for Beta1 release.
>
> 1. While sending push notification from the browser, there is "No
> variants" in variant selection by default. When I do not select any
> variant, the message is sent to all variants. It should be renamed to
> "All variants" instead "No variants" or it should be said that when
> nothing is chosen, by default it will be sent everywhere.
>

I have created https://issues.jboss.org/browse/AGPUSH-1449




> 2. For some reason there is a lot of space in the bottom and I can
> scroll away all the content - minor issue.
>

Not sure I understand; bottom of where (and what browser)?
Mind filing a JIRA for this ?



> Bugs:
>
> 1. After adding variant for simple push in the wizard, all links on
> that variant page are dead - they do not do anything.
>


Hrm, worked for me (Chrome, incognito window). What browser did you use ?


>
> UI/UX Quirks
>
> 4. This is not changed in beta 2 and I agree with Tadeas about it -
> When hitting the Edit variant button, it shows a dialog where I can
> change only the name of the variant. However when I click the Change
> network options button, I am presented with the possibility to change
> both the name of the variant and the network specific configuration. I
> would therefore suggest to not show the name field in the Change
> network options dialog as it is not considered a good practise to have
> two ways of doing the same thing in UI.
>

I have created https://issues.jboss.org/browse/AGPUSH-1448



> I tried helloworld quickstart on Android tablet, pushes arrived
> without problems, I reinstalled my notebook few days ago so you can
> imagine that the bootstraping of all development tools and compilation
> of all libs was not so straighforward however I have to say that it
> was overall smooth experience and I did it at the first shot.
>

thanks, glad to hear. And yes, the tricky part is the 3rd party setup :-)


>
> Admin UI is very nice and responsive as well and I like it as Tadeas
> does. Whoever made the decision to migrate to new visual look&feel did
> a good job. I excersised UI quite a lot and I do not encounter any
> usability nor performance issue.
>

Andres drove the initiative w/ help from Lukas and?

>
> I am overall satisfied with this release and I do not raise any
> significant objections which would prevent the release of 1.1.0-beta.2
> of UPS.
>

awesome, will click the button


>
> I would like to see the release of UPS Java client 1.0.0.Beta2 as
> well. Right now there is not any beta2-aligned sender to UPS
> 1.1.0-beta.2. Beta1 sender is using unifiedpush-push-model of version
> 1.0.0-alpha2 so I expect that Java client will use parent 0.2.15 and
> all bits will be aligned properly.
>

fair point! This needs (and will be) to be fixed in Final.


Thanks again for the detailed report!

-Matthias


>
> Regards
>
> Stefan
>
> On Wed, Jun 10, 2015 at 4:46 PM, Sebastien Blanc <scm.blanc at gmail.com>
> wrote:
> > +1
> >
> > On Wed, Jun 10, 2015 at 4:45 PM, Matthias Wessendorf <matzew at apache.org>
> > wrote:
> >>
> >> Hi,
> >>
> >> Stefan from our QE ask if we can delay the release to tomorrow,
> >> test have been updated to beta.2 but he wants to web console and run
> some
> >> demos.
> >>
> >> IMO this is fine
> >>
> >> On Fri, Jun 5, 2015 at 4:58 PM, Matthias Wessendorf <matzew at apache.org>
> >> wrote:
> >>>
> >>> Hi team,
> >>>
> >>> here is the second beta release for the UPS 1.1.0. It contains more
> >>> features and improvements around UI, Keycloak_1.2.0 (w/ enabled direct
> >>> access grant) and a lot of other stuff:
> >>> https://issues.jboss.org/browse/AGPUSH/fixforversion/12326578
> >>>
> >>> Please test the staged release:
> >>>
> >>>
> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-5745/
> >>>
> >>> Like w/ the previous beta, please make sure you use a full profile
> >>> WildFly or EAP server for tests, since we now have JMS hooks ;-)
> >>> (See README for details)
> >>>
> >>> On Wednesday I'd like to press the button to release it to the wild.
> >>>
> >>> PS: For this beta release we won't yet be updating our Openshift
> >>> cartridge - that will stay on 1.0.3 (stable) for a little longer time.
> For
> >>> the next FINAL release in a few weeks we will get to this Openshift as
> well.
> >>>
> >>> -Matthias
> >>>
> >>> --
> >>> Matthias Wessendorf
> >>>
> >>> blog: http://matthiaswessendorf.wordpress.com/
> >>> sessions: http://www.slideshare.net/mwessendorf
> >>> twitter: http://twitter.com/mwessendorf
> >>
> >>
> >>
> >>
> >> --
> >> Matthias Wessendorf
> >>
> >> blog: http://matthiaswessendorf.wordpress.com/
> >> sessions: http://www.slideshare.net/mwessendorf
> >> twitter: http://twitter.com/mwessendorf
> >>
> >> _______________________________________________
> >> aerogear-dev mailing list
> >> aerogear-dev at lists.jboss.org
> >> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >
> >
> >
> > _______________________________________________
> > aerogear-dev mailing list
> > aerogear-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
>
> --
> Stefan Miklosovic
> Red Hat Brno - JBoss Mobile Platform
>
> e-mail: smikloso at redhat.com
> irc: smikloso
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150611/188e5e4a/attachment-0001.html 

From smikloso at redhat.com  Thu Jun 11 05:42:54 2015
From: smikloso at redhat.com (Stefan Miklosovic)
Date: Thu, 11 Jun 2015 11:42:54 +0200
Subject: [aerogear-dev] Staging of UPS 1.1.0-beta.2
In-Reply-To: <CAAg5f2Sc6Cs=-Dx7M1WHZFXYnnaHQbJ7K9dzF7e45tWxKeybsg@mail.gmail.com>
References: <CAAg5f2RymAcHAo2MhDtrBVbPx8xOaz+mDc5Hw+6LKUjfkGQRtw@mail.gmail.com>
	<CAAg5f2SOWY=EOwat8DJzReM00j9WE9uQesrMqbbMkhU6WFLhqw@mail.gmail.com>
	<CAD_dpu04U4pCfbD=hVej3F7px+LYuh6yDwrzLs6fPXnm+iSUhA@mail.gmail.com>
	<CALiy7HduwK3LVKBT9dLicbBxpenkQZFnyhAVZ483e9E=QR3Ttg@mail.gmail.com>
	<CAAg5f2Sc6Cs=-Dx7M1WHZFXYnnaHQbJ7K9dzF7e45tWxKeybsg@mail.gmail.com>
Message-ID: <CALiy7Hfxr21hoRD3mWD+YcXuzh_hSLWBGiN-r1hRkDSMwV+tMQ@mail.gmail.com>

On Thu, Jun 11, 2015 at 11:24 AM, Matthias Wessendorf <matzew at apache.org> wrote:
> Hi Stefan,
>
> thanks for the tests!
>
>
> On Thu, Jun 11, 2015 at 5:01 AM, Stefan Miklosovic <smikloso at redhat.com>
> wrote:
>>
>> Hi,
>>
>> I am mostly tracking what Tadeas found for Beta1 release.
>>
>> 1. While sending push notification from the browser, there is "No
>> variants" in variant selection by default. When I do not select any
>> variant, the message is sent to all variants. It should be renamed to
>> "All variants" instead "No variants" or it should be said that when
>> nothing is chosen, by default it will be sent everywhere.
>
>
> I have created https://issues.jboss.org/browse/AGPUSH-1449
>
>
>
>>
>> 2. For some reason there is a lot of space in the bottom and I can
>> scroll away all the content - minor issue.
>
>
> Not sure I understand; bottom of where (and what browser)?
> Mind filing a JIRA for this ?

I am using Chrome on CentOS. The thing is that you can scroll down the page
faaar down even there is nothing to see obviously as all UI elements
occupy the top of the page. I can just scroll down and see nothing.

>
>>
>> Bugs:
>>
>> 1. After adding variant for simple push in the wizard, all links on
>> that variant page are dead - they do not do anything.

As far as I remember they were inactive however maybe that was my bad,
i'll try to recheck it.

>
>
> Hrm, worked for me (Chrome, incognito window). What browser did you use ?
>>
>>
>> UI/UX Quirks
>>
>> 4. This is not changed in beta 2 and I agree with Tadeas about it -
>> When hitting the Edit variant button, it shows a dialog where I can
>> change only the name of the variant. However when I click the Change
>> network options button, I am presented with the possibility to change
>> both the name of the variant and the network specific configuration. I
>> would therefore suggest to not show the name field in the Change
>> network options dialog as it is not considered a good practise to have
>> two ways of doing the same thing in UI.
>
>
> I have created https://issues.jboss.org/browse/AGPUSH-1448
>
>
>>
>> I tried helloworld quickstart on Android tablet, pushes arrived
>> without problems, I reinstalled my notebook few days ago so you can
>> imagine that the bootstraping of all development tools and compilation
>> of all libs was not so straighforward however I have to say that it
>> was overall smooth experience and I did it at the first shot.
>
>
> thanks, glad to hear. And yes, the tricky part is the 3rd party setup :-)
>
>>
>>
>> Admin UI is very nice and responsive as well and I like it as Tadeas
>> does. Whoever made the decision to migrate to new visual look&feel did
>> a good job. I excersised UI quite a lot and I do not encounter any
>> usability nor performance issue.
>
>
> Andres drove the initiative w/ help from Lukas and?
>>
>>
>> I am overall satisfied with this release and I do not raise any
>> significant objections which would prevent the release of 1.1.0-beta.2
>> of UPS.
>
>
> awesome, will click the button
>
>>
>>
>> I would like to see the release of UPS Java client 1.0.0.Beta2 as
>> well. Right now there is not any beta2-aligned sender to UPS
>> 1.1.0-beta.2. Beta1 sender is using unifiedpush-push-model of version
>> 1.0.0-alpha2 so I expect that Java client will use parent 0.2.15 and
>> all bits will be aligned properly.
>
>
> fair point! This needs (and will be) to be fixed in Final.
>
>
> Thanks again for the detailed report!
>
> -Matthias
>
>>
>>
>> Regards
>>
>> Stefan
>>
>> On Wed, Jun 10, 2015 at 4:46 PM, Sebastien Blanc <scm.blanc at gmail.com>
>> wrote:
>> > +1
>> >
>> > On Wed, Jun 10, 2015 at 4:45 PM, Matthias Wessendorf <matzew at apache.org>
>> > wrote:
>> >>
>> >> Hi,
>> >>
>> >> Stefan from our QE ask if we can delay the release to tomorrow,
>> >> test have been updated to beta.2 but he wants to web console and run
>> >> some
>> >> demos.
>> >>
>> >> IMO this is fine
>> >>
>> >> On Fri, Jun 5, 2015 at 4:58 PM, Matthias Wessendorf <matzew at apache.org>
>> >> wrote:
>> >>>
>> >>> Hi team,
>> >>>
>> >>> here is the second beta release for the UPS 1.1.0. It contains more
>> >>> features and improvements around UI, Keycloak_1.2.0 (w/ enabled direct
>> >>> access grant) and a lot of other stuff:
>> >>> https://issues.jboss.org/browse/AGPUSH/fixforversion/12326578
>> >>>
>> >>> Please test the staged release:
>> >>>
>> >>>
>> >>> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-5745/
>> >>>
>> >>> Like w/ the previous beta, please make sure you use a full profile
>> >>> WildFly or EAP server for tests, since we now have JMS hooks ;-)
>> >>> (See README for details)
>> >>>
>> >>> On Wednesday I'd like to press the button to release it to the wild.
>> >>>
>> >>> PS: For this beta release we won't yet be updating our Openshift
>> >>> cartridge - that will stay on 1.0.3 (stable) for a little longer time.
>> >>> For
>> >>> the next FINAL release in a few weeks we will get to this Openshift as
>> >>> well.
>> >>>
>> >>> -Matthias
>> >>>
>> >>> --
>> >>> Matthias Wessendorf
>> >>>
>> >>> blog: http://matthiaswessendorf.wordpress.com/
>> >>> sessions: http://www.slideshare.net/mwessendorf
>> >>> twitter: http://twitter.com/mwessendorf
>> >>
>> >>
>> >>
>> >>
>> >> --
>> >> Matthias Wessendorf
>> >>
>> >> blog: http://matthiaswessendorf.wordpress.com/
>> >> sessions: http://www.slideshare.net/mwessendorf
>> >> twitter: http://twitter.com/mwessendorf
>> >>
>> >> _______________________________________________
>> >> aerogear-dev mailing list
>> >> aerogear-dev at lists.jboss.org
>> >> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>> >
>> >
>> >
>> > _______________________________________________
>> > aerogear-dev mailing list
>> > aerogear-dev at lists.jboss.org
>> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>>
>>
>> --
>> Stefan Miklosovic
>> Red Hat Brno - JBoss Mobile Platform
>>
>> e-mail: smikloso at redhat.com
>> irc: smikloso
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev



-- 
Stefan Miklosovic
Red Hat Brno - JBoss Mobile Platform

e-mail: smikloso at redhat.com
irc: smikloso

From lukas.fryc at gmail.com  Thu Jun 11 05:50:44 2015
From: lukas.fryc at gmail.com (=?UTF-8?B?THVrw6HFoSBGcnnEjQ==?=)
Date: Thu, 11 Jun 2015 09:50:44 +0000
Subject: [aerogear-dev] Staging of UPS 1.1.0-beta.2
In-Reply-To: <CAAg5f2Sc6Cs=-Dx7M1WHZFXYnnaHQbJ7K9dzF7e45tWxKeybsg@mail.gmail.com>
References: <CAAg5f2RymAcHAo2MhDtrBVbPx8xOaz+mDc5Hw+6LKUjfkGQRtw@mail.gmail.com>
	<CAAg5f2SOWY=EOwat8DJzReM00j9WE9uQesrMqbbMkhU6WFLhqw@mail.gmail.com>
	<CAD_dpu04U4pCfbD=hVej3F7px+LYuh6yDwrzLs6fPXnm+iSUhA@mail.gmail.com>
	<CALiy7HduwK3LVKBT9dLicbBxpenkQZFnyhAVZ483e9E=QR3Ttg@mail.gmail.com>
	<CAAg5f2Sc6Cs=-Dx7M1WHZFXYnnaHQbJ7K9dzF7e45tWxKeybsg@mail.gmail.com>
Message-ID: <CAEroY37xs=-DdWdYcWG_YYpr6Gh+DoaDzNs4Byg0bY77Vxbd0g@mail.gmail.com>

?t 11. 6. 2015 v 11:25 odes?latel Matthias Wessendorf <matzew at apache.org>
napsal:

> Hi Stefan,
>
> thanks for the tests!
>
>
> On Thu, Jun 11, 2015 at 5:01 AM, Stefan Miklosovic <smikloso at redhat.com>
> wrote:
>
>> Hi,
>>
>> I am mostly tracking what Tadeas found for Beta1 release.
>>
>> 1. While sending push notification from the browser, there is "No
>> variants" in variant selection by default. When I do not select any
>> variant, the message is sent to all variants. It should be renamed to
>> "All variants" instead "No variants" or it should be said that when
>> nothing is chosen, by default it will be sent everywhere.
>>
>
> I have created https://issues.jboss.org/browse/AGPUSH-1449
>


See my reaction here:
https://issues.jboss.org/browse/AGPUSH-1449?focusedCommentId=13077344&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13077344


>
>
>
>
>> 2. For some reason there is a lot of space in the bottom and I can
>> scroll away all the content - minor issue.
>>
>
> Not sure I understand; bottom of where (and what browser)?
> Mind filing a JIRA for this ?
>

This should be fixed imo, @Andres worked on that. I was not able to
reproduce is though and ?I'

>
>
>
>> Bugs:
>>
>> 1. After adding variant for simple push in the wizard, all links on
>> that variant page are dead - they do not do anything.
>>
>
>
>

> Hrm, worked for me (Chrome, incognito window). What browser did you use ?
>
>
>>
>> UI/UX Quirks
>
>
>>
>> 4. This is not changed in beta 2 and I agree with Tadeas about it -
>> When hitting the Edit variant button, it shows a dialog where I can
>> change only the name of the variant. However when I click the Change
>> network options button, I am presented with the possibility to change
>> both the name of the variant and the network specific configuration. I
>> would therefore suggest to not show the name field in the Change
>> network options dialog as it is not considered a good practise to have
>> two ways of doing the same thing in UI.
>>
>

>
> I have created https://issues.jboss.org/browse/AGPUSH-1448
>
>
>
>> I tried helloworld quickstart on Android tablet, pushes arrived
>> without problems, I reinstalled my notebook few days ago so you can
>> imagine that the bootstraping of all development tools and compilation
>> of all libs was not so straighforward however I have to say that it
>> was overall smooth experience and I did it at the first shot.
>>
>
> thanks, glad to hear. And yes, the tricky part is the 3rd party setup :-)
>
>
>>
>> Admin UI is very nice and responsive as well and I like it as Tadeas
>> does. Whoever made the decision to migrate to new visual look&feel did
>> a good job. I excersised UI quite a lot and I do not encounter any
>> usability nor performance issue.
>>
>
> Andres drove the initiative w/ help from Lukas and?
>
>>
>> I am overall satisfied with this release and I do not raise any
>> significant objections which would prevent the release of 1.1.0-beta.2
>> of UPS.
>>
>
> awesome, will click the button
>
>
>>
>> I would like to see the release of UPS Java client 1.0.0.Beta2 as
>> well. Right now there is not any beta2-aligned sender to UPS
>> 1.1.0-beta.2. Beta1 sender is using unifiedpush-push-model of version
>> 1.0.0-alpha2 so I expect that Java client will use parent 0.2.15 and
>> all bits will be aligned properly.
>>
>
> fair point! This needs (and will be) to be fixed in Final.
>
>
> Thanks again for the detailed report!
>
> -Matthias
>
>
>>
>> Regards
>>
>> Stefan
>>
>> On Wed, Jun 10, 2015 at 4:46 PM, Sebastien Blanc <scm.blanc at gmail.com>
>> wrote:
>> > +1
>> >
>> > On Wed, Jun 10, 2015 at 4:45 PM, Matthias Wessendorf <matzew at apache.org
>> >
>> > wrote:
>> >>
>> >> Hi,
>> >>
>> >> Stefan from our QE ask if we can delay the release to tomorrow,
>> >> test have been updated to beta.2 but he wants to web console and run
>> some
>> >> demos.
>> >>
>> >> IMO this is fine
>> >>
>> >> On Fri, Jun 5, 2015 at 4:58 PM, Matthias Wessendorf <matzew at apache.org
>> >
>> >> wrote:
>> >>>
>> >>> Hi team,
>> >>>
>> >>> here is the second beta release for the UPS 1.1.0. It contains more
>> >>> features and improvements around UI, Keycloak_1.2.0 (w/ enabled direct
>> >>> access grant) and a lot of other stuff:
>> >>> https://issues.jboss.org/browse/AGPUSH/fixforversion/12326578
>> >>>
>> >>> Please test the staged release:
>> >>>
>> >>>
>> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-5745/
>> >>>
>> >>> Like w/ the previous beta, please make sure you use a full profile
>> >>> WildFly or EAP server for tests, since we now have JMS hooks ;-)
>> >>> (See README for details)
>> >>>
>> >>> On Wednesday I'd like to press the button to release it to the wild.
>> >>>
>> >>> PS: For this beta release we won't yet be updating our Openshift
>> >>> cartridge - that will stay on 1.0.3 (stable) for a little longer
>> time. For
>> >>> the next FINAL release in a few weeks we will get to this Openshift
>> as well.
>> >>>
>> >>> -Matthias
>> >>>
>> >>> --
>> >>> Matthias Wessendorf
>> >>>
>> >>> blog: http://matthiaswessendorf.wordpress.com/
>> >>> sessions: http://www.slideshare.net/mwessendorf
>> >>> twitter: http://twitter.com/mwessendorf
>> >>
>> >>
>> >>
>> >>
>> >> --
>> >> Matthias Wessendorf
>> >>
>> >> blog: http://matthiaswessendorf.wordpress.com/
>> >> sessions: http://www.slideshare.net/mwessendorf
>> >> twitter: http://twitter.com/mwessendorf
>> >>
>> >> _______________________________________________
>> >> aerogear-dev mailing list
>> >> aerogear-dev at lists.jboss.org
>> >> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>> >
>> >
>> >
>> > _______________________________________________
>> > aerogear-dev mailing list
>> > aerogear-dev at lists.jboss.org
>> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>>
>>
>> --
>> Stefan Miklosovic
>> Red Hat Brno - JBoss Mobile Platform
>>
>> e-mail: smikloso at redhat.com
>> irc: smikloso
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>  _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150611/0d4cf78e/attachment-0001.html 

From matzew at apache.org  Thu Jun 11 07:21:25 2015
From: matzew at apache.org (Matthias Wessendorf)
Date: Thu, 11 Jun 2015 13:21:25 +0200
Subject: [aerogear-dev] [ANN] UnifiedPush Server 1.1.0-beta.2 is out
Message-ID: <CAAg5f2RjmQ4aHrZ=P6KJWfKtVi07KNYHDa80d7vH8jdvTa1mfQ@mail.gmail.com>

Folks,

the AeroGear team is happy to announce the second beta release for the UPS
1.1.0!

A list of highlights:
* Keycloak 1.2.0 usage (and by default enabled direct access grant)
* AngularJS 1.4 usage
* UI improvements
* Remove GCM iteration, due to JMS batching

All content for this release is is visible here:
https://issues.jboss.org/browse/AGPUSH/fixforversion/12326578

The items are downloadable on Github:
https://github.com/aerogear/aerogear-unifiedpush-server/releases/tag/1.1.0-beta.2

And the maven central repos should be sync'd by tomorrow morning (EU)

Have fun!
-Matthias


-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150611/326fbdee/attachment.html 

From matzew at apache.org  Fri Jun 12 10:41:45 2015
From: matzew at apache.org (Matthias Wessendorf)
Date: Fri, 12 Jun 2015 16:41:45 +0200
Subject: [aerogear-dev] Question about next version of
	draft-thomson-webpush-protocol-00
In-Reply-To: <CAN+BUJr5y6fcYcfw1GAKpFHnXdBetAqap8nr+vCjMHrA44GO0A@mail.gmail.com>
References: <CAN+BUJr5y6fcYcfw1GAKpFHnXdBetAqap8nr+vCjMHrA44GO0A@mail.gmail.com>
Message-ID: <CAAg5f2TadXfU_V9YmoAx+tNPgyXEGAgU_deA=_RDb6KpYuQaNw@mail.gmail.com>

Idel,

on the Mozilla #push channel, I got pointed to this newer draft:
https://unicorn-wg.github.io/webpush-protocol/

On that channel kitcambridge told me that the nightly FF is doing webpush,
instead of simplepush, when setting 'dom.push.serverURL, to an HTTPs
endpoint, following the above mentioned draft.

-Matthias


On Thu, Jun 11, 2015 at 10:38 AM, Idel Pivnitskiy <idel.pivnitskiy at gmail.com
> wrote:

> Hello Martin, Elio and Brian,
>
> Thanks for the great work on WebPush protocol!
>
> I'm a student of NRNU MEPhI and this year I take part in GSoC [1] with
> AeroGear team [2]. I'm working on experimental project, which is called
> "Aerogear WebPush Server" [3].
> I'm watching for updates of WebPush protocol and discussions in this
> mailing list and I will update our project to support the latest version.
> I want to know about your current plans, when do you plan to release a new
> draft? Maybe you know an approximate month?
>
> Best regards,
> Idel Pivnitskiy
>
> [1] https://www.google-melange.com/gsoc/homepage/google/gsoc2015
> [2] https://aerogear.org/
> [3] https://github.com/aerogear/aerogear-webpush-server
> --
> E-mail: Idel.Pivnitskiy at gmail.com
> Twitter: @idelpivnitskiy <https://twitter.com/idelpivnitskiy>
> GitHub: @idelpivnitskiy <https://github.com/idelpivnitskiy>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150612/eb3f5adf/attachment.html 

From idel.pivnitskiy at gmail.com  Sat Jun 13 05:48:47 2015
From: idel.pivnitskiy at gmail.com (Idel Pivnitskiy)
Date: Sat, 13 Jun 2015 12:48:47 +0300
Subject: [aerogear-dev] Question about next version of
	draft-thomson-webpush-protocol-00
In-Reply-To: <CAAg5f2TadXfU_V9YmoAx+tNPgyXEGAgU_deA=_RDb6KpYuQaNw@mail.gmail.com>
References: <CAN+BUJr5y6fcYcfw1GAKpFHnXdBetAqap8nr+vCjMHrA44GO0A@mail.gmail.com>
	<CAAg5f2TadXfU_V9YmoAx+tNPgyXEGAgU_deA=_RDb6KpYuQaNw@mail.gmail.com>
Message-ID: <CAN+BUJoDtPjAwXQAF2juYyeQDQG447ker-7vDzPo7VQzpdEzvg@mail.gmail.com>

Hi Matthias,

Good news about WebPush support in FF!

Yes, but after releasing this draft, there was some discussions in the
WebPush mailing list and new opened PRs on github. So, I want to know only
about plans to release the next draft.

Thanks,
Idel Pivnitskiy
-- 
E-mail: Idel.Pivnitskiy at gmail.com
Twitter: @idelpivnitskiy <https://twitter.com/idelpivnitskiy>
GitHub: @idelpivnitskiy <https://github.com/idelpivnitskiy>

2015-06-12 17:41 GMT+03:00 Matthias Wessendorf <matzew at apache.org>:

> Idel,
>
> on the Mozilla #push channel, I got pointed to this newer draft:
> https://unicorn-wg.github.io/webpush-protocol/
>
> On that channel kitcambridge told me that the nightly FF is doing webpush,
> instead of simplepush, when setting 'dom.push.serverURL, to an HTTPs
> endpoint, following the above mentioned draft.
>
> -Matthias
>
>
> On Thu, Jun 11, 2015 at 10:38 AM, Idel Pivnitskiy <
> idel.pivnitskiy at gmail.com> wrote:
>
>> Hello Martin, Elio and Brian,
>>
>> Thanks for the great work on WebPush protocol!
>>
>> I'm a student of NRNU MEPhI and this year I take part in GSoC [1] with
>> AeroGear team [2]. I'm working on experimental project, which is called
>> "Aerogear WebPush Server" [3].
>> I'm watching for updates of WebPush protocol and discussions in this
>> mailing list and I will update our project to support the latest version.
>> I want to know about your current plans, when do you plan to release a
>> new draft? Maybe you know an approximate month?
>>
>> Best regards,
>> Idel Pivnitskiy
>>
>> [1] https://www.google-melange.com/gsoc/homepage/google/gsoc2015
>> [2] https://aerogear.org/
>> [3] https://github.com/aerogear/aerogear-webpush-server
>> --
>> E-mail: Idel.Pivnitskiy at gmail.com
>> Twitter: @idelpivnitskiy <https://twitter.com/idelpivnitskiy>
>> GitHub: @idelpivnitskiy <https://github.com/idelpivnitskiy>
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150613/d8a7bd35/attachment.html 

From dpassos at redhat.com  Sun Jun 14 20:42:05 2015
From: dpassos at redhat.com (Daniel Passos)
Date: Sun, 14 Jun 2015 21:42:05 -0300
Subject: [aerogear-dev] AeroGear Android Push 2.2.0
Message-ID: <CADF=h2vVgw1UUGXHs+x=4zr12ZnC9Q=iAuw1z+OtVGQDtO=LFA@mail.gmail.com>

Hey Everyone,

We are ready to release AeroGear Android Push 2.2.0, we staged[1] it on
Nexus.

What is new in this version?

   - AGDROID-422 <https://issues.jboss.org/browse/AGDROID-422> - Add
   support for push-config.json for Android Push SDK
   - AGDROID-423 <https://issues.jboss.org/browse/AGDROID-423> - Android
   SDK hook for notifying the server if app has been opened due to a push



We?re planning to release it next Thursday.

Fell free to test it and let us know if you find any issues.

[1]
https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-5783/
?
-- 
-- Passos
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150614/b188c7e1/attachment.html 

From matzew at apache.org  Mon Jun 15 05:28:55 2015
From: matzew at apache.org (Matthias Wessendorf)
Date: Mon, 15 Jun 2015 11:28:55 +0200
Subject: [aerogear-dev] Openshift UPS cartridge updates
Message-ID: <CAAg5f2REGDeMsDg25NHDyPias+w_j9=SYdw-upp1kreacWm2xA@mail.gmail.com>

Hi,

currently we have the UPS server _and_ the SimplePush server on on
cartridge.

Since the UPS now is a full profile dependent server (JMS/HornetQ) is on,
I'd like to change remove the SimplePush Server from the cartridge.

For SimplePush, IMO it's best to have a standalone cartridge, that just is
Java based and fire up the Netty based server - no WildFly really needed,
just MySQL and the SimplePush server

Any thoughts?

-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150615/7508c1c5/attachment-0001.html 

From dpassos at redhat.com  Mon Jun 15 08:23:43 2015
From: dpassos at redhat.com (Daniel Passos)
Date: Mon, 15 Jun 2015 09:23:43 -0300
Subject: [aerogear-dev] Openshift UPS cartridge updates
In-Reply-To: <CAAg5f2REGDeMsDg25NHDyPias+w_j9=SYdw-upp1kreacWm2xA@mail.gmail.com>
References: <CAAg5f2REGDeMsDg25NHDyPias+w_j9=SYdw-upp1kreacWm2xA@mail.gmail.com>
Message-ID: <CADF=h2tP9uNG1G-xJSbgG+ju4QLwZ1mw-QiG=ewmoTaeb3q-2Q@mail.gmail.com>

+1

On Mon, Jun 15, 2015 at 6:28 AM, Matthias Wessendorf <matzew at apache.org>
wrote:

> Hi,
>
> currently we have the UPS server _and_ the SimplePush server on on
> cartridge.
>
> Since the UPS now is a full profile dependent server (JMS/HornetQ) is on,
> I'd like to change remove the SimplePush Server from the cartridge.
>
> For SimplePush, IMO it's best to have a standalone cartridge, that just is
> Java based and fire up the Netty based server - no WildFly really needed,
> just MySQL and the SimplePush server
>
> Any thoughts?
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 
-- Passos
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150615/d97428c9/attachment.html 

From matzew at apache.org  Mon Jun 15 08:42:43 2015
From: matzew at apache.org (Matthias Wessendorf)
Date: Mon, 15 Jun 2015 14:42:43 +0200
Subject: [aerogear-dev] AeroGear Android Push 2.2.0
In-Reply-To: <CADF=h2vVgw1UUGXHs+x=4zr12ZnC9Q=iAuw1z+OtVGQDtO=LFA@mail.gmail.com>
References: <CADF=h2vVgw1UUGXHs+x=4zr12ZnC9Q=iAuw1z+OtVGQDtO=LFA@mail.gmail.com>
Message-ID: <CAAg5f2QcCaXJjNUgjG3BmGuPDkRbzVx75EAYJ2rVErZiifMx=g@mail.gmail.com>

I noticed a little bug w/ the current libray

https://issues.jboss.org/browse/AGDROID-425



On Mon, Jun 15, 2015 at 2:42 AM, Daniel Passos <dpassos at redhat.com> wrote:

> Hey Everyone,
>
> We are ready to release AeroGear Android Push 2.2.0, we staged[1] it on
> Nexus.
>
> What is new in this version?
>
>    - AGDROID-422 <https://issues.jboss.org/browse/AGDROID-422> - Add
>    support for push-config.json for Android Push SDK
>    - AGDROID-423 <https://issues.jboss.org/browse/AGDROID-423> - Android
>    SDK hook for notifying the server if app has been opened due to a push
>
>
>
> We?re planning to release it next Thursday.
>
> Fell free to test it and let us know if you find any issues.
>
> [1]
> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-5783/
> ?
> --
> -- Passos
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150615/99846bef/attachment.html 

From supittma at redhat.com  Mon Jun 15 10:19:43 2015
From: supittma at redhat.com (Summers Pittman)
Date: Mon, 15 Jun 2015 10:19:43 -0400
Subject: [aerogear-dev] Ant in Android is currently Broken (with workaround)
Message-ID: <CAEQz2CtpbJFM6_q4hLi0YOTGskxpChs80HteoS+5gVERy6FLrw@mail.gmail.com>

Y'all,

Google broke ant in Android.  This means that, among other things, Cordova
is broken if you are using the latest tooling.  HOWEVER, I found a
workaround and this is tracked in Android's bug tracker.

If you are seeing an error along the lines of ${aapt} can not be found then
this affects you.

First the workaround :

add
```
    <property name="aapt" location="${sdk.dir}/build-tools/22.0.1/aapt" />
    <property name="aidl" location="${sdk.dir}/build-tools/22.0.1/aidl" />
    <property name="dx" location="${sdk.dir}/build-tools/22.0.1/dx" />
    <property name="zipalign"
location="${sdk.dir}/build-tools/22.0.1/zipalign" />
```

to $ANDROID_HOME/tools/ant/build.xml

Second, Google's bug report for tracking :

https://code.google.com/p/android/issues/detail?id=176488
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150615/e278bc08/attachment.html 

From matzew at apache.org  Mon Jun 15 10:45:38 2015
From: matzew at apache.org (Matthias Wessendorf)
Date: Mon, 15 Jun 2015 16:45:38 +0200
Subject: [aerogear-dev] Ant in Android is currently Broken (with
	workaround)
In-Reply-To: <CAEQz2CtpbJFM6_q4hLi0YOTGskxpChs80HteoS+5gVERy6FLrw@mail.gmail.com>
References: <CAEQz2CtpbJFM6_q4hLi0YOTGskxpChs80HteoS+5gVERy6FLrw@mail.gmail.com>
Message-ID: <CAAg5f2TBRNZVPnOEB=eCka6gteQgGWeL7FUuH8GgmF2O38d_+w@mail.gmail.com>

And yes, I ran into this too

https://github.com/jboss-mobile/unified-push-helloworld/pull/13#issuecomment-112071704

-Matthias

On Mon, Jun 15, 2015 at 4:19 PM, Summers Pittman <supittma at redhat.com>
wrote:

> Y'all,
>
> Google broke ant in Android.  This means that, among other things, Cordova
> is broken if you are using the latest tooling.  HOWEVER, I found a
> workaround and this is tracked in Android's bug tracker.
>
> If you are seeing an error along the lines of ${aapt} can not be found
> then this affects you.
>
> First the workaround :
>
> add
> ```
>     <property name="aapt" location="${sdk.dir}/build-tools/22.0.1/aapt" />
>     <property name="aidl" location="${sdk.dir}/build-tools/22.0.1/aidl" />
>     <property name="dx" location="${sdk.dir}/build-tools/22.0.1/dx" />
>     <property name="zipalign"
> location="${sdk.dir}/build-tools/22.0.1/zipalign" />
> ```
>
> to $ANDROID_HOME/tools/ant/build.xml
>
> Second, Google's bug report for tracking :
>
> https://code.google.com/p/android/issues/detail?id=176488
>
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150615/dfef8d53/attachment.html 

From lukas at fryc.eu  Mon Jun 15 11:31:01 2015
From: lukas at fryc.eu (=?UTF-8?B?THVrw6HFoSBGcnnEjQ==?=)
Date: Mon, 15 Jun 2015 17:31:01 +0200
Subject: [aerogear-dev] New diagrams for UPS clustering and metrics
	collection improvements
Message-ID: <CAEroY35BwnwtNR0THTDPNpPcR3bn0C2icc2RGqFKYN=PaLZr8g@mail.gmail.com>

Hi guys,

I'm finishing diagrams for the docs that cover how UPS using JMS works (or
will work in a near future) internally.

The concepts illustrated in (2) and (3) are not yet implemented, they are
just proposals,

that's why I would appreciate if you go through them, read callouts, and if
you have idea how to improve them, let us know!

*1. Overall picture:*
https://docs.google.com/drawings/d/13IsJWPSJNYXtst-UVxQYmzH36C_EXQMYYr_jcu7nFmE/edit?usp=sharing

*2. Token loading, dispatching and metrics collection in detail:*
https://docs.google.com/a/fryc.eu/drawings/d/12cUrYf7ACLYEoYsIWul2szN3lmQcYFMjjaZDq2fr9qQ/edit?usp=sharing

*3. Concept of limiting number of push dispatching sessions *
*(cluster-wide):*
https://docs.google.com/a/fryc.eu/drawings/d/12cUrYf7ACLYEoYsIWul2szN3lmQcYFMjjaZDq2fr9qQ/edit?usp=sharing


There are more details coming in form of UPS guide docs / appendix.

Cheers!

~ Lukas
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150615/97145f92/attachment-0001.html 

From matzew at apache.org  Mon Jun 15 11:44:09 2015
From: matzew at apache.org (Matthias Wessendorf)
Date: Mon, 15 Jun 2015 17:44:09 +0200
Subject: [aerogear-dev] What's new in AeroGear (June, 15th)
Message-ID: <CAAg5f2S6uT=4erauOVVG2eh3S9Q37DQz5sEHgVdZzzfDgiP93g@mail.gmail.com>

Hello there!

Here are this weeks highlights:


Android

We are about to release a new push version. Feel free to test it and let us
know if you find some bug.
http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-AeroGear-Android-Push-2-2-0-td11781.html
<https://gist.github.com/matzew/f28110d34f3fba35732d#ios-lovers>iOS lovers

Last week was WWDC events, as each year comes with its surprise and
breaking news, this year we've got: Swifty going Open Source. In AeroGear
we believe, this is super power! See oublog about it:
http://corinnekrych.blogspot.fr/2015/06/swift-new-super-power.html This
we'll explore in more details what's new in Swift2, expect a swift2 branch
to come :)
<https://gist.github.com/matzew/f28110d34f3fba35732d#push>Push

For the Unified Push our 1.1.0-beta.2 got released
<https://twitter.com/AeroGears/status/608957509764820992> and a nice guide
on how to use the Unified Push Server from FeedHenry has been published
<http://docs.feedhenry.com/v3/guides/app_development_push.html>!

On our Web Push effort we got good feedback from the Mozilla team on our
Web Push Console, and a nice PR from them got merged, to a branch
<https://github.com/aerogear/aerogear-webpush-server/pull/11>. Idel, our
GSoC student, is now getting up to spead and will look into the new draft
from the wg!
<https://gist.github.com/matzew/f28110d34f3fba35732d#misc-javascript>Misc
Javascript

   - Ember 1.13 and 2.0-beta release -
   http://emberjs.com/blog/2015/06/12/ember-1-13-0-released.html
   - Interesed in using ES6(the next generation of Javascript),
   https://babeljs.io/


-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150615/b3ef9ed0/attachment.html 

From lukas at fryc.eu  Mon Jun 15 11:53:20 2015
From: lukas at fryc.eu (=?UTF-8?B?THVrw6HFoSBGcnnEjQ==?=)
Date: Mon, 15 Jun 2015 17:53:20 +0200
Subject: [aerogear-dev] New diagrams for UPS clustering and metrics
	collection improvements
In-Reply-To: <CAEroY35BwnwtNR0THTDPNpPcR3bn0C2icc2RGqFKYN=PaLZr8g@mail.gmail.com>
References: <CAEroY35BwnwtNR0THTDPNpPcR3bn0C2icc2RGqFKYN=PaLZr8g@mail.gmail.com>
Message-ID: <CAEroY34_LBjaRd0f5o477e1oM06i66VSLR7t_kuEwQ1MpnD-ig@mail.gmail.com>

Small correction, here is (3):
https://docs.google.com/drawings/d/1Dt-ANkv7Z0PuyVjdkPrkH0ZAO8VOr8GbZ0dGmL5iXTw/edit?usp=sharing

On Mon, Jun 15, 2015 at 5:31 PM, Luk?? Fry? <lukas at fryc.eu> wrote:

> Hi guys,
>
> I'm finishing diagrams for the docs that cover how UPS using JMS works (or
> will work in a near future) internally.
>
> The concepts illustrated in (2) and (3) are not yet implemented, they are
> just proposals,
>
> that's why I would appreciate if you go through them, read callouts, and
> if you have idea how to improve them, let us know!
>
> *1. Overall picture:*
>
> https://docs.google.com/drawings/d/13IsJWPSJNYXtst-UVxQYmzH36C_EXQMYYr_jcu7nFmE/edit?usp=sharing
>
> *2. Token loading, dispatching and metrics collection in detail:*
>
> https://docs.google.com/a/fryc.eu/drawings/d/12cUrYf7ACLYEoYsIWul2szN3lmQcYFMjjaZDq2fr9qQ/edit?usp=sharing
>
> *3. Concept of limiting number of push dispatching sessions *
> *(cluster-wide):*
>
> https://docs.google.com/a/fryc.eu/drawings/d/12cUrYf7ACLYEoYsIWul2szN3lmQcYFMjjaZDq2fr9qQ/edit?usp=sharing
>
>
> There are more details coming in form of UPS guide docs / appendix.
>
> Cheers!
>
> ~ Lukas
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150615/c2e89eb0/attachment.html 

From matzew at apache.org  Mon Jun 15 21:39:48 2015
From: matzew at apache.org (Matthias Wessendorf)
Date: Tue, 16 Jun 2015 03:39:48 +0200
Subject: [aerogear-dev] Pixel fun with Keycloak Admin Console?
Message-ID: <CAAg5f2S+uWLw+eoYXk=h8kuo_G8D=vxYnai4TSg_1BRRcRCGAQ@mail.gmail.com>

Hi,

related to [1], I noticed a slight worse placing when I take a look at the
Keycloak Admin Console that comes w/ the UPS:
https://www.dropbox.com/s/92fbci7q322ppv6/Screen%20Shot%202015-06-16%20at%2003.16.38.png?dl=0

Looks like an issue w/ our theme/CSS?

-Matthias

[1] http://lists.jboss.org/pipermail/keycloak-dev/2015-June/004683.html


-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150616/77864333/attachment.html 

From matzew at apache.org  Mon Jun 15 21:47:16 2015
From: matzew at apache.org (Matthias Wessendorf)
Date: Tue, 16 Jun 2015 03:47:16 +0200
Subject: [aerogear-dev] SimplePush: Java Client release (0.2.0)
Message-ID: <CAAg5f2SUO30KGmFrN1pW=ASnQCJO8ANJF64eXqsFVRy-Na4ayw@mail.gmail.com>

Hi,

mainly to fix an issue w/ on the registration process w/ UPS, I'd like to
get a new version out:
https://github.com/aerogear/aerogear-simplepush-java-client/pull/7
(Noticed the bug when doing DevNation prep :-))

I have staged the JAR file here:
https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-5809/

Let me know if there are any concerns, otherwise I will push to Maven
Central on Thursday morning.

Thanks!
Matthias

-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150616/8d7f25a8/attachment.html 

From matzew at apache.org  Mon Jun 15 21:56:18 2015
From: matzew at apache.org (Matthias Wessendorf)
Date: Tue, 16 Jun 2015 03:56:18 +0200
Subject: [aerogear-dev] Java MPNS release (0.2.0)
Message-ID: <CAAg5f2RZKKLA0QOVNjBTc7Ww1JN3ZhgVhWP-H2EX4kiWdeJiTA@mail.gmail.com>

Hi,

for two bug fixes:
* AGPUSH-1451
* AGPUSH-1372

We need a new version, to be included in UPS 1.1.0.Final. The staging repo
is located here:
https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-5814/

Let me know if there are any concerns, otherwise I will release the JAR to
Maven central on Thursday morning

Thanks,
Matthias

-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150616/a6ebe730/attachment.html 

From avibelli at redhat.com  Tue Jun 16 03:12:02 2015
From: avibelli at redhat.com (Andrea Vibelli)
Date: Tue, 16 Jun 2015 00:12:02 -0700 (MST)
Subject: [aerogear-dev] Java MPNS release (0.2.0)
In-Reply-To: <CAAg5f2RZKKLA0QOVNjBTc7Ww1JN3ZhgVhWP-H2EX4kiWdeJiTA@mail.gmail.com>
References: <CAAg5f2RZKKLA0QOVNjBTc7Ww1JN3ZhgVhWP-H2EX4kiWdeJiTA@mail.gmail.com>
Message-ID: <1434438722367-11793.post@n5.nabble.com>

Thanks for merging Matt, 
+1 for release!

Andrea


Matthias Wessendorf wrote
> Hi,
> 
> for two bug fixes:
> * AGPUSH-1451
> * AGPUSH-1372
> 
> We need a new version, to be included in UPS 1.1.0.Final. The staging repo
> is located here:
> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-5814/
> 
> Let me know if there are any concerns, otherwise I will release the JAR to
> Maven central on Thursday morning
> 
> Thanks,
> Matthias
> 
> -- 
> Matthias Wessendorf
> 
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
> 
> _______________________________________________
> aerogear-dev mailing list

> aerogear-dev at .jboss

> https://lists.jboss.org/mailman/listinfo/aerogear-dev





--
View this message in context: http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-Java-MPNS-release-0-2-0-tp11792p11793.html
Sent from the aerogear-dev mailing list archive at Nabble.com.

From dpassos at redhat.com  Tue Jun 16 10:50:21 2015
From: dpassos at redhat.com (Daniel Passos)
Date: Tue, 16 Jun 2015 11:50:21 -0300
Subject: [aerogear-dev] AeroGear Android Push 2.2.0
In-Reply-To: <CAAg5f2QcCaXJjNUgjG3BmGuPDkRbzVx75EAYJ2rVErZiifMx=g@mail.gmail.com>
References: <CADF=h2vVgw1UUGXHs+x=4zr12ZnC9Q=iAuw1z+OtVGQDtO=LFA@mail.gmail.com>
	<CAAg5f2QcCaXJjNUgjG3BmGuPDkRbzVx75EAYJ2rVErZiifMx=g@mail.gmail.com>
Message-ID: <CADF=h2vO6zErixrULXSim_-PGTQaFcRsJ=y4n3BfJa5VreQZwg@mail.gmail.com>

Seems the problem was in the app not in the library. For more details
please see my comment[1] in Jira and the fix in this PR[2]

[1]
https://issues.jboss.org/browse/AGDROID-425?focusedCommentId=13079805&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13079805
[2] https://github.com/jboss-mobile/unified-push-helloworld/pull/14

On Mon, Jun 15, 2015 at 9:42 AM, Matthias Wessendorf <matzew at apache.org>
wrote:

> I noticed a little bug w/ the current libray
>
> https://issues.jboss.org/browse/AGDROID-425
>
>
>
> On Mon, Jun 15, 2015 at 2:42 AM, Daniel Passos <dpassos at redhat.com> wrote:
>
>> Hey Everyone,
>>
>> We are ready to release AeroGear Android Push 2.2.0, we staged[1] it on
>> Nexus.
>>
>> What is new in this version?
>>
>>    - AGDROID-422 <https://issues.jboss.org/browse/AGDROID-422> - Add
>>    support for push-config.json for Android Push SDK
>>    - AGDROID-423 <https://issues.jboss.org/browse/AGDROID-423> - Android
>>    SDK hook for notifying the server if app has been opened due to a push
>>
>>
>>
>> We?re planning to release it next Thursday.
>>
>> Fell free to test it and let us know if you find any issues.
>>
>> [1]
>> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-5783/
>> ?
>> --
>> -- Passos
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 
-- Passos
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150616/af9858a0/attachment.html 

From matzew at apache.org  Wed Jun 17 02:45:58 2015
From: matzew at apache.org (Matthias Wessendorf)
Date: Wed, 17 Jun 2015 08:45:58 +0200
Subject: [aerogear-dev] APNS/UPS: With iOS 8.0 the 'alert' no longer
 just a string
In-Reply-To: <CAO2B-fauH82Ybv2GNbzVKp8UCW2jfju7o+pk8L_EaoEy85GsPg@mail.gmail.com>
References: <CAAg5f2Rdb_uFZdNYcw4_JgwzCOFxjBWkP_ncs81PDab0GrPSTA@mail.gmail.com>
	<CAL8vO=dNWCi1bLZ-WjgLEFoxyYVJUFo5C6L3HyO7+qrfOyU0SA@mail.gmail.com>
	<CAAg5f2RcKmUfanB=8avwRiPgfXsjyc+=ca0k3teA3CVgoAeqOw@mail.gmail.com>
	<CAO2B-fauH82Ybv2GNbzVKp8UCW2jfju7o+pk8L_EaoEy85GsPg@mail.gmail.com>
Message-ID: <CAAg5f2QDCa66J41kZ4X7DS4CU_Ze4e58_ECGze79-4YGnmF8yg@mail.gmail.com>

Created https://issues.jboss.org/browse/AGCORDOVA-106 for this

On Wed, Jun 3, 2015 at 10:04 AM, Erik Jan de Wit <edewit at redhat.com> wrote:

> So what the cordova plugin does now is take the payload it received
> create a json from this and call the js interface. So as a 3rd option
> we could also remove all the properties from the alert and leave only
> the body in all cases. This only question is does one need to know the
> title and action settings in the js or is can one suffice with the
> alert text?
>
> If needed the plugin can move these things to a ios specific object, I
> would like to keep it as unified as possible the whole idea of our own
> plugin was to eliminate the need for platform aware js code.
>
> On Wed, Jun 3, 2015 at 9:45 AM, Matthias Wessendorf <matzew at apache.org>
> wrote:
> >
> >
> > On Wed, Jun 3, 2015 at 8:37 AM, Corinne Krych <corinnekrych at gmail.com>
> > wrote:
> >>
> >> Is there an option to move this payload from under alert to a dedicated
> >> "ios" section as we have the "windows" one explained in UPS guide [1]?
> >> With this option Cordova will still have to deal with extended ios
> >> features for alert and we will have a new payload version.
> >
> >
> > right, since Cordova_iOS boils down to be... iOS :-)
> >
> >>
> >> Out of all options, I think a Cordova support need to be done anyway.
> >
> >
> > I think so too
> >
> >>
> >>
> >> ++
> >> Corinne
> >> [1] https://aerogear.org/docs/unifiedpush/push-message-format-dev/
> >>
> >> On 2 June 2015 at 18:09, Matthias Wessendorf <matzew at apache.org> wrote:
> >>>
> >>> Hi,
> >>>
> >>> since iOS 8.0 we have the option for UI actions on the push
> notification:
> >>>
> >>>
> http://cdn.iphonehacks.com/wp-content/uploads/2014/06/lock-screen-notifications.jpg
> >>>
> >>> This is supported on java-apns and therefore on the UPS, however this
> >>> causes the alert to be an object, and not a String, if the 'action' is
> >>> provided.
> >>> Another feature that is leveraging this is the support for Safari,
> there
> >>> is a 'title' on the alert object, used by Apple Watch (iOS 8.3) as
> well.
> >>>
> >>> Sending always an object from the UPS to the APNs cloud breaks the
> >>> Cordova code, since it's expecting a string.
> >>>
> >>> On the UPS I could do construct the object only if things like title or
> >>> action are actually set. This would fix the issue on Cordova. However,
> this
> >>> means that our Cordova code would not support the 'action', introduced
> in
> >>> iOS 8.0
> >>>
> >>>
> >>> I can see a few options:
> >>> * for 1.1.0 -> do if/else and send object only if present. However,
> this
> >>> would still mean the Cordova plugin has to check if the alert is just a
> >>> string, to avoid crahes
> >>> * for 1.2.0 (or 1.1.x, if really needed) -> Add Cordova support for
> alert
> >>> being an object (helps for Apple Watch apps and supports the 'action')
> >>>
> >>> Any thoughts or other options?
> >>>
> >>> Thanks,
> >>> Matthias
> >>>
> >>>
> >>> --
> >>> Matthias Wessendorf
> >>>
> >>> blog: http://matthiaswessendorf.wordpress.com/
> >>> sessions: http://www.slideshare.net/mwessendorf
> >>> twitter: http://twitter.com/mwessendorf
> >>>
> >>> _______________________________________________
> >>> aerogear-dev mailing list
> >>> aerogear-dev at lists.jboss.org
> >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >>
> >>
> >>
> >> _______________________________________________
> >> aerogear-dev mailing list
> >> aerogear-dev at lists.jboss.org
> >> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >
> >
> >
> >
> > --
> > Matthias Wessendorf
> >
> > blog: http://matthiaswessendorf.wordpress.com/
> > sessions: http://www.slideshare.net/mwessendorf
> > twitter: http://twitter.com/mwessendorf
> >
> > _______________________________________________
> > aerogear-dev mailing list
> > aerogear-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
>
> --
> Cheers,
>        Erik Jan
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150617/a8cea604/attachment.html 

From scm.blanc at gmail.com  Wed Jun 17 03:17:05 2015
From: scm.blanc at gmail.com (Sebastien Blanc)
Date: Wed, 17 Jun 2015 09:17:05 +0200
Subject: [aerogear-dev] AeroGear Android Push 2.2.0
In-Reply-To: <CADF=h2vO6zErixrULXSim_-PGTQaFcRsJ=y4n3BfJa5VreQZwg@mail.gmail.com>
References: <CADF=h2vVgw1UUGXHs+x=4zr12ZnC9Q=iAuw1z+OtVGQDtO=LFA@mail.gmail.com>
	<CAAg5f2QcCaXJjNUgjG3BmGuPDkRbzVx75EAYJ2rVErZiifMx=g@mail.gmail.com>
	<CADF=h2vO6zErixrULXSim_-PGTQaFcRsJ=y4n3BfJa5VreQZwg@mail.gmail.com>
Message-ID: <CAD_dpu2u8iENYLASAOAD-EmmQp-nhT0qgCxt8sfvrxjr5y0v+w@mail.gmail.com>

This fix is more a workaround since it was not needed with the previous
versions.  so we need to be sure to check if :

- This fix was needed because of other commits on the helloworld
- This fix was needed because of the new version of the library
- This fix was needed because of a change from GCM server
- This fix was needed because of a mix/combination of all the previous
potential causes

Passos have you been able to test the lib with Aerodoc ?

Sebi




On Tue, Jun 16, 2015 at 4:50 PM, Daniel Passos <dpassos at redhat.com> wrote:

> Seems the problem was in the app not in the library. For more details
> please see my comment[1] in Jira and the fix in this PR[2]
>
> [1]
> https://issues.jboss.org/browse/AGDROID-425?focusedCommentId=13079805&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13079805
> [2] https://github.com/jboss-mobile/unified-push-helloworld/pull/14
>
> On Mon, Jun 15, 2015 at 9:42 AM, Matthias Wessendorf <matzew at apache.org>
> wrote:
>
>> I noticed a little bug w/ the current libray
>>
>> https://issues.jboss.org/browse/AGDROID-425
>>
>>
>>
>> On Mon, Jun 15, 2015 at 2:42 AM, Daniel Passos <dpassos at redhat.com>
>> wrote:
>>
>>> Hey Everyone,
>>>
>>> We are ready to release AeroGear Android Push 2.2.0, we staged[1] it on
>>> Nexus.
>>>
>>> What is new in this version?
>>>
>>>    - AGDROID-422 <https://issues.jboss.org/browse/AGDROID-422> - Add
>>>    support for push-config.json for Android Push SDK
>>>    - AGDROID-423 <https://issues.jboss.org/browse/AGDROID-423> -
>>>    Android SDK hook for notifying the server if app has been opened due to a
>>>    push
>>>
>>>
>>>
>>> We?re planning to release it next Thursday.
>>>
>>> Fell free to test it and let us know if you find any issues.
>>>
>>> [1]
>>> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-5783/
>>> ?
>>> --
>>> -- Passos
>>>
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>
>>
>>
>> --
>> Matthias Wessendorf
>>
>> blog: http://matthiaswessendorf.wordpress.com/
>> sessions: http://www.slideshare.net/mwessendorf
>> twitter: http://twitter.com/mwessendorf
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
>
> --
> -- Passos
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150617/6f2ea1f1/attachment-0001.html 

From scm.blanc at gmail.com  Wed Jun 17 05:44:11 2015
From: scm.blanc at gmail.com (Sebastien Blanc)
Date: Wed, 17 Jun 2015 11:44:11 +0200
Subject: [aerogear-dev] SimplePush: Java Client release (0.2.0)
In-Reply-To: <CAAg5f2SUO30KGmFrN1pW=ASnQCJO8ANJF64eXqsFVRy-Na4ayw@mail.gmail.com>
References: <CAAg5f2SUO30KGmFrN1pW=ASnQCJO8ANJF64eXqsFVRy-Na4ayw@mail.gmail.com>
Message-ID: <CAD_dpu2aYTNi8x_rFZrCY6hHddT8J3amqf0C=XZ9upyCt=asKQ@mail.gmail.com>

Ship it !

On Tue, Jun 16, 2015 at 3:47 AM, Matthias Wessendorf <matzew at apache.org>
wrote:

> Hi,
>
> mainly to fix an issue w/ on the registration process w/ UPS, I'd like to
> get a new version out:
> https://github.com/aerogear/aerogear-simplepush-java-client/pull/7
> (Noticed the bug when doing DevNation prep :-))
>
> I have staged the JAR file here:
>
> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-5809/
>
> Let me know if there are any concerns, otherwise I will push to Maven
> Central on Thursday morning.
>
> Thanks!
> Matthias
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150617/0a8f2c79/attachment.html 

From supittma at redhat.com  Wed Jun 17 10:03:41 2015
From: supittma at redhat.com (Summers Pittman)
Date: Wed, 17 Jun 2015 10:03:41 -0400
Subject: [aerogear-dev] GCM 3.0 and Instance ID
Message-ID: <CAEQz2Cs2WwZBruMxXN+Phyu4qwJ77gG7KOYDE9SUoLtAmP=S3w@mail.gmail.com>

Sooooo we have a 2.2.0 staged.  Google has a ton of new functionality
rolling out for GCM.

We think that 2.2.0 works with it mostly correctly but we are finding some
"gotchas".  Notably it looks like Google is sending some ACK messages after
we register that the library is ignoring.

We will need to support InstanceID (tl;dr; Google is enhancing
registraiton_id).  Passos and I are still digesting the volumes of stuff
being rolled out from IO so we can't really give too many details right now
because we simply don't know them (And Google is still updating their docs,
fixing links, etc).

So the question to the list is :
 Do we delay 2.2.0 and include support for InstanceID and any other best
practices Google has introduced or do we release 2.2.0, document / work
around any gotchas and then prioritize GCM 3.0 support for 2.3.0?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150617/e3a580fa/attachment.html 

From matzew at apache.org  Wed Jun 17 10:28:10 2015
From: matzew at apache.org (Matthias Wessendorf)
Date: Wed, 17 Jun 2015 16:28:10 +0200
Subject: [aerogear-dev] GCM 3.0 and Instance ID
In-Reply-To: <CAEQz2Cs2WwZBruMxXN+Phyu4qwJ77gG7KOYDE9SUoLtAmP=S3w@mail.gmail.com>
References: <CAEQz2Cs2WwZBruMxXN+Phyu4qwJ77gG7KOYDE9SUoLtAmP=S3w@mail.gmail.com>
Message-ID: <CAAg5f2To7ujXR=+kd69fJi0Nkx6xd8QFT_LGQ92udY-guLVgdw@mail.gmail.com>

Hi,

On Wed, Jun 17, 2015 at 4:03 PM, Summers Pittman <supittma at redhat.com>
wrote:

> Sooooo we have a 2.2.0 staged.  Google has a ton of new functionality
> rolling out for GCM.
>
> We think that 2.2.0 works with it mostly correctly but we are finding some
> "gotchas".  Notably it looks like Google is sending some ACK messages after
> we register that the library is ignoring.
>
> We will need to support InstanceID (tl;dr; Google is enhancing
> registraiton_id).  Passos and I are still digesting the volumes of stuff
> being rolled out from IO so we can't really give too many details right now
> because we simply don't know them (And Google is still updating their docs,
> fixing links, etc).
>
> So the question to the list is :
>  Do we delay 2.2.0 and include support for InstanceID and any other best
> practices Google has introduced or do we release 2.2.0, document / work
> around any gotchas and then prioritize GCM 3.0 support for 2.3.0?
>

(assuming this is related to the NPE I am seeing in [1])

I think the ultimate goal for 2.2.0 should be to to not crash like in [1].

I see three options:
1) document the work-around ([2]) and release the _existing_ 2.2.0, as is
-> The fact that the work-around needs to be added to (almost) all apps,
makes it an odd work-around (not saying it's a no-go)
2) delay the 2.2.0 and get full GCM 3.0 support in there
-> IMO it's unknown how long that takes, and ideally our 2.2.0 AGDroid-Push
should be out once we have the UPS released (early July); This also could
mean a delay on our Cordova lib.
3) Update 2.2.0 to ignore the ACK sent from GCM 3.0, and get a 2.2.x (or
2.3.0) a bit later for full support on GCM 3.0
-> IMO this allows us to release UPS 1.1.0 (and AGDroid-Push) in a
reasonable timeframe and moves the work-around into our library, and not
onto all the app developers.


My vote would be going w/ option #3, given the above reasoning and the fact
that we don't use any GCM 3.0 feature atm, it sounds fairly safe (at least
to me) doing the working inside of our library

-Matthias

[1] https://issues.jboss.org/browse/AGDROID-425
[2]
https://github.com/jboss-mobile/unified-push-helloworld/commit/077bfdce8980f86fde1662b490139573792c82fc



>
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150617/739e9a19/attachment.html 

From scm.blanc at gmail.com  Wed Jun 17 10:32:17 2015
From: scm.blanc at gmail.com (Sebastien Blanc)
Date: Wed, 17 Jun 2015 16:32:17 +0200
Subject: [aerogear-dev] GCM 3.0 and Instance ID
In-Reply-To: <CAAg5f2To7ujXR=+kd69fJi0Nkx6xd8QFT_LGQ92udY-guLVgdw@mail.gmail.com>
References: <CAEQz2Cs2WwZBruMxXN+Phyu4qwJ77gG7KOYDE9SUoLtAmP=S3w@mail.gmail.com>
	<CAAg5f2To7ujXR=+kd69fJi0Nkx6xd8QFT_LGQ92udY-guLVgdw@mail.gmail.com>
Message-ID: <CAD_dpu0=VCYj=1womQFJMPkgF6dP0Zq9jeF0tdjBZEdDXFX_xQ@mail.gmail.com>

if #3 is possible (check&ignore the ack backed into the library) I would go
for this option as well.

On Wed, Jun 17, 2015 at 4:28 PM, Matthias Wessendorf <matzew at apache.org>
wrote:

> Hi,
>
> On Wed, Jun 17, 2015 at 4:03 PM, Summers Pittman <supittma at redhat.com>
> wrote:
>
>> Sooooo we have a 2.2.0 staged.  Google has a ton of new functionality
>> rolling out for GCM.
>>
>> We think that 2.2.0 works with it mostly correctly but we are finding
>> some "gotchas".  Notably it looks like Google is sending some ACK messages
>> after we register that the library is ignoring.
>>
>> We will need to support InstanceID (tl;dr; Google is enhancing
>> registraiton_id).  Passos and I are still digesting the volumes of stuff
>> being rolled out from IO so we can't really give too many details right now
>> because we simply don't know them (And Google is still updating their docs,
>> fixing links, etc).
>>
>> So the question to the list is :
>>  Do we delay 2.2.0 and include support for InstanceID and any other best
>> practices Google has introduced or do we release 2.2.0, document / work
>> around any gotchas and then prioritize GCM 3.0 support for 2.3.0?
>>
>
> (assuming this is related to the NPE I am seeing in [1])
>
> I think the ultimate goal for 2.2.0 should be to to not crash like in [1].
>
> I see three options:
> 1) document the work-around ([2]) and release the _existing_ 2.2.0, as is
> -> The fact that the work-around needs to be added to (almost) all apps,
> makes it an odd work-around (not saying it's a no-go)
> 2) delay the 2.2.0 and get full GCM 3.0 support in there
> -> IMO it's unknown how long that takes, and ideally our 2.2.0
> AGDroid-Push should be out once we have the UPS released (early July); This
> also could mean a delay on our Cordova lib.
> 3) Update 2.2.0 to ignore the ACK sent from GCM 3.0, and get a 2.2.x (or
> 2.3.0) a bit later for full support on GCM 3.0
> -> IMO this allows us to release UPS 1.1.0 (and AGDroid-Push) in a
> reasonable timeframe and moves the work-around into our library, and not
> onto all the app developers.
>
>
> My vote would be going w/ option #3, given the above reasoning and the
> fact that we don't use any GCM 3.0 feature atm, it sounds fairly safe (at
> least to me) doing the working inside of our library
>
> -Matthias
>
> [1] https://issues.jboss.org/browse/AGDROID-425
> [2]
> https://github.com/jboss-mobile/unified-push-helloworld/commit/077bfdce8980f86fde1662b490139573792c82fc
>
>
>
>>
>>
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150617/f0a28328/attachment.html 

From supittma at redhat.com  Wed Jun 17 10:32:23 2015
From: supittma at redhat.com (Summers Pittman)
Date: Wed, 17 Jun 2015 10:32:23 -0400
Subject: [aerogear-dev] AeroGear Android Push 2.2.0
In-Reply-To: <CAD_dpu2u8iENYLASAOAD-EmmQp-nhT0qgCxt8sfvrxjr5y0v+w@mail.gmail.com>
References: <CADF=h2vVgw1UUGXHs+x=4zr12ZnC9Q=iAuw1z+OtVGQDtO=LFA@mail.gmail.com>
	<CAAg5f2QcCaXJjNUgjG3BmGuPDkRbzVx75EAYJ2rVErZiifMx=g@mail.gmail.com>
	<CADF=h2vO6zErixrULXSim_-PGTQaFcRsJ=y4n3BfJa5VreQZwg@mail.gmail.com>
	<CAD_dpu2u8iENYLASAOAD-EmmQp-nhT0qgCxt8sfvrxjr5y0v+w@mail.gmail.com>
Message-ID: <CAEQz2Ctkv3AMQbSgbKu8Ugy8WbGY9o44E6xa22TEX8Jyenaxmg@mail.gmail.com>

On Wed, Jun 17, 2015 at 3:17 AM, Sebastien Blanc <scm.blanc at gmail.com>
wrote:

> This fix is more a workaround since it was not needed with the previous
> versions.  so we need to be sure to check if :
>
No.  The hello world app is broken.

>
> - This fix was needed because of other commits on the helloworld
>
- This fix was needed because of the new version of the library
> - This fix was needed because of a change from GCM server
> - This fix was needed because of a mix/combination of all the previous
> potential causes
>

TL;DR: We never needed information from the PushRegistrar to handle
messages until metrics were added.  Now we do.  However, if the app is
garbage collected then the registration information is cleared from memory
(it is persisted on the device of course).  Because the notification
handler is invoked by android it bypasses the RegisterActivity.  When we
try to fetch the registration information to send the metric message it
isn't loaded and the NPE is thrown.  Previously had enabled the ability to
unregister the client from the message list screen we would have seen
similar results.

The application work by happy coincidence.  It wasn't until matz tested on
a hellishly obsolete device that the issue appeared. ;)



> Passos have you been able to test the lib with Aerodoc ?
>
> Sebi
>
>
>
>
> On Tue, Jun 16, 2015 at 4:50 PM, Daniel Passos <dpassos at redhat.com> wrote:
>
>> Seems the problem was in the app not in the library. For more details
>> please see my comment[1] in Jira and the fix in this PR[2]
>>
>> [1]
>> https://issues.jboss.org/browse/AGDROID-425?focusedCommentId=13079805&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13079805
>> [2] https://github.com/jboss-mobile/unified-push-helloworld/pull/14
>>
>> On Mon, Jun 15, 2015 at 9:42 AM, Matthias Wessendorf <matzew at apache.org>
>> wrote:
>>
>>> I noticed a little bug w/ the current libray
>>>
>>> https://issues.jboss.org/browse/AGDROID-425
>>>
>>>
>>>
>>> On Mon, Jun 15, 2015 at 2:42 AM, Daniel Passos <dpassos at redhat.com>
>>> wrote:
>>>
>>>> Hey Everyone,
>>>>
>>>> We are ready to release AeroGear Android Push 2.2.0, we staged[1] it on
>>>> Nexus.
>>>>
>>>> What is new in this version?
>>>>
>>>>    - AGDROID-422 <https://issues.jboss.org/browse/AGDROID-422> - Add
>>>>    support for push-config.json for Android Push SDK
>>>>    - AGDROID-423 <https://issues.jboss.org/browse/AGDROID-423> -
>>>>    Android SDK hook for notifying the server if app has been opened due to a
>>>>    push
>>>>
>>>>
>>>>
>>>> We?re planning to release it next Thursday.
>>>>
>>>> Fell free to test it and let us know if you find any issues.
>>>>
>>>> [1]
>>>> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-5783/
>>>> ?
>>>> --
>>>> -- Passos
>>>>
>>>> _______________________________________________
>>>> aerogear-dev mailing list
>>>> aerogear-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>
>>>
>>>
>>>
>>> --
>>> Matthias Wessendorf
>>>
>>> blog: http://matthiaswessendorf.wordpress.com/
>>> sessions: http://www.slideshare.net/mwessendorf
>>> twitter: http://twitter.com/mwessendorf
>>>
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>
>>
>>
>> --
>> -- Passos
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150617/1770ed7e/attachment-0001.html 

From supittma at redhat.com  Wed Jun 17 10:35:13 2015
From: supittma at redhat.com (Summers Pittman)
Date: Wed, 17 Jun 2015 10:35:13 -0400
Subject: [aerogear-dev] GCM 3.0 and Instance ID
In-Reply-To: <CAAg5f2To7ujXR=+kd69fJi0Nkx6xd8QFT_LGQ92udY-guLVgdw@mail.gmail.com>
References: <CAEQz2Cs2WwZBruMxXN+Phyu4qwJ77gG7KOYDE9SUoLtAmP=S3w@mail.gmail.com>
	<CAAg5f2To7ujXR=+kd69fJi0Nkx6xd8QFT_LGQ92udY-guLVgdw@mail.gmail.com>
Message-ID: <CAEQz2CtLCFkX-RTSTjhacjm9yMGNRQPso_cmyYaJgVfZ-fi7RQ@mail.gmail.com>

On Wed, Jun 17, 2015 at 10:28 AM, Matthias Wessendorf <matzew at apache.org>
wrote:

> Hi,
>
> On Wed, Jun 17, 2015 at 4:03 PM, Summers Pittman <supittma at redhat.com>
> wrote:
>
>> Sooooo we have a 2.2.0 staged.  Google has a ton of new functionality
>> rolling out for GCM.
>>
>> We think that 2.2.0 works with it mostly correctly but we are finding
>> some "gotchas".  Notably it looks like Google is sending some ACK messages
>> after we register that the library is ignoring.
>>
>> We will need to support InstanceID (tl;dr; Google is enhancing
>> registraiton_id).  Passos and I are still digesting the volumes of stuff
>> being rolled out from IO so we can't really give too many details right now
>> because we simply don't know them (And Google is still updating their docs,
>> fixing links, etc).
>>
>> So the question to the list is :
>>  Do we delay 2.2.0 and include support for InstanceID and any other best
>> practices Google has introduced or do we release 2.2.0, document / work
>> around any gotchas and then prioritize GCM 3.0 support for 2.3.0?
>>
>
> (assuming this is related to the NPE I am seeing in [1])
>

> I think the ultimate goal for 2.2.0 should be to to not crash like in [1].
>

It is unrelated.  1 is caused by the registration token getting GC'd by
Android and not being refreshed when the application launches.


> I see three options:
> 1) document the work-around ([2]) and release the _existing_ 2.2.0, as is
> -> The fact that the work-around needs to be added to (almost) all apps,
> makes it an odd work-around (not saying it's a no-go)
>
This isn't a "work around" this is a "The applications worked by
coincidence"

> 2) delay the 2.2.0 and get full GCM 3.0 support in there
> -> IMO it's unknown how long that takes, and ideally our 2.2.0
> AGDroid-Push should be out once we have the UPS released (early July); This
> also could mean a delay on our Cordova lib.
> 3) Update 2.2.0 to ignore the ACK sent from GCM 3.0, and get a 2.2.x (or
> 2.3.0) a bit later for full support on GCM 3.0
> -> IMO this allows us to release UPS 1.1.0 (and AGDroid-Push) in a
> reasonable timeframe and moves the work-around into our library, and not
> onto all the app developers.
>
>
> My vote would be going w/ option #3, given the above reasoning and the
> fact that we don't use any GCM 3.0 feature atm, it sounds fairly safe (at
> least to me) doing the working inside of our library
>
> -Matthias
>
> [1] https://issues.jboss.org/browse/AGDROID-425
> [2]
> https://github.com/jboss-mobile/unified-push-helloworld/commit/077bfdce8980f86fde1662b490139573792c82fc
>
>
>
>>
>>
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150617/15d26af8/attachment.html 

From supittma at redhat.com  Wed Jun 17 10:35:59 2015
From: supittma at redhat.com (Summers Pittman)
Date: Wed, 17 Jun 2015 10:35:59 -0400
Subject: [aerogear-dev] GCM 3.0 and Instance ID
In-Reply-To: <CAD_dpu0=VCYj=1womQFJMPkgF6dP0Zq9jeF0tdjBZEdDXFX_xQ@mail.gmail.com>
References: <CAEQz2Cs2WwZBruMxXN+Phyu4qwJ77gG7KOYDE9SUoLtAmP=S3w@mail.gmail.com>
	<CAAg5f2To7ujXR=+kd69fJi0Nkx6xd8QFT_LGQ92udY-guLVgdw@mail.gmail.com>
	<CAD_dpu0=VCYj=1womQFJMPkgF6dP0Zq9jeF0tdjBZEdDXFX_xQ@mail.gmail.com>
Message-ID: <CAEQz2CtJe3gTs5ZqtAxu76B-reBCXtU=502tXQWd+mwpAsMDhQ@mail.gmail.com>

On Wed, Jun 17, 2015 at 10:32 AM, Sebastien Blanc <scm.blanc at gmail.com>
wrote:

> if #3 is possible (check&ignore the ack backed into the library) I would
> go for this option as well.
>
The ACK is mostly ignored now.  There is a log message saying that the GCM
handler couldn't process it but otherwise the application is unaffected.

>
> On Wed, Jun 17, 2015 at 4:28 PM, Matthias Wessendorf <matzew at apache.org>
> wrote:
>
>> Hi,
>>
>> On Wed, Jun 17, 2015 at 4:03 PM, Summers Pittman <supittma at redhat.com>
>> wrote:
>>
>>> Sooooo we have a 2.2.0 staged.  Google has a ton of new functionality
>>> rolling out for GCM.
>>>
>>> We think that 2.2.0 works with it mostly correctly but we are finding
>>> some "gotchas".  Notably it looks like Google is sending some ACK messages
>>> after we register that the library is ignoring.
>>>
>>> We will need to support InstanceID (tl;dr; Google is enhancing
>>> registraiton_id).  Passos and I are still digesting the volumes of stuff
>>> being rolled out from IO so we can't really give too many details right now
>>> because we simply don't know them (And Google is still updating their docs,
>>> fixing links, etc).
>>>
>>> So the question to the list is :
>>>  Do we delay 2.2.0 and include support for InstanceID and any other best
>>> practices Google has introduced or do we release 2.2.0, document / work
>>> around any gotchas and then prioritize GCM 3.0 support for 2.3.0?
>>>
>>
>> (assuming this is related to the NPE I am seeing in [1])
>>
>> I think the ultimate goal for 2.2.0 should be to to not crash like in
>> [1].
>>
>> I see three options:
>> 1) document the work-around ([2]) and release the _existing_ 2.2.0, as is
>> -> The fact that the work-around needs to be added to (almost) all apps,
>> makes it an odd work-around (not saying it's a no-go)
>> 2) delay the 2.2.0 and get full GCM 3.0 support in there
>> -> IMO it's unknown how long that takes, and ideally our 2.2.0
>> AGDroid-Push should be out once we have the UPS released (early July); This
>> also could mean a delay on our Cordova lib.
>> 3) Update 2.2.0 to ignore the ACK sent from GCM 3.0, and get a 2.2.x (or
>> 2.3.0) a bit later for full support on GCM 3.0
>> -> IMO this allows us to release UPS 1.1.0 (and AGDroid-Push) in a
>> reasonable timeframe and moves the work-around into our library, and not
>> onto all the app developers.
>>
>>
>> My vote would be going w/ option #3, given the above reasoning and the
>> fact that we don't use any GCM 3.0 feature atm, it sounds fairly safe (at
>> least to me) doing the working inside of our library
>>
>> -Matthias
>>
>> [1] https://issues.jboss.org/browse/AGDROID-425
>> [2]
>> https://github.com/jboss-mobile/unified-push-helloworld/commit/077bfdce8980f86fde1662b490139573792c82fc
>>
>>
>>
>>>
>>>
>>>
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>
>>
>>
>> --
>> Matthias Wessendorf
>>
>> blog: http://matthiaswessendorf.wordpress.com/
>> sessions: http://www.slideshare.net/mwessendorf
>> twitter: http://twitter.com/mwessendorf
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150617/ef62ca24/attachment.html 

From dpassos at redhat.com  Wed Jun 17 10:40:19 2015
From: dpassos at redhat.com (Daniel Passos)
Date: Wed, 17 Jun 2015 11:40:19 -0300
Subject: [aerogear-dev] GCM 3.0 and Instance ID
In-Reply-To: <CAAg5f2To7ujXR=+kd69fJi0Nkx6xd8QFT_LGQ92udY-guLVgdw@mail.gmail.com>
References: <CAEQz2Cs2WwZBruMxXN+Phyu4qwJ77gG7KOYDE9SUoLtAmP=S3w@mail.gmail.com>
	<CAAg5f2To7ujXR=+kd69fJi0Nkx6xd8QFT_LGQ92udY-guLVgdw@mail.gmail.com>
Message-ID: <CADF=h2sGU6xmQPLfmYYo-viMcv60gxoPiFZ0FtEyF1EAw1KosA@mail.gmail.com>

The option #3 is exactly what I was thinking about. Postpone a week the
2.2.0 release and add the workaround in the library.

On Wed, Jun 17, 2015 at 11:28 AM, Matthias Wessendorf <matzew at apache.org>
wrote:

> Hi,
>
> On Wed, Jun 17, 2015 at 4:03 PM, Summers Pittman <supittma at redhat.com>
> wrote:
>
>> Sooooo we have a 2.2.0 staged.  Google has a ton of new functionality
>> rolling out for GCM.
>>
>> We think that 2.2.0 works with it mostly correctly but we are finding
>> some "gotchas".  Notably it looks like Google is sending some ACK messages
>> after we register that the library is ignoring.
>>
>> We will need to support InstanceID (tl;dr; Google is enhancing
>> registraiton_id).  Passos and I are still digesting the volumes of stuff
>> being rolled out from IO so we can't really give too many details right now
>> because we simply don't know them (And Google is still updating their docs,
>> fixing links, etc).
>>
>> So the question to the list is :
>>  Do we delay 2.2.0 and include support for InstanceID and any other best
>> practices Google has introduced or do we release 2.2.0, document / work
>> around any gotchas and then prioritize GCM 3.0 support for 2.3.0?
>>
>
> (assuming this is related to the NPE I am seeing in [1])
>
> I think the ultimate goal for 2.2.0 should be to to not crash like in [1].
>
> I see three options:
> 1) document the work-around ([2]) and release the _existing_ 2.2.0, as is
> -> The fact that the work-around needs to be added to (almost) all apps,
> makes it an odd work-around (not saying it's a no-go)
> 2) delay the 2.2.0 and get full GCM 3.0 support in there
> -> IMO it's unknown how long that takes, and ideally our 2.2.0
> AGDroid-Push should be out once we have the UPS released (early July); This
> also could mean a delay on our Cordova lib.
> 3) Update 2.2.0 to ignore the ACK sent from GCM 3.0, and get a 2.2.x (or
> 2.3.0) a bit later for full support on GCM 3.0
> -> IMO this allows us to release UPS 1.1.0 (and AGDroid-Push) in a
> reasonable timeframe and moves the work-around into our library, and not
> onto all the app developers.
>
>
> My vote would be going w/ option #3, given the above reasoning and the
> fact that we don't use any GCM 3.0 feature atm, it sounds fairly safe (at
> least to me) doing the working inside of our library
>
> -Matthias
>
> [1] https://issues.jboss.org/browse/AGDROID-425
> [2]
> https://github.com/jboss-mobile/unified-push-helloworld/commit/077bfdce8980f86fde1662b490139573792c82fc
>
>
>
>>
>>
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 
-- Passos
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150617/1175229d/attachment-0001.html 

From matzew at apache.org  Wed Jun 17 10:42:03 2015
From: matzew at apache.org (Matthias Wessendorf)
Date: Wed, 17 Jun 2015 16:42:03 +0200
Subject: [aerogear-dev] GCM 3.0 and Instance ID
In-Reply-To: <CAEQz2CtJe3gTs5ZqtAxu76B-reBCXtU=502tXQWd+mwpAsMDhQ@mail.gmail.com>
References: <CAEQz2Cs2WwZBruMxXN+Phyu4qwJ77gG7KOYDE9SUoLtAmP=S3w@mail.gmail.com>
	<CAAg5f2To7ujXR=+kd69fJi0Nkx6xd8QFT_LGQ92udY-guLVgdw@mail.gmail.com>
	<CAD_dpu0=VCYj=1womQFJMPkgF6dP0Zq9jeF0tdjBZEdDXFX_xQ@mail.gmail.com>
	<CAEQz2CtJe3gTs5ZqtAxu76B-reBCXtU=502tXQWd+mwpAsMDhQ@mail.gmail.com>
Message-ID: <CAAg5f2SVR+vSvJzNLW5CPPT=7pj-1VXK-0XMMmNZ9J7p476gbA@mail.gmail.com>

On Wed, Jun 17, 2015 at 4:35 PM, Summers Pittman <supittma at redhat.com>
wrote:

>
>
> On Wed, Jun 17, 2015 at 10:32 AM, Sebastien Blanc <scm.blanc at gmail.com>
> wrote:
>
>> if #3 is possible (check&ignore the ack backed into the library) I would
>> go for this option as well.
>>
> The ACK is mostly ignored now.  There is a log message saying that the GCM
> handler couldn't process it but otherwise the application is unaffected.
>

perfect, so #3 it is? :)

So a bit of delay on 2.2.0, a little release note of no support of GCM 3
and afterwards do that in 2.2.1 (or 2.3.0) ?





>
>> On Wed, Jun 17, 2015 at 4:28 PM, Matthias Wessendorf <matzew at apache.org>
>> wrote:
>>
>>> Hi,
>>>
>>> On Wed, Jun 17, 2015 at 4:03 PM, Summers Pittman <supittma at redhat.com>
>>> wrote:
>>>
>>>> Sooooo we have a 2.2.0 staged.  Google has a ton of new functionality
>>>> rolling out for GCM.
>>>>
>>>> We think that 2.2.0 works with it mostly correctly but we are finding
>>>> some "gotchas".  Notably it looks like Google is sending some ACK messages
>>>> after we register that the library is ignoring.
>>>>
>>>> We will need to support InstanceID (tl;dr; Google is enhancing
>>>> registraiton_id).  Passos and I are still digesting the volumes of stuff
>>>> being rolled out from IO so we can't really give too many details right now
>>>> because we simply don't know them (And Google is still updating their docs,
>>>> fixing links, etc).
>>>>
>>>> So the question to the list is :
>>>>  Do we delay 2.2.0 and include support for InstanceID and any other
>>>> best practices Google has introduced or do we release 2.2.0, document /
>>>> work around any gotchas and then prioritize GCM 3.0 support for 2.3.0?
>>>>
>>>
>>> (assuming this is related to the NPE I am seeing in [1])
>>>
>>> I think the ultimate goal for 2.2.0 should be to to not crash like in
>>> [1].
>>>
>>> I see three options:
>>> 1) document the work-around ([2]) and release the _existing_ 2.2.0, as is
>>> -> The fact that the work-around needs to be added to (almost) all apps,
>>> makes it an odd work-around (not saying it's a no-go)
>>> 2) delay the 2.2.0 and get full GCM 3.0 support in there
>>> -> IMO it's unknown how long that takes, and ideally our 2.2.0
>>> AGDroid-Push should be out once we have the UPS released (early July); This
>>> also could mean a delay on our Cordova lib.
>>> 3) Update 2.2.0 to ignore the ACK sent from GCM 3.0, and get a 2.2.x (or
>>> 2.3.0) a bit later for full support on GCM 3.0
>>> -> IMO this allows us to release UPS 1.1.0 (and AGDroid-Push) in a
>>> reasonable timeframe and moves the work-around into our library, and not
>>> onto all the app developers.
>>>
>>>
>>> My vote would be going w/ option #3, given the above reasoning and the
>>> fact that we don't use any GCM 3.0 feature atm, it sounds fairly safe (at
>>> least to me) doing the working inside of our library
>>>
>>> -Matthias
>>>
>>> [1] https://issues.jboss.org/browse/AGDROID-425
>>> [2]
>>> https://github.com/jboss-mobile/unified-push-helloworld/commit/077bfdce8980f86fde1662b490139573792c82fc
>>>
>>>
>>>
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> aerogear-dev mailing list
>>>> aerogear-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>
>>>
>>>
>>>
>>> --
>>> Matthias Wessendorf
>>>
>>> blog: http://matthiaswessendorf.wordpress.com/
>>> sessions: http://www.slideshare.net/mwessendorf
>>> twitter: http://twitter.com/mwessendorf
>>>
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150617/d6083ae7/attachment.html 

From dpassos at redhat.com  Wed Jun 17 10:45:46 2015
From: dpassos at redhat.com (Daniel Passos)
Date: Wed, 17 Jun 2015 11:45:46 -0300
Subject: [aerogear-dev] GCM 3.0 and Instance ID
In-Reply-To: <CAAg5f2SVR+vSvJzNLW5CPPT=7pj-1VXK-0XMMmNZ9J7p476gbA@mail.gmail.com>
References: <CAEQz2Cs2WwZBruMxXN+Phyu4qwJ77gG7KOYDE9SUoLtAmP=S3w@mail.gmail.com>
	<CAAg5f2To7ujXR=+kd69fJi0Nkx6xd8QFT_LGQ92udY-guLVgdw@mail.gmail.com>
	<CAD_dpu0=VCYj=1womQFJMPkgF6dP0Zq9jeF0tdjBZEdDXFX_xQ@mail.gmail.com>
	<CAEQz2CtJe3gTs5ZqtAxu76B-reBCXtU=502tXQWd+mwpAsMDhQ@mail.gmail.com>
	<CAAg5f2SVR+vSvJzNLW5CPPT=7pj-1VXK-0XMMmNZ9J7p476gbA@mail.gmail.com>
Message-ID: <CADF=h2viiOdT4gxjz31pvbioeDCi=8hxMsAes7obZ9zjaBLJZQ@mail.gmail.com>

+1 Anyway UPS add a key (in the future release) to identify the message
come from UPS is also a good idea

On Wed, Jun 17, 2015 at 11:42 AM, Matthias Wessendorf <matzew at apache.org>
wrote:

>
>
> On Wed, Jun 17, 2015 at 4:35 PM, Summers Pittman <supittma at redhat.com>
> wrote:
>
>>
>>
>> On Wed, Jun 17, 2015 at 10:32 AM, Sebastien Blanc <scm.blanc at gmail.com>
>> wrote:
>>
>>> if #3 is possible (check&ignore the ack backed into the library) I would
>>> go for this option as well.
>>>
>> The ACK is mostly ignored now.  There is a log message saying that the
>> GCM handler couldn't process it but otherwise the application is
>> unaffected.
>>
>
> perfect, so #3 it is? :)
>
> So a bit of delay on 2.2.0, a little release note of no support of GCM 3
> and afterwards do that in 2.2.1 (or 2.3.0) ?
>
>
>
>
>
>>
>>> On Wed, Jun 17, 2015 at 4:28 PM, Matthias Wessendorf <matzew at apache.org>
>>> wrote:
>>>
>>>> Hi,
>>>>
>>>> On Wed, Jun 17, 2015 at 4:03 PM, Summers Pittman <supittma at redhat.com>
>>>> wrote:
>>>>
>>>>> Sooooo we have a 2.2.0 staged.  Google has a ton of new functionality
>>>>> rolling out for GCM.
>>>>>
>>>>> We think that 2.2.0 works with it mostly correctly but we are finding
>>>>> some "gotchas".  Notably it looks like Google is sending some ACK messages
>>>>> after we register that the library is ignoring.
>>>>>
>>>>> We will need to support InstanceID (tl;dr; Google is enhancing
>>>>> registraiton_id).  Passos and I are still digesting the volumes of stuff
>>>>> being rolled out from IO so we can't really give too many details right now
>>>>> because we simply don't know them (And Google is still updating their docs,
>>>>> fixing links, etc).
>>>>>
>>>>> So the question to the list is :
>>>>>  Do we delay 2.2.0 and include support for InstanceID and any other
>>>>> best practices Google has introduced or do we release 2.2.0, document /
>>>>> work around any gotchas and then prioritize GCM 3.0 support for 2.3.0?
>>>>>
>>>>
>>>> (assuming this is related to the NPE I am seeing in [1])
>>>>
>>>> I think the ultimate goal for 2.2.0 should be to to not crash like in
>>>> [1].
>>>>
>>>> I see three options:
>>>> 1) document the work-around ([2]) and release the _existing_ 2.2.0, as
>>>> is
>>>> -> The fact that the work-around needs to be added to (almost) all
>>>> apps, makes it an odd work-around (not saying it's a no-go)
>>>> 2) delay the 2.2.0 and get full GCM 3.0 support in there
>>>> -> IMO it's unknown how long that takes, and ideally our 2.2.0
>>>> AGDroid-Push should be out once we have the UPS released (early July); This
>>>> also could mean a delay on our Cordova lib.
>>>> 3) Update 2.2.0 to ignore the ACK sent from GCM 3.0, and get a 2.2.x
>>>> (or 2.3.0) a bit later for full support on GCM 3.0
>>>> -> IMO this allows us to release UPS 1.1.0 (and AGDroid-Push) in a
>>>> reasonable timeframe and moves the work-around into our library, and not
>>>> onto all the app developers.
>>>>
>>>>
>>>> My vote would be going w/ option #3, given the above reasoning and the
>>>> fact that we don't use any GCM 3.0 feature atm, it sounds fairly safe (at
>>>> least to me) doing the working inside of our library
>>>>
>>>> -Matthias
>>>>
>>>> [1] https://issues.jboss.org/browse/AGDROID-425
>>>> [2]
>>>> https://github.com/jboss-mobile/unified-push-helloworld/commit/077bfdce8980f86fde1662b490139573792c82fc
>>>>
>>>>
>>>>
>>>>>
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> aerogear-dev mailing list
>>>>> aerogear-dev at lists.jboss.org
>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Matthias Wessendorf
>>>>
>>>> blog: http://matthiaswessendorf.wordpress.com/
>>>> sessions: http://www.slideshare.net/mwessendorf
>>>> twitter: http://twitter.com/mwessendorf
>>>>
>>>> _______________________________________________
>>>> aerogear-dev mailing list
>>>> aerogear-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>
>>>
>>>
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 
-- Passos
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150617/834489f2/attachment-0001.html 

From matzew at apache.org  Wed Jun 17 11:04:03 2015
From: matzew at apache.org (Matthias Wessendorf)
Date: Wed, 17 Jun 2015 17:04:03 +0200
Subject: [aerogear-dev] GCM 3.0 and Instance ID
In-Reply-To: <CADF=h2viiOdT4gxjz31pvbioeDCi=8hxMsAes7obZ9zjaBLJZQ@mail.gmail.com>
References: <CAEQz2Cs2WwZBruMxXN+Phyu4qwJ77gG7KOYDE9SUoLtAmP=S3w@mail.gmail.com>
	<CAAg5f2To7ujXR=+kd69fJi0Nkx6xd8QFT_LGQ92udY-guLVgdw@mail.gmail.com>
	<CAD_dpu0=VCYj=1womQFJMPkgF6dP0Zq9jeF0tdjBZEdDXFX_xQ@mail.gmail.com>
	<CAEQz2CtJe3gTs5ZqtAxu76B-reBCXtU=502tXQWd+mwpAsMDhQ@mail.gmail.com>
	<CAAg5f2SVR+vSvJzNLW5CPPT=7pj-1VXK-0XMMmNZ9J7p476gbA@mail.gmail.com>
	<CADF=h2viiOdT4gxjz31pvbioeDCi=8hxMsAes7obZ9zjaBLJZQ@mail.gmail.com>
Message-ID: <CAAg5f2R0u8-wSSz00Jib_k=exnMg5020o3cq_XkO87S3OE-=0g@mail.gmail.com>

we can do that now, and infact the push-message-id (we introduced for
analyics) is already that kinda identifier

-M

On Wed, Jun 17, 2015 at 4:45 PM, Daniel Passos <dpassos at redhat.com> wrote:

> +1 Anyway UPS add a key (in the future release) to identify the message
> come from UPS is also a good idea
>
> On Wed, Jun 17, 2015 at 11:42 AM, Matthias Wessendorf <matzew at apache.org>
> wrote:
>
>>
>>
>> On Wed, Jun 17, 2015 at 4:35 PM, Summers Pittman <supittma at redhat.com>
>> wrote:
>>
>>>
>>>
>>> On Wed, Jun 17, 2015 at 10:32 AM, Sebastien Blanc <scm.blanc at gmail.com>
>>> wrote:
>>>
>>>> if #3 is possible (check&ignore the ack backed into the library) I
>>>> would go for this option as well.
>>>>
>>> The ACK is mostly ignored now.  There is a log message saying that the
>>> GCM handler couldn't process it but otherwise the application is
>>> unaffected.
>>>
>>
>> perfect, so #3 it is? :)
>>
>> So a bit of delay on 2.2.0, a little release note of no support of GCM 3
>> and afterwards do that in 2.2.1 (or 2.3.0) ?
>>
>>
>>
>>
>>
>>>
>>>> On Wed, Jun 17, 2015 at 4:28 PM, Matthias Wessendorf <matzew at apache.org
>>>> > wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> On Wed, Jun 17, 2015 at 4:03 PM, Summers Pittman <supittma at redhat.com>
>>>>> wrote:
>>>>>
>>>>>> Sooooo we have a 2.2.0 staged.  Google has a ton of new functionality
>>>>>> rolling out for GCM.
>>>>>>
>>>>>> We think that 2.2.0 works with it mostly correctly but we are finding
>>>>>> some "gotchas".  Notably it looks like Google is sending some ACK messages
>>>>>> after we register that the library is ignoring.
>>>>>>
>>>>>> We will need to support InstanceID (tl;dr; Google is enhancing
>>>>>> registraiton_id).  Passos and I are still digesting the volumes of stuff
>>>>>> being rolled out from IO so we can't really give too many details right now
>>>>>> because we simply don't know them (And Google is still updating their docs,
>>>>>> fixing links, etc).
>>>>>>
>>>>>> So the question to the list is :
>>>>>>  Do we delay 2.2.0 and include support for InstanceID and any other
>>>>>> best practices Google has introduced or do we release 2.2.0, document /
>>>>>> work around any gotchas and then prioritize GCM 3.0 support for 2.3.0?
>>>>>>
>>>>>
>>>>> (assuming this is related to the NPE I am seeing in [1])
>>>>>
>>>>> I think the ultimate goal for 2.2.0 should be to to not crash like in
>>>>> [1].
>>>>>
>>>>> I see three options:
>>>>> 1) document the work-around ([2]) and release the _existing_ 2.2.0, as
>>>>> is
>>>>> -> The fact that the work-around needs to be added to (almost) all
>>>>> apps, makes it an odd work-around (not saying it's a no-go)
>>>>> 2) delay the 2.2.0 and get full GCM 3.0 support in there
>>>>> -> IMO it's unknown how long that takes, and ideally our 2.2.0
>>>>> AGDroid-Push should be out once we have the UPS released (early July); This
>>>>> also could mean a delay on our Cordova lib.
>>>>> 3) Update 2.2.0 to ignore the ACK sent from GCM 3.0, and get a 2.2.x
>>>>> (or 2.3.0) a bit later for full support on GCM 3.0
>>>>> -> IMO this allows us to release UPS 1.1.0 (and AGDroid-Push) in a
>>>>> reasonable timeframe and moves the work-around into our library, and not
>>>>> onto all the app developers.
>>>>>
>>>>>
>>>>> My vote would be going w/ option #3, given the above reasoning and the
>>>>> fact that we don't use any GCM 3.0 feature atm, it sounds fairly safe (at
>>>>> least to me) doing the working inside of our library
>>>>>
>>>>> -Matthias
>>>>>
>>>>> [1] https://issues.jboss.org/browse/AGDROID-425
>>>>> [2]
>>>>> https://github.com/jboss-mobile/unified-push-helloworld/commit/077bfdce8980f86fde1662b490139573792c82fc
>>>>>
>>>>>
>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> aerogear-dev mailing list
>>>>>> aerogear-dev at lists.jboss.org
>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Matthias Wessendorf
>>>>>
>>>>> blog: http://matthiaswessendorf.wordpress.com/
>>>>> sessions: http://www.slideshare.net/mwessendorf
>>>>> twitter: http://twitter.com/mwessendorf
>>>>>
>>>>> _______________________________________________
>>>>> aerogear-dev mailing list
>>>>> aerogear-dev at lists.jboss.org
>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> aerogear-dev mailing list
>>>> aerogear-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>
>>>
>>>
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>
>>
>>
>> --
>> Matthias Wessendorf
>>
>> blog: http://matthiaswessendorf.wordpress.com/
>> sessions: http://www.slideshare.net/mwessendorf
>> twitter: http://twitter.com/mwessendorf
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
>
> --
> -- Passos
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150617/de57d148/attachment.html 

From dpassos at redhat.com  Wed Jun 17 21:36:50 2015
From: dpassos at redhat.com (Daniel Passos)
Date: Wed, 17 Jun 2015 22:36:50 -0300
Subject: [aerogear-dev] AeroGear Android Push 2.2.0
In-Reply-To: <CAEQz2Ctkv3AMQbSgbKu8Ugy8WbGY9o44E6xa22TEX8Jyenaxmg@mail.gmail.com>
References: <CADF=h2vVgw1UUGXHs+x=4zr12ZnC9Q=iAuw1z+OtVGQDtO=LFA@mail.gmail.com>
	<CAAg5f2QcCaXJjNUgjG3BmGuPDkRbzVx75EAYJ2rVErZiifMx=g@mail.gmail.com>
	<CADF=h2vO6zErixrULXSim_-PGTQaFcRsJ=y4n3BfJa5VreQZwg@mail.gmail.com>
	<CAD_dpu2u8iENYLASAOAD-EmmQp-nhT0qgCxt8sfvrxjr5y0v+w@mail.gmail.com>
	<CAEQz2Ctkv3AMQbSgbKu8Ugy8WbGY9o44E6xa22TEX8Jyenaxmg@mail.gmail.com>
Message-ID: <CADF=h2u0kc8d9O93VqHSWazqWtGOQ=Acb=AaOrByYW+d7rNY0g@mail.gmail.com>

Hey Guys,

We are postpone it to fix the bug Matthias found. I just send a PR[1] to
fix it.

[1] https://github.com/aerogear/aerogear-android-push/pull/38

On Wed, Jun 17, 2015 at 11:32 AM, Summers Pittman <supittma at redhat.com>
wrote:

>
>
>
> On Wed, Jun 17, 2015 at 3:17 AM, Sebastien Blanc <scm.blanc at gmail.com>
> wrote:
>
>> This fix is more a workaround since it was not needed with the previous
>> versions.  so we need to be sure to check if :
>>
> No.  The hello world app is broken.
>
>>
>> - This fix was needed because of other commits on the helloworld
>>
> - This fix was needed because of the new version of the library
>> - This fix was needed because of a change from GCM server
>> - This fix was needed because of a mix/combination of all the previous
>> potential causes
>>
>
> TL;DR: We never needed information from the PushRegistrar to handle
> messages until metrics were added.  Now we do.  However, if the app is
> garbage collected then the registration information is cleared from memory
> (it is persisted on the device of course).  Because the notification
> handler is invoked by android it bypasses the RegisterActivity.  When we
> try to fetch the registration information to send the metric message it
> isn't loaded and the NPE is thrown.  Previously had enabled the ability to
> unregister the client from the message list screen we would have seen
> similar results.
>
> The application work by happy coincidence.  It wasn't until matz tested on
> a hellishly obsolete device that the issue appeared. ;)
>
>
>
>> Passos have you been able to test the lib with Aerodoc ?
>>
>> Sebi
>>
>>
>>
>>
>> On Tue, Jun 16, 2015 at 4:50 PM, Daniel Passos <dpassos at redhat.com>
>> wrote:
>>
>>> Seems the problem was in the app not in the library. For more details
>>> please see my comment[1] in Jira and the fix in this PR[2]
>>>
>>> [1]
>>> https://issues.jboss.org/browse/AGDROID-425?focusedCommentId=13079805&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13079805
>>> [2] https://github.com/jboss-mobile/unified-push-helloworld/pull/14
>>>
>>> On Mon, Jun 15, 2015 at 9:42 AM, Matthias Wessendorf <matzew at apache.org>
>>> wrote:
>>>
>>>> I noticed a little bug w/ the current libray
>>>>
>>>> https://issues.jboss.org/browse/AGDROID-425
>>>>
>>>>
>>>>
>>>> On Mon, Jun 15, 2015 at 2:42 AM, Daniel Passos <dpassos at redhat.com>
>>>> wrote:
>>>>
>>>>> Hey Everyone,
>>>>>
>>>>> We are ready to release AeroGear Android Push 2.2.0, we staged[1] it
>>>>> on Nexus.
>>>>>
>>>>> What is new in this version?
>>>>>
>>>>>    - AGDROID-422 <https://issues.jboss.org/browse/AGDROID-422> - Add
>>>>>    support for push-config.json for Android Push SDK
>>>>>    - AGDROID-423 <https://issues.jboss.org/browse/AGDROID-423> -
>>>>>    Android SDK hook for notifying the server if app has been opened due to a
>>>>>    push
>>>>>
>>>>>
>>>>>
>>>>> We?re planning to release it next Thursday.
>>>>>
>>>>> Fell free to test it and let us know if you find any issues.
>>>>>
>>>>> [1]
>>>>> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-5783/
>>>>> ?
>>>>> --
>>>>> -- Passos
>>>>>
>>>>> _______________________________________________
>>>>> aerogear-dev mailing list
>>>>> aerogear-dev at lists.jboss.org
>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Matthias Wessendorf
>>>>
>>>> blog: http://matthiaswessendorf.wordpress.com/
>>>> sessions: http://www.slideshare.net/mwessendorf
>>>> twitter: http://twitter.com/mwessendorf
>>>>
>>>> _______________________________________________
>>>> aerogear-dev mailing list
>>>> aerogear-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>
>>>
>>>
>>>
>>> --
>>> -- Passos
>>>
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 
-- Passos
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150617/546d096d/attachment-0001.html 

From matzew at apache.org  Thu Jun 18 07:02:20 2015
From: matzew at apache.org (Matthias Wessendorf)
Date: Thu, 18 Jun 2015 13:02:20 +0200
Subject: [aerogear-dev] UPS - GCM 3.0 support
Message-ID: <CAAg5f2So=3QEXq-7nxSJfYpC+rtNRPR5eXj11v0RYneStPeyjA@mail.gmail.com>

Hi team,

here is an epic to support GCM3 for 1.2.0:
https://issues.jboss.org/browse/AGPUSH-1453

Especially the "topic messaging" sub-task is kick ass! This means we need
to map our categories to GCM topics, and that allows us to ping all
devices, with a single request, to GCM.

That is an extremely awesome boost! The epic contains a 35 min. video of
the new GCM 3.0 changes.

Very cool, it also takes about the iOS/GCM mapping (at least worth to
explore / evaluate)

-Matthias


-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150618/5985b0af/attachment.html 

From scm.blanc at gmail.com  Thu Jun 18 14:22:25 2015
From: scm.blanc at gmail.com (Sebastien Blanc)
Date: Thu, 18 Jun 2015 20:22:25 +0200
Subject: [aerogear-dev] Openshift UPS cartridge updates
In-Reply-To: <CADF=h2tP9uNG1G-xJSbgG+ju4QLwZ1mw-QiG=ewmoTaeb3q-2Q@mail.gmail.com>
References: <CAAg5f2REGDeMsDg25NHDyPias+w_j9=SYdw-upp1kreacWm2xA@mail.gmail.com>
	<CADF=h2tP9uNG1G-xJSbgG+ju4QLwZ1mw-QiG=ewmoTaeb3q-2Q@mail.gmail.com>
Message-ID: <CAD_dpu18pGN6-UYpcP0vC_pjikso3sjVqRH0XehtvoULbOLAQg@mail.gmail.com>

+1
The vert.x version could also be cool

On Mon, Jun 15, 2015 at 2:23 PM, Daniel Passos <dpassos at redhat.com> wrote:

> +1
>
> On Mon, Jun 15, 2015 at 6:28 AM, Matthias Wessendorf <matzew at apache.org>
> wrote:
>
>> Hi,
>>
>> currently we have the UPS server _and_ the SimplePush server on on
>> cartridge.
>>
>> Since the UPS now is a full profile dependent server (JMS/HornetQ) is on,
>> I'd like to change remove the SimplePush Server from the cartridge.
>>
>> For SimplePush, IMO it's best to have a standalone cartridge, that just
>> is Java based and fire up the Netty based server - no WildFly really
>> needed, just MySQL and the SimplePush server
>>
>> Any thoughts?
>>
>> --
>> Matthias Wessendorf
>>
>> blog: http://matthiaswessendorf.wordpress.com/
>> sessions: http://www.slideshare.net/mwessendorf
>> twitter: http://twitter.com/mwessendorf
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
>
> --
> -- Passos
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150618/bad0c1c5/attachment.html 

From matzew at apache.org  Thu Jun 18 14:35:46 2015
From: matzew at apache.org (Matthias Wessendorf)
Date: Thu, 18 Jun 2015 20:35:46 +0200
Subject: [aerogear-dev] Openshift UPS cartridge updates
In-Reply-To: <CAD_dpu18pGN6-UYpcP0vC_pjikso3sjVqRH0XehtvoULbOLAQg@mail.gmail.com>
References: <CAAg5f2REGDeMsDg25NHDyPias+w_j9=SYdw-upp1kreacWm2xA@mail.gmail.com>
	<CADF=h2tP9uNG1G-xJSbgG+ju4QLwZ1mw-QiG=ewmoTaeb3q-2Q@mail.gmail.com>
	<CAD_dpu18pGN6-UYpcP0vC_pjikso3sjVqRH0XehtvoULbOLAQg@mail.gmail.com>
Message-ID: <CAAg5f2RgLmD9KCgP=c72BOuW=84zQgrGX2H_hqvAsVXi5L6z=Q@mail.gmail.com>

Not sure if there is actually a benefit for the user if the implementation
of the server is done w/ pure netty, or w/ netty+vert.x on-top



On Thu, Jun 18, 2015 at 8:22 PM, Sebastien Blanc <scm.blanc at gmail.com>
wrote:

> +1
> The vert.x version could also be cool
>
> On Mon, Jun 15, 2015 at 2:23 PM, Daniel Passos <dpassos at redhat.com> wrote:
>
>> +1
>>
>> On Mon, Jun 15, 2015 at 6:28 AM, Matthias Wessendorf <matzew at apache.org>
>> wrote:
>>
>>> Hi,
>>>
>>> currently we have the UPS server _and_ the SimplePush server on on
>>> cartridge.
>>>
>>> Since the UPS now is a full profile dependent server (JMS/HornetQ) is
>>> on, I'd like to change remove the SimplePush Server from the cartridge.
>>>
>>> For SimplePush, IMO it's best to have a standalone cartridge, that just
>>> is Java based and fire up the Netty based server - no WildFly really
>>> needed, just MySQL and the SimplePush server
>>>
>>> Any thoughts?
>>>
>>> --
>>> Matthias Wessendorf
>>>
>>> blog: http://matthiaswessendorf.wordpress.com/
>>> sessions: http://www.slideshare.net/mwessendorf
>>> twitter: http://twitter.com/mwessendorf
>>>
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>
>>
>>
>> --
>> -- Passos
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150618/6ab03f88/attachment.html 

From scm.blanc at gmail.com  Thu Jun 18 14:41:03 2015
From: scm.blanc at gmail.com (Sebastien Blanc)
Date: Thu, 18 Jun 2015 20:41:03 +0200
Subject: [aerogear-dev] Openshift UPS cartridge updates
In-Reply-To: <CAAg5f2RgLmD9KCgP=c72BOuW=84zQgrGX2H_hqvAsVXi5L6z=Q@mail.gmail.com>
References: <CAAg5f2REGDeMsDg25NHDyPias+w_j9=SYdw-upp1kreacWm2xA@mail.gmail.com>
	<CADF=h2tP9uNG1G-xJSbgG+ju4QLwZ1mw-QiG=ewmoTaeb3q-2Q@mail.gmail.com>
	<CAD_dpu18pGN6-UYpcP0vC_pjikso3sjVqRH0XehtvoULbOLAQg@mail.gmail.com>
	<CAAg5f2RgLmD9KCgP=c72BOuW=84zQgrGX2H_hqvAsVXi5L6z=Q@mail.gmail.com>
Message-ID: <CAD_dpu3zSAZYN5ac_ns3DgsN5QKjCpBX+tX+TumJmY4uBNazmA@mail.gmail.com>

Oh right, that's true :)

On Thu, Jun 18, 2015 at 8:35 PM, Matthias Wessendorf <matzew at apache.org>
wrote:

> Not sure if there is actually a benefit for the user if the implementation
> of the server is done w/ pure netty, or w/ netty+vert.x on-top
>
>
>
> On Thu, Jun 18, 2015 at 8:22 PM, Sebastien Blanc <scm.blanc at gmail.com>
> wrote:
>
>> +1
>> The vert.x version could also be cool
>>
>> On Mon, Jun 15, 2015 at 2:23 PM, Daniel Passos <dpassos at redhat.com>
>> wrote:
>>
>>> +1
>>>
>>> On Mon, Jun 15, 2015 at 6:28 AM, Matthias Wessendorf <matzew at apache.org>
>>> wrote:
>>>
>>>> Hi,
>>>>
>>>> currently we have the UPS server _and_ the SimplePush server on on
>>>> cartridge.
>>>>
>>>> Since the UPS now is a full profile dependent server (JMS/HornetQ) is
>>>> on, I'd like to change remove the SimplePush Server from the cartridge.
>>>>
>>>> For SimplePush, IMO it's best to have a standalone cartridge, that just
>>>> is Java based and fire up the Netty based server - no WildFly really
>>>> needed, just MySQL and the SimplePush server
>>>>
>>>> Any thoughts?
>>>>
>>>> --
>>>> Matthias Wessendorf
>>>>
>>>> blog: http://matthiaswessendorf.wordpress.com/
>>>> sessions: http://www.slideshare.net/mwessendorf
>>>> twitter: http://twitter.com/mwessendorf
>>>>
>>>> _______________________________________________
>>>> aerogear-dev mailing list
>>>> aerogear-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>
>>>
>>>
>>>
>>> --
>>> -- Passos
>>>
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150618/f2a7a788/attachment.html 

From dpassos at redhat.com  Thu Jun 18 18:53:05 2015
From: dpassos at redhat.com (Daniel Passos)
Date: Thu, 18 Jun 2015 19:53:05 -0300
Subject: [aerogear-dev] AeroGear Android Push 2.2.0
In-Reply-To: <CADF=h2u0kc8d9O93VqHSWazqWtGOQ=Acb=AaOrByYW+d7rNY0g@mail.gmail.com>
References: <CADF=h2vVgw1UUGXHs+x=4zr12ZnC9Q=iAuw1z+OtVGQDtO=LFA@mail.gmail.com>
	<CAAg5f2QcCaXJjNUgjG3BmGuPDkRbzVx75EAYJ2rVErZiifMx=g@mail.gmail.com>
	<CADF=h2vO6zErixrULXSim_-PGTQaFcRsJ=y4n3BfJa5VreQZwg@mail.gmail.com>
	<CAD_dpu2u8iENYLASAOAD-EmmQp-nhT0qgCxt8sfvrxjr5y0v+w@mail.gmail.com>
	<CAEQz2Ctkv3AMQbSgbKu8Ugy8WbGY9o44E6xa22TEX8Jyenaxmg@mail.gmail.com>
	<CADF=h2u0kc8d9O93VqHSWazqWtGOQ=Acb=AaOrByYW+d7rNY0g@mail.gmail.com>
Message-ID: <CADF=h2tm7Ccrdhrje3NhW7XshXiREq=uRdKE3wqbCQNiNP1wFA@mail.gmail.com>

Hi,

I've staged[1] the Push library 2.2.0 again and send a PR for UnifiedPush
helloworld[2] using it.

We?re planning to release it next Wednesday

Fell free to test it and let us know if you find any issues.
[1]
https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-5856/
[2] https://github.com/jboss-mobile/unified-push-helloworld/pull/15


On Wed, Jun 17, 2015 at 10:36 PM, Daniel Passos <dpassos at redhat.com> wrote:

> Hey Guys,
>
> We are postpone it to fix the bug Matthias found. I just send a PR[1] to
> fix it.
>
> [1] https://github.com/aerogear/aerogear-android-push/pull/38
>
> On Wed, Jun 17, 2015 at 11:32 AM, Summers Pittman <supittma at redhat.com>
> wrote:
>
>>
>>
>>
>> On Wed, Jun 17, 2015 at 3:17 AM, Sebastien Blanc <scm.blanc at gmail.com>
>> wrote:
>>
>>> This fix is more a workaround since it was not needed with the previous
>>> versions.  so we need to be sure to check if :
>>>
>> No.  The hello world app is broken.
>>
>>>
>>> - This fix was needed because of other commits on the helloworld
>>>
>> - This fix was needed because of the new version of the library
>>> - This fix was needed because of a change from GCM server
>>> - This fix was needed because of a mix/combination of all the previous
>>> potential causes
>>>
>>
>> TL;DR: We never needed information from the PushRegistrar to handle
>> messages until metrics were added.  Now we do.  However, if the app is
>> garbage collected then the registration information is cleared from memory
>> (it is persisted on the device of course).  Because the notification
>> handler is invoked by android it bypasses the RegisterActivity.  When we
>> try to fetch the registration information to send the metric message it
>> isn't loaded and the NPE is thrown.  Previously had enabled the ability to
>> unregister the client from the message list screen we would have seen
>> similar results.
>>
>> The application work by happy coincidence.  It wasn't until matz tested
>> on a hellishly obsolete device that the issue appeared. ;)
>>
>>
>>
>>> Passos have you been able to test the lib with Aerodoc ?
>>>
>>> Sebi
>>>
>>>
>>>
>>>
>>> On Tue, Jun 16, 2015 at 4:50 PM, Daniel Passos <dpassos at redhat.com>
>>> wrote:
>>>
>>>> Seems the problem was in the app not in the library. For more details
>>>> please see my comment[1] in Jira and the fix in this PR[2]
>>>>
>>>> [1]
>>>> https://issues.jboss.org/browse/AGDROID-425?focusedCommentId=13079805&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13079805
>>>> [2] https://github.com/jboss-mobile/unified-push-helloworld/pull/14
>>>>
>>>> On Mon, Jun 15, 2015 at 9:42 AM, Matthias Wessendorf <matzew at apache.org
>>>> > wrote:
>>>>
>>>>> I noticed a little bug w/ the current libray
>>>>>
>>>>> https://issues.jboss.org/browse/AGDROID-425
>>>>>
>>>>>
>>>>>
>>>>> On Mon, Jun 15, 2015 at 2:42 AM, Daniel Passos <dpassos at redhat.com>
>>>>> wrote:
>>>>>
>>>>>> Hey Everyone,
>>>>>>
>>>>>> We are ready to release AeroGear Android Push 2.2.0, we staged[1] it
>>>>>> on Nexus.
>>>>>>
>>>>>> What is new in this version?
>>>>>>
>>>>>>    - AGDROID-422 <https://issues.jboss.org/browse/AGDROID-422> - Add
>>>>>>    support for push-config.json for Android Push SDK
>>>>>>    - AGDROID-423 <https://issues.jboss.org/browse/AGDROID-423> -
>>>>>>    Android SDK hook for notifying the server if app has been opened due to a
>>>>>>    push
>>>>>>
>>>>>>
>>>>>>
>>>>>> We?re planning to release it next Thursday.
>>>>>>
>>>>>> Fell free to test it and let us know if you find any issues.
>>>>>>
>>>>>> [1]
>>>>>> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-5783/
>>>>>> ?
>>>>>> --
>>>>>> -- Passos
>>>>>>
>>>>>> _______________________________________________
>>>>>> aerogear-dev mailing list
>>>>>> aerogear-dev at lists.jboss.org
>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Matthias Wessendorf
>>>>>
>>>>> blog: http://matthiaswessendorf.wordpress.com/
>>>>> sessions: http://www.slideshare.net/mwessendorf
>>>>> twitter: http://twitter.com/mwessendorf
>>>>>
>>>>> _______________________________________________
>>>>> aerogear-dev mailing list
>>>>> aerogear-dev at lists.jboss.org
>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> -- Passos
>>>>
>>>> _______________________________________________
>>>> aerogear-dev mailing list
>>>> aerogear-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>
>>>
>>>
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
>
> --
> -- Passos
>



-- 
-- Passos
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150618/a81e785e/attachment-0001.html 

From dpassos at redhat.com  Fri Jun 19 09:24:56 2015
From: dpassos at redhat.com (Daniel Passos)
Date: Fri, 19 Jun 2015 10:24:56 -0300
Subject: [aerogear-dev] Fwd: AeroGear Pipe
In-Reply-To: <CADF=h2ssAipvTUBANVboc+PQQk500vo0TJeLE8b2DpV0d73YFA@mail.gmail.com>
References: <CAC6O=UVzC=EZXva7iYVgqWhQYebbFNWiFLL-kU0KLvc4Rg934Q@mail.gmail.com>
	<CADF=h2ssAipvTUBANVboc+PQQk500vo0TJeLE8b2DpV0d73YFA@mail.gmail.com>
Message-ID: <CADF=h2u_LCokK0gX-qxw7ALdcYt34boOEazP9Y3KgQ=Y1Dy_gg@mail.gmail.com>

Hi Autur,

For now, the only way to use HTTP put is saving[1] an object with id,
because that is the common use for PUT, update a *specific* resource.

https://github.com/aerogear/aerogear-android-pipe/blob/master/aerogear-android-pipe/src/main/java/org/jboss/aerogear/android/pipe/rest/RestRunner.java#L306-L317

-- 
-- Passos

On Fri, Jun 19, 2015 at 6:36 AM, Artur Dryomov <artur.dryomov at gmail.com>
wrote:

> Hi,
>
> I need to perform a HTTP PUT request using the Hawkular API. Documentation
> <http://www.hawkular.org/docs/rest/rest-alerts.html#_alert_handling> and
> example <http://pastie.org/private/fw02g8us6g20esc7dczng>. I. e. I need
> to send PUT request with some URL query. What is the best way to achieve
> that using AeroGear? Should I use HTTP client instead of AeroGear? I
> haven?t found any related APIs in the documentation.
>
> Artur.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150619/f8dd08f4/attachment.html 

From supittma at redhat.com  Fri Jun 19 10:05:19 2015
From: supittma at redhat.com (Summers Pittman)
Date: Fri, 19 Jun 2015 10:05:19 -0400
Subject: [aerogear-dev] Fwd: AeroGear Pipe
In-Reply-To: <CADF=h2u_LCokK0gX-qxw7ALdcYt34boOEazP9Y3KgQ=Y1Dy_gg@mail.gmail.com>
References: <CAC6O=UVzC=EZXva7iYVgqWhQYebbFNWiFLL-kU0KLvc4Rg934Q@mail.gmail.com>
	<CADF=h2ssAipvTUBANVboc+PQQk500vo0TJeLE8b2DpV0d73YFA@mail.gmail.com>
	<CADF=h2u_LCokK0gX-qxw7ALdcYt34boOEazP9Y3KgQ=Y1Dy_gg@mail.gmail.com>
Message-ID: <CAEQz2CsNmyDTR6QHo0fVYFA8D-51Haa1iqKHW_oYCtDCG9W8jg@mail.gmail.com>

You can also implement a PIpeHandler (like RestRunner) and supply your own
save implementation.

 *
https://github.com/aerogear/aerogear-android-pipe/blob/master/aerogear-android-pipe/src/main/java/org/jboss/aerogear/android/pipe/rest/RestRunner.java

You will set when you set up your pipe with the Configuration Object.

PipeManager.config("developers", RestfulPipeConfiguration.class)
           .pipeHandler(new MySpecifalHandler())
           .withUrl(new URL("http://www.server.com/developer"))
           .forClass(Developer.class);

On Fri, Jun 19, 2015 at 9:24 AM, Daniel Passos <dpassos at redhat.com> wrote:

> Hi Autur,
>
> For now, the only way to use HTTP put is saving[1] an object with id,
> because that is the common use for PUT, update a *specific* resource.
>
>
> https://github.com/aerogear/aerogear-android-pipe/blob/master/aerogear-android-pipe/src/main/java/org/jboss/aerogear/android/pipe/rest/RestRunner.java#L306-L317
>
> --
> -- Passos
>
> On Fri, Jun 19, 2015 at 6:36 AM, Artur Dryomov <artur.dryomov at gmail.com>
> wrote:
>
>> Hi,
>>
>> I need to perform a HTTP PUT request using the Hawkular API.
>> Documentation
>> <http://www.hawkular.org/docs/rest/rest-alerts.html#_alert_handling> and
>> example <http://pastie.org/private/fw02g8us6g20esc7dczng>. I. e. I need
>> to send PUT request with some URL query. What is the best way to achieve
>> that using AeroGear? Should I use HTTP client instead of AeroGear? I
>> haven?t found any related APIs in the documentation.
>>
>> Artur.
>>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150619/3f8c960c/attachment.html 

From matzew at apache.org  Fri Jun 19 13:51:09 2015
From: matzew at apache.org (Matthias Wessendorf)
Date: Fri, 19 Jun 2015 19:51:09 +0200
Subject: [aerogear-dev] Parent 0.2.16 -> staging repo
Message-ID: <CAAg5f2QJKg8fxuQi7Ldy3rMYxQyJ8FSzkRtTwziZveRrt1_xJA@mail.gmail.com>

Ahoy!

A new release of aerogear-parent was staged at:
https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-5882/

This is basically an increase of the KC used version

I'm considering to release it on Monday. If you want
the release to be postoned to another day, let me know.

-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150619/504448d4/attachment.html 

From matzew at apache.org  Mon Jun 22 04:56:19 2015
From: matzew at apache.org (Matthias Wessendorf)
Date: Mon, 22 Jun 2015 10:56:19 +0200
Subject: [aerogear-dev] Parent 0.2.16 -> staging repo
In-Reply-To: <CAAg5f2QJKg8fxuQi7Ldy3rMYxQyJ8FSzkRtTwziZveRrt1_xJA@mail.gmail.com>
References: <CAAg5f2QJKg8fxuQi7Ldy3rMYxQyJ8FSzkRtTwziZveRrt1_xJA@mail.gmail.com>
Message-ID: <CAAg5f2SdCoKdVXwRSb+T8muwQyJkmZYVPzdK=ramfdqAOQZstQ@mail.gmail.com>

released and on maven central

On Fri, Jun 19, 2015 at 7:51 PM, Matthias Wessendorf <matzew at apache.org>
wrote:

> Ahoy!
>
> A new release of aerogear-parent was staged at:
>
> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-5882/
>
> This is basically an increase of the KC used version
>
> I'm considering to release it on Monday. If you want
> the release to be postoned to another day, let me know.
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>



-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150622/10505f5d/attachment.html 

From matzew at apache.org  Tue Jun 23 01:07:08 2015
From: matzew at apache.org (Matthias Wessendorf)
Date: Tue, 23 Jun 2015 07:07:08 +0200
Subject: [aerogear-dev] What's new in AeroGear?
Message-ID: <CAAg5f2Qdvg_ZXZFYXBa9ZnouWQU6nyz0LdB2q7BD-wC-F1vSnA@mail.gmail.com>

Hi all,

here is a community update

*Android
We fixed the bug Matthias found last week and staged the AeroGear Android
Push 2.2.0 again:
http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-AeroGear-Android-Push-2-2-0-tp11781p11813.html

* iOS lovers,
Last week we released aerogear-ios-push in its Swift and Objc version, see
by yourself:
    https://github.com/aerogear/aerogear-ios-push/tree/1.1.0-beta.2
    https://github.com/aerogear/aerogear-ios-push/tree/1.1.0-beta.2-swift
This new version include an enhance config file management, you can now
have your serverURL, varianID, vareiantSecret read from config file.
This week we'll work on  moving aerogear-ios-http and aerogear-ios-oauth2
to Swift 2.0. Watch out for a swift2.0 branch, coming soon.

* Push
The UnifiedPush Server is working towards 1.1.0.Final - Internally we will
be also using the latest release of Keycloak (1.3.1):
https://github.com/aerogear/aerogear-unifiedpush-server/pull/601
On the WebPush side, our GSoC student Idel is continuing to make
improvements to our server and console. Worth to visit the repo:
https://github.com/aerogear/aerogear-webpush-server

For the UPS cartridge, we are looking to improve memory and based on a
suggestion by the awesome Farah, we are removing JGroups subsystem
https://github.com/aerogear/openshift-origin-cartridge-aerogear-push/pull/18

A few releases have been produced over the last week
* SimplePush client release (0.2.0)
* java-mpns release (0.2.0)
* aerogear-parent release (0.2.16)

Have fun!

-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150623/46d06e75/attachment-0001.html 

From edewit at redhat.com  Tue Jun 23 10:39:34 2015
From: edewit at redhat.com (Erik Jan de Wit)
Date: Tue, 23 Jun 2015 16:39:34 +0200
Subject: [aerogear-dev] Release cordova push plugin
Message-ID: <CAO2B-fbn-75NuuP8DH2vACoDSXkWK18AEsrE-unAkEPdOL8XSw@mail.gmail.com>

Because we have a critical issue[1] with the current push plugin we
are going to release the new plugin that adds support for sending
metrics and uses the new android 2.0 libs you can test it by using the
master branch.

[1] https://issues.jboss.org/browse/AGCORDOVA-107
-- 
Cheers,
       Erik Jan

From matzew at apache.org  Tue Jun 23 10:44:04 2015
From: matzew at apache.org (Matthias Wessendorf)
Date: Tue, 23 Jun 2015 16:44:04 +0200
Subject: [aerogear-dev] [Aerogear-users] Release cordova push plugin
In-Reply-To: <CAO2B-fbn-75NuuP8DH2vACoDSXkWK18AEsrE-unAkEPdOL8XSw@mail.gmail.com>
References: <CAO2B-fbn-75NuuP8DH2vACoDSXkWK18AEsrE-unAkEPdOL8XSw@mail.gmail.com>
Message-ID: <CAAg5f2S2-LcbFJ8RK6dR1wSysNiZnGA8qOxJSArc1xJa=g8zYg@mail.gmail.com>

On Tue, Jun 23, 2015 at 4:39 PM, Erik Jan de Wit <edewit at redhat.com> wrote:

> Because we have a critical issue[1] with the current push plugin we
> are going to release the new plugin that adds support for sending
> metrics and uses the new android 2.0 libs


you mean 2.2.0 ?
http://lists.jboss.org/pipermail/aerogear-dev/2015-June/011714.html

If yes, I will do a quick sanity test on this version later tonight, so
that passos can move forward w/ its release



> you can test it by using the
> master branch.
>
> [1] https://issues.jboss.org/browse/AGCORDOVA-107
> --
> Cheers,
>        Erik Jan
> _______________________________________________
> Aerogear-users mailing list
> Aerogear-users at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-users
>



-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150623/2b23692c/attachment.html 

From matzew at apache.org  Tue Jun 23 11:52:02 2015
From: matzew at apache.org (Matthias Wessendorf)
Date: Tue, 23 Jun 2015 17:52:02 +0200
Subject: [aerogear-dev] AeroGear Android Push 2.2.0
In-Reply-To: <CADF=h2tm7Ccrdhrje3NhW7XshXiREq=uRdKE3wqbCQNiNP1wFA@mail.gmail.com>
References: <CADF=h2vVgw1UUGXHs+x=4zr12ZnC9Q=iAuw1z+OtVGQDtO=LFA@mail.gmail.com>
	<CAAg5f2QcCaXJjNUgjG3BmGuPDkRbzVx75EAYJ2rVErZiifMx=g@mail.gmail.com>
	<CADF=h2vO6zErixrULXSim_-PGTQaFcRsJ=y4n3BfJa5VreQZwg@mail.gmail.com>
	<CAD_dpu2u8iENYLASAOAD-EmmQp-nhT0qgCxt8sfvrxjr5y0v+w@mail.gmail.com>
	<CAEQz2Ctkv3AMQbSgbKu8Ugy8WbGY9o44E6xa22TEX8Jyenaxmg@mail.gmail.com>
	<CADF=h2u0kc8d9O93VqHSWazqWtGOQ=Acb=AaOrByYW+d7rNY0g@mail.gmail.com>
	<CADF=h2tm7Ccrdhrje3NhW7XshXiREq=uRdKE3wqbCQNiNP1wFA@mail.gmail.com>
Message-ID: <CAAg5f2S8O-OQXJHW1LEUZEiF7_CUPXtNvK31=SCnXav2oNSyXA@mail.gmail.com>

this pom.xml, on the 2.2.0 tag has incorrect version nr:
https://github.com/aerogear/aerogear-android-push/blob/2.2.0/aerogear-android-push-test/pom.xml#L29


On Fri, Jun 19, 2015 at 12:53 AM, Daniel Passos <dpassos at redhat.com> wrote:

> Hi,
>
> I've staged[1] the Push library 2.2.0 again and send a PR for UnifiedPush
> helloworld[2] using it.
>
> We?re planning to release it next Wednesday
>
> Fell free to test it and let us know if you find any issues.
> [1]
> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-5856/
> [2] https://github.com/jboss-mobile/unified-push-helloworld/pull/15
>
>
> On Wed, Jun 17, 2015 at 10:36 PM, Daniel Passos <dpassos at redhat.com>
> wrote:
>
>> Hey Guys,
>>
>> We are postpone it to fix the bug Matthias found. I just send a PR[1] to
>> fix it.
>>
>> [1] https://github.com/aerogear/aerogear-android-push/pull/38
>>
>> On Wed, Jun 17, 2015 at 11:32 AM, Summers Pittman <supittma at redhat.com>
>> wrote:
>>
>>>
>>>
>>>
>>> On Wed, Jun 17, 2015 at 3:17 AM, Sebastien Blanc <scm.blanc at gmail.com>
>>> wrote:
>>>
>>>> This fix is more a workaround since it was not needed with the previous
>>>> versions.  so we need to be sure to check if :
>>>>
>>> No.  The hello world app is broken.
>>>
>>>>
>>>> - This fix was needed because of other commits on the helloworld
>>>>
>>> - This fix was needed because of the new version of the library
>>>> - This fix was needed because of a change from GCM server
>>>> - This fix was needed because of a mix/combination of all the previous
>>>> potential causes
>>>>
>>>
>>> TL;DR: We never needed information from the PushRegistrar to handle
>>> messages until metrics were added.  Now we do.  However, if the app is
>>> garbage collected then the registration information is cleared from memory
>>> (it is persisted on the device of course).  Because the notification
>>> handler is invoked by android it bypasses the RegisterActivity.  When we
>>> try to fetch the registration information to send the metric message it
>>> isn't loaded and the NPE is thrown.  Previously had enabled the ability to
>>> unregister the client from the message list screen we would have seen
>>> similar results.
>>>
>>> The application work by happy coincidence.  It wasn't until matz tested
>>> on a hellishly obsolete device that the issue appeared. ;)
>>>
>>>
>>>
>>>> Passos have you been able to test the lib with Aerodoc ?
>>>>
>>>> Sebi
>>>>
>>>>
>>>>
>>>>
>>>> On Tue, Jun 16, 2015 at 4:50 PM, Daniel Passos <dpassos at redhat.com>
>>>> wrote:
>>>>
>>>>> Seems the problem was in the app not in the library. For more details
>>>>> please see my comment[1] in Jira and the fix in this PR[2]
>>>>>
>>>>> [1]
>>>>> https://issues.jboss.org/browse/AGDROID-425?focusedCommentId=13079805&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13079805
>>>>> [2] https://github.com/jboss-mobile/unified-push-helloworld/pull/14
>>>>>
>>>>> On Mon, Jun 15, 2015 at 9:42 AM, Matthias Wessendorf <
>>>>> matzew at apache.org> wrote:
>>>>>
>>>>>> I noticed a little bug w/ the current libray
>>>>>>
>>>>>> https://issues.jboss.org/browse/AGDROID-425
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Mon, Jun 15, 2015 at 2:42 AM, Daniel Passos <dpassos at redhat.com>
>>>>>> wrote:
>>>>>>
>>>>>>> Hey Everyone,
>>>>>>>
>>>>>>> We are ready to release AeroGear Android Push 2.2.0, we staged[1] it
>>>>>>> on Nexus.
>>>>>>>
>>>>>>> What is new in this version?
>>>>>>>
>>>>>>>    - AGDROID-422 <https://issues.jboss.org/browse/AGDROID-422> -
>>>>>>>    Add support for push-config.json for Android Push SDK
>>>>>>>    - AGDROID-423 <https://issues.jboss.org/browse/AGDROID-423> -
>>>>>>>    Android SDK hook for notifying the server if app has been opened due to a
>>>>>>>    push
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> We?re planning to release it next Thursday.
>>>>>>>
>>>>>>> Fell free to test it and let us know if you find any issues.
>>>>>>>
>>>>>>> [1]
>>>>>>> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-5783/
>>>>>>> ?
>>>>>>> --
>>>>>>> -- Passos
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> aerogear-dev mailing list
>>>>>>> aerogear-dev at lists.jboss.org
>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Matthias Wessendorf
>>>>>>
>>>>>> blog: http://matthiaswessendorf.wordpress.com/
>>>>>> sessions: http://www.slideshare.net/mwessendorf
>>>>>> twitter: http://twitter.com/mwessendorf
>>>>>>
>>>>>> _______________________________________________
>>>>>> aerogear-dev mailing list
>>>>>> aerogear-dev at lists.jboss.org
>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> -- Passos
>>>>>
>>>>> _______________________________________________
>>>>> aerogear-dev mailing list
>>>>> aerogear-dev at lists.jboss.org
>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> aerogear-dev mailing list
>>>> aerogear-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>
>>>
>>>
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>
>>
>>
>> --
>> -- Passos
>>
>
>
>
> --
> -- Passos
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150623/128060d7/attachment-0001.html 

From edewit at redhat.com  Tue Jun 23 12:01:51 2015
From: edewit at redhat.com (Erik Jan de Wit)
Date: Tue, 23 Jun 2015 18:01:51 +0200
Subject: [aerogear-dev] [Aerogear-users] Release cordova push plugin
In-Reply-To: <CAAg5f2S2-LcbFJ8RK6dR1wSysNiZnGA8qOxJSArc1xJa=g8zYg@mail.gmail.com>
References: <CAO2B-fbn-75NuuP8DH2vACoDSXkWK18AEsrE-unAkEPdOL8XSw@mail.gmail.com>
	<CAAg5f2S2-LcbFJ8RK6dR1wSysNiZnGA8qOxJSArc1xJa=g8zYg@mail.gmail.com>
Message-ID: <CAO2B-faQD+dMB=8garTkDk2L-KbisFV84CmJf6CvTY3pnHydFw@mail.gmail.com>

yes I meant 2.2.0 and we can already test with the snapshot version

On Tue, Jun 23, 2015 at 4:44 PM, Matthias Wessendorf <matzew at apache.org> wrote:
>
>
> On Tue, Jun 23, 2015 at 4:39 PM, Erik Jan de Wit <edewit at redhat.com> wrote:
>>
>> Because we have a critical issue[1] with the current push plugin we
>> are going to release the new plugin that adds support for sending
>> metrics and uses the new android 2.0 libs
>
>
> you mean 2.2.0 ?
> http://lists.jboss.org/pipermail/aerogear-dev/2015-June/011714.html
>
> If yes, I will do a quick sanity test on this version later tonight, so that
> passos can move forward w/ its release
>
>
>>
>> you can test it by using the
>> master branch.
>>
>> [1] https://issues.jboss.org/browse/AGCORDOVA-107
>> --
>> Cheers,
>>        Erik Jan
>> _______________________________________________
>> Aerogear-users mailing list
>> Aerogear-users at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-users
>
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>
> _______________________________________________
> Aerogear-users mailing list
> Aerogear-users at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-users
>



-- 
Cheers,
       Erik Jan

From dpassos at redhat.com  Tue Jun 23 12:49:11 2015
From: dpassos at redhat.com (Daniel Passos)
Date: Tue, 23 Jun 2015 13:49:11 -0300
Subject: [aerogear-dev] AeroGear Android Push 2.2.0
In-Reply-To: <CAAg5f2S8O-OQXJHW1LEUZEiF7_CUPXtNvK31=SCnXav2oNSyXA@mail.gmail.com>
References: <CADF=h2vVgw1UUGXHs+x=4zr12ZnC9Q=iAuw1z+OtVGQDtO=LFA@mail.gmail.com>
	<CAAg5f2QcCaXJjNUgjG3BmGuPDkRbzVx75EAYJ2rVErZiifMx=g@mail.gmail.com>
	<CADF=h2vO6zErixrULXSim_-PGTQaFcRsJ=y4n3BfJa5VreQZwg@mail.gmail.com>
	<CAD_dpu2u8iENYLASAOAD-EmmQp-nhT0qgCxt8sfvrxjr5y0v+w@mail.gmail.com>
	<CAEQz2Ctkv3AMQbSgbKu8Ugy8WbGY9o44E6xa22TEX8Jyenaxmg@mail.gmail.com>
	<CADF=h2u0kc8d9O93VqHSWazqWtGOQ=Acb=AaOrByYW+d7rNY0g@mail.gmail.com>
	<CADF=h2tm7Ccrdhrje3NhW7XshXiREq=uRdKE3wqbCQNiNP1wFA@mail.gmail.com>
	<CAAg5f2S8O-OQXJHW1LEUZEiF7_CUPXtNvK31=SCnXav2oNSyXA@mail.gmail.com>
Message-ID: <CADF=h2tAqSZvdobU_6Kg1U2N7cc6h=-MMxKww3tjCxmQo+YnsA@mail.gmail.com>

Because test is not part of the release.

On Tue, Jun 23, 2015 at 12:52 PM, Matthias Wessendorf <matzew at apache.org>
wrote:

> this pom.xml, on the 2.2.0 tag has incorrect version nr:
> https://github.com/aerogear/aerogear-android-push/blob/2.2.0/aerogear-android-push-test/pom.xml#L29
>
>
> On Fri, Jun 19, 2015 at 12:53 AM, Daniel Passos <dpassos at redhat.com>
> wrote:
>
>> Hi,
>>
>> I've staged[1] the Push library 2.2.0 again and send a PR for UnifiedPush
>> helloworld[2] using it.
>>
>> We?re planning to release it next Wednesday
>>
>> Fell free to test it and let us know if you find any issues.
>> [1]
>> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-5856/
>> [2] https://github.com/jboss-mobile/unified-push-helloworld/pull/15
>>
>>
>> On Wed, Jun 17, 2015 at 10:36 PM, Daniel Passos <dpassos at redhat.com>
>> wrote:
>>
>>> Hey Guys,
>>>
>>> We are postpone it to fix the bug Matthias found. I just send a PR[1] to
>>> fix it.
>>>
>>> [1] https://github.com/aerogear/aerogear-android-push/pull/38
>>>
>>> On Wed, Jun 17, 2015 at 11:32 AM, Summers Pittman <supittma at redhat.com>
>>> wrote:
>>>
>>>>
>>>>
>>>>
>>>> On Wed, Jun 17, 2015 at 3:17 AM, Sebastien Blanc <scm.blanc at gmail.com>
>>>> wrote:
>>>>
>>>>> This fix is more a workaround since it was not needed with the
>>>>> previous versions.  so we need to be sure to check if :
>>>>>
>>>> No.  The hello world app is broken.
>>>>
>>>>>
>>>>> - This fix was needed because of other commits on the helloworld
>>>>>
>>>> - This fix was needed because of the new version of the library
>>>>> - This fix was needed because of a change from GCM server
>>>>> - This fix was needed because of a mix/combination of all the previous
>>>>> potential causes
>>>>>
>>>>
>>>> TL;DR: We never needed information from the PushRegistrar to handle
>>>> messages until metrics were added.  Now we do.  However, if the app is
>>>> garbage collected then the registration information is cleared from memory
>>>> (it is persisted on the device of course).  Because the notification
>>>> handler is invoked by android it bypasses the RegisterActivity.  When we
>>>> try to fetch the registration information to send the metric message it
>>>> isn't loaded and the NPE is thrown.  Previously had enabled the ability to
>>>> unregister the client from the message list screen we would have seen
>>>> similar results.
>>>>
>>>> The application work by happy coincidence.  It wasn't until matz tested
>>>> on a hellishly obsolete device that the issue appeared. ;)
>>>>
>>>>
>>>>
>>>>> Passos have you been able to test the lib with Aerodoc ?
>>>>>
>>>>> Sebi
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> On Tue, Jun 16, 2015 at 4:50 PM, Daniel Passos <dpassos at redhat.com>
>>>>> wrote:
>>>>>
>>>>>> Seems the problem was in the app not in the library. For more details
>>>>>> please see my comment[1] in Jira and the fix in this PR[2]
>>>>>>
>>>>>> [1]
>>>>>> https://issues.jboss.org/browse/AGDROID-425?focusedCommentId=13079805&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13079805
>>>>>> [2] https://github.com/jboss-mobile/unified-push-helloworld/pull/14
>>>>>>
>>>>>> On Mon, Jun 15, 2015 at 9:42 AM, Matthias Wessendorf <
>>>>>> matzew at apache.org> wrote:
>>>>>>
>>>>>>> I noticed a little bug w/ the current libray
>>>>>>>
>>>>>>> https://issues.jboss.org/browse/AGDROID-425
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Mon, Jun 15, 2015 at 2:42 AM, Daniel Passos <dpassos at redhat.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Hey Everyone,
>>>>>>>>
>>>>>>>> We are ready to release AeroGear Android Push 2.2.0, we staged[1]
>>>>>>>> it on Nexus.
>>>>>>>>
>>>>>>>> What is new in this version?
>>>>>>>>
>>>>>>>>    - AGDROID-422 <https://issues.jboss.org/browse/AGDROID-422> -
>>>>>>>>    Add support for push-config.json for Android Push SDK
>>>>>>>>    - AGDROID-423 <https://issues.jboss.org/browse/AGDROID-423> -
>>>>>>>>    Android SDK hook for notifying the server if app has been opened due to a
>>>>>>>>    push
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> We?re planning to release it next Thursday.
>>>>>>>>
>>>>>>>> Fell free to test it and let us know if you find any issues.
>>>>>>>>
>>>>>>>> [1]
>>>>>>>> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-5783/
>>>>>>>> ?
>>>>>>>> --
>>>>>>>> -- Passos
>>>>>>>>
>>>>>>>> _______________________________________________
>>>>>>>> aerogear-dev mailing list
>>>>>>>> aerogear-dev at lists.jboss.org
>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Matthias Wessendorf
>>>>>>>
>>>>>>> blog: http://matthiaswessendorf.wordpress.com/
>>>>>>> sessions: http://www.slideshare.net/mwessendorf
>>>>>>> twitter: http://twitter.com/mwessendorf
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> aerogear-dev mailing list
>>>>>>> aerogear-dev at lists.jboss.org
>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> -- Passos
>>>>>>
>>>>>> _______________________________________________
>>>>>> aerogear-dev mailing list
>>>>>> aerogear-dev at lists.jboss.org
>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>>>
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> aerogear-dev mailing list
>>>>> aerogear-dev at lists.jboss.org
>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> aerogear-dev mailing list
>>>> aerogear-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>
>>>
>>>
>>>
>>> --
>>> -- Passos
>>>
>>
>>
>>
>> --
>> -- Passos
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 
-- Passos
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150623/119f8724/attachment.html 

From matzew at apache.org  Tue Jun 23 12:53:07 2015
From: matzew at apache.org (Matthias Wessendorf)
Date: Tue, 23 Jun 2015 18:53:07 +0200
Subject: [aerogear-dev] AeroGear Android Push 2.2.0
In-Reply-To: <CADF=h2tAqSZvdobU_6Kg1U2N7cc6h=-MMxKww3tjCxmQo+YnsA@mail.gmail.com>
References: <CADF=h2vVgw1UUGXHs+x=4zr12ZnC9Q=iAuw1z+OtVGQDtO=LFA@mail.gmail.com>
	<CAAg5f2QcCaXJjNUgjG3BmGuPDkRbzVx75EAYJ2rVErZiifMx=g@mail.gmail.com>
	<CADF=h2vO6zErixrULXSim_-PGTQaFcRsJ=y4n3BfJa5VreQZwg@mail.gmail.com>
	<CAD_dpu2u8iENYLASAOAD-EmmQp-nhT0qgCxt8sfvrxjr5y0v+w@mail.gmail.com>
	<CAEQz2Ctkv3AMQbSgbKu8Ugy8WbGY9o44E6xa22TEX8Jyenaxmg@mail.gmail.com>
	<CADF=h2u0kc8d9O93VqHSWazqWtGOQ=Acb=AaOrByYW+d7rNY0g@mail.gmail.com>
	<CADF=h2tm7Ccrdhrje3NhW7XshXiREq=uRdKE3wqbCQNiNP1wFA@mail.gmail.com>
	<CAAg5f2S8O-OQXJHW1LEUZEiF7_CUPXtNvK31=SCnXav2oNSyXA@mail.gmail.com>
	<CADF=h2tAqSZvdobU_6Kg1U2N7cc6h=-MMxKww3tjCxmQo+YnsA@mail.gmail.com>
Message-ID: <CAAg5f2S6+q7g=rc7KXne3tnDOhC725peG5e-Nsm3osZdDxkX+A@mail.gmail.com>

ah, I thought it would be still make sense to update the version there :-)

That's not a blocker ;-) Just noticed

On Tue, Jun 23, 2015 at 6:49 PM, Daniel Passos <dpassos at redhat.com> wrote:

> Because test is not part of the release.
>
> On Tue, Jun 23, 2015 at 12:52 PM, Matthias Wessendorf <matzew at apache.org>
> wrote:
>
>> this pom.xml, on the 2.2.0 tag has incorrect version nr:
>> https://github.com/aerogear/aerogear-android-push/blob/2.2.0/aerogear-android-push-test/pom.xml#L29
>>
>>
>> On Fri, Jun 19, 2015 at 12:53 AM, Daniel Passos <dpassos at redhat.com>
>> wrote:
>>
>>> Hi,
>>>
>>> I've staged[1] the Push library 2.2.0 again and send a PR for
>>> UnifiedPush helloworld[2] using it.
>>>
>>> We?re planning to release it next Wednesday
>>>
>>> Fell free to test it and let us know if you find any issues.
>>> [1]
>>> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-5856/
>>> [2] https://github.com/jboss-mobile/unified-push-helloworld/pull/15
>>>
>>>
>>> On Wed, Jun 17, 2015 at 10:36 PM, Daniel Passos <dpassos at redhat.com>
>>> wrote:
>>>
>>>> Hey Guys,
>>>>
>>>> We are postpone it to fix the bug Matthias found. I just send a PR[1]
>>>> to fix it.
>>>>
>>>> [1] https://github.com/aerogear/aerogear-android-push/pull/38
>>>>
>>>> On Wed, Jun 17, 2015 at 11:32 AM, Summers Pittman <supittma at redhat.com>
>>>> wrote:
>>>>
>>>>>
>>>>>
>>>>>
>>>>> On Wed, Jun 17, 2015 at 3:17 AM, Sebastien Blanc <scm.blanc at gmail.com>
>>>>> wrote:
>>>>>
>>>>>> This fix is more a workaround since it was not needed with the
>>>>>> previous versions.  so we need to be sure to check if :
>>>>>>
>>>>> No.  The hello world app is broken.
>>>>>
>>>>>>
>>>>>> - This fix was needed because of other commits on the helloworld
>>>>>>
>>>>> - This fix was needed because of the new version of the library
>>>>>> - This fix was needed because of a change from GCM server
>>>>>> - This fix was needed because of a mix/combination of all the
>>>>>> previous potential causes
>>>>>>
>>>>>
>>>>> TL;DR: We never needed information from the PushRegistrar to handle
>>>>> messages until metrics were added.  Now we do.  However, if the app is
>>>>> garbage collected then the registration information is cleared from memory
>>>>> (it is persisted on the device of course).  Because the notification
>>>>> handler is invoked by android it bypasses the RegisterActivity.  When we
>>>>> try to fetch the registration information to send the metric message it
>>>>> isn't loaded and the NPE is thrown.  Previously had enabled the ability to
>>>>> unregister the client from the message list screen we would have seen
>>>>> similar results.
>>>>>
>>>>> The application work by happy coincidence.  It wasn't until matz
>>>>> tested on a hellishly obsolete device that the issue appeared. ;)
>>>>>
>>>>>
>>>>>
>>>>>> Passos have you been able to test the lib with Aerodoc ?
>>>>>>
>>>>>> Sebi
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Tue, Jun 16, 2015 at 4:50 PM, Daniel Passos <dpassos at redhat.com>
>>>>>> wrote:
>>>>>>
>>>>>>> Seems the problem was in the app not in the library. For more
>>>>>>> details please see my comment[1] in Jira and the fix in this PR[2]
>>>>>>>
>>>>>>> [1]
>>>>>>> https://issues.jboss.org/browse/AGDROID-425?focusedCommentId=13079805&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13079805
>>>>>>> [2] https://github.com/jboss-mobile/unified-push-helloworld/pull/14
>>>>>>>
>>>>>>> On Mon, Jun 15, 2015 at 9:42 AM, Matthias Wessendorf <
>>>>>>> matzew at apache.org> wrote:
>>>>>>>
>>>>>>>> I noticed a little bug w/ the current libray
>>>>>>>>
>>>>>>>> https://issues.jboss.org/browse/AGDROID-425
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> On Mon, Jun 15, 2015 at 2:42 AM, Daniel Passos <dpassos at redhat.com>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> Hey Everyone,
>>>>>>>>>
>>>>>>>>> We are ready to release AeroGear Android Push 2.2.0, we staged[1]
>>>>>>>>> it on Nexus.
>>>>>>>>>
>>>>>>>>> What is new in this version?
>>>>>>>>>
>>>>>>>>>    - AGDROID-422 <https://issues.jboss.org/browse/AGDROID-422> -
>>>>>>>>>    Add support for push-config.json for Android Push SDK
>>>>>>>>>    - AGDROID-423 <https://issues.jboss.org/browse/AGDROID-423> -
>>>>>>>>>    Android SDK hook for notifying the server if app has been opened due to a
>>>>>>>>>    push
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> We?re planning to release it next Thursday.
>>>>>>>>>
>>>>>>>>> Fell free to test it and let us know if you find any issues.
>>>>>>>>>
>>>>>>>>> [1]
>>>>>>>>> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-5783/
>>>>>>>>> ?
>>>>>>>>> --
>>>>>>>>> -- Passos
>>>>>>>>>
>>>>>>>>> _______________________________________________
>>>>>>>>> aerogear-dev mailing list
>>>>>>>>> aerogear-dev at lists.jboss.org
>>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Matthias Wessendorf
>>>>>>>>
>>>>>>>> blog: http://matthiaswessendorf.wordpress.com/
>>>>>>>> sessions: http://www.slideshare.net/mwessendorf
>>>>>>>> twitter: http://twitter.com/mwessendorf
>>>>>>>>
>>>>>>>> _______________________________________________
>>>>>>>> aerogear-dev mailing list
>>>>>>>> aerogear-dev at lists.jboss.org
>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> -- Passos
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> aerogear-dev mailing list
>>>>>>> aerogear-dev at lists.jboss.org
>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>>>>
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> aerogear-dev mailing list
>>>>>> aerogear-dev at lists.jboss.org
>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>>>
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> aerogear-dev mailing list
>>>>> aerogear-dev at lists.jboss.org
>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> -- Passos
>>>>
>>>
>>>
>>>
>>> --
>>> -- Passos
>>>
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>
>>
>>
>> --
>> Matthias Wessendorf
>>
>> blog: http://matthiaswessendorf.wordpress.com/
>> sessions: http://www.slideshare.net/mwessendorf
>> twitter: http://twitter.com/mwessendorf
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
>
> --
> -- Passos
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150623/a2431c4e/attachment-0001.html 

From dpassos at redhat.com  Tue Jun 23 12:58:35 2015
From: dpassos at redhat.com (Daniel Passos)
Date: Tue, 23 Jun 2015 13:58:35 -0300
Subject: [aerogear-dev] AeroGear Android Push 2.2.0
In-Reply-To: <CAAg5f2S6+q7g=rc7KXne3tnDOhC725peG5e-Nsm3osZdDxkX+A@mail.gmail.com>
References: <CADF=h2vVgw1UUGXHs+x=4zr12ZnC9Q=iAuw1z+OtVGQDtO=LFA@mail.gmail.com>
	<CAAg5f2QcCaXJjNUgjG3BmGuPDkRbzVx75EAYJ2rVErZiifMx=g@mail.gmail.com>
	<CADF=h2vO6zErixrULXSim_-PGTQaFcRsJ=y4n3BfJa5VreQZwg@mail.gmail.com>
	<CAD_dpu2u8iENYLASAOAD-EmmQp-nhT0qgCxt8sfvrxjr5y0v+w@mail.gmail.com>
	<CAEQz2Ctkv3AMQbSgbKu8Ugy8WbGY9o44E6xa22TEX8Jyenaxmg@mail.gmail.com>
	<CADF=h2u0kc8d9O93VqHSWazqWtGOQ=Acb=AaOrByYW+d7rNY0g@mail.gmail.com>
	<CADF=h2tm7Ccrdhrje3NhW7XshXiREq=uRdKE3wqbCQNiNP1wFA@mail.gmail.com>
	<CAAg5f2S8O-OQXJHW1LEUZEiF7_CUPXtNvK31=SCnXav2oNSyXA@mail.gmail.com>
	<CADF=h2tAqSZvdobU_6Kg1U2N7cc6h=-MMxKww3tjCxmQo+YnsA@mail.gmail.com>
	<CAAg5f2S6+q7g=rc7KXne3tnDOhC725peG5e-Nsm3osZdDxkX+A@mail.gmail.com>
Message-ID: <CADF=h2tAHvbLTWDoU9jkzSv-qV-1vMNN6PKkhnf2fwbjNtL=uA@mail.gmail.com>

Yeap, Summers and I discussed a bit about it time ago, but we decided not
change anything after run maven release, so we can easily revert the
release using maven-release-plugin. Anyway we are always open to
suggestions.

On Tue, Jun 23, 2015 at 1:53 PM, Matthias Wessendorf <matzew at apache.org>
wrote:

> ah, I thought it would be still make sense to update the version there :-)
>
> That's not a blocker ;-) Just noticed
>
> On Tue, Jun 23, 2015 at 6:49 PM, Daniel Passos <dpassos at redhat.com> wrote:
>
>> Because test is not part of the release.
>>
>> On Tue, Jun 23, 2015 at 12:52 PM, Matthias Wessendorf <matzew at apache.org>
>> wrote:
>>
>>> this pom.xml, on the 2.2.0 tag has incorrect version nr:
>>> https://github.com/aerogear/aerogear-android-push/blob/2.2.0/aerogear-android-push-test/pom.xml#L29
>>>
>>>
>>> On Fri, Jun 19, 2015 at 12:53 AM, Daniel Passos <dpassos at redhat.com>
>>> wrote:
>>>
>>>> Hi,
>>>>
>>>> I've staged[1] the Push library 2.2.0 again and send a PR for
>>>> UnifiedPush helloworld[2] using it.
>>>>
>>>> We?re planning to release it next Wednesday
>>>>
>>>> Fell free to test it and let us know if you find any issues.
>>>> [1]
>>>> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-5856/
>>>> [2] https://github.com/jboss-mobile/unified-push-helloworld/pull/15
>>>>
>>>>
>>>> On Wed, Jun 17, 2015 at 10:36 PM, Daniel Passos <dpassos at redhat.com>
>>>> wrote:
>>>>
>>>>> Hey Guys,
>>>>>
>>>>> We are postpone it to fix the bug Matthias found. I just send a PR[1]
>>>>> to fix it.
>>>>>
>>>>> [1] https://github.com/aerogear/aerogear-android-push/pull/38
>>>>>
>>>>> On Wed, Jun 17, 2015 at 11:32 AM, Summers Pittman <supittma at redhat.com
>>>>> > wrote:
>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Wed, Jun 17, 2015 at 3:17 AM, Sebastien Blanc <scm.blanc at gmail.com
>>>>>> > wrote:
>>>>>>
>>>>>>> This fix is more a workaround since it was not needed with the
>>>>>>> previous versions.  so we need to be sure to check if :
>>>>>>>
>>>>>> No.  The hello world app is broken.
>>>>>>
>>>>>>>
>>>>>>> - This fix was needed because of other commits on the helloworld
>>>>>>>
>>>>>> - This fix was needed because of the new version of the library
>>>>>>> - This fix was needed because of a change from GCM server
>>>>>>> - This fix was needed because of a mix/combination of all the
>>>>>>> previous potential causes
>>>>>>>
>>>>>>
>>>>>> TL;DR: We never needed information from the PushRegistrar to handle
>>>>>> messages until metrics were added.  Now we do.  However, if the app is
>>>>>> garbage collected then the registration information is cleared from memory
>>>>>> (it is persisted on the device of course).  Because the notification
>>>>>> handler is invoked by android it bypasses the RegisterActivity.  When we
>>>>>> try to fetch the registration information to send the metric message it
>>>>>> isn't loaded and the NPE is thrown.  Previously had enabled the ability to
>>>>>> unregister the client from the message list screen we would have seen
>>>>>> similar results.
>>>>>>
>>>>>> The application work by happy coincidence.  It wasn't until matz
>>>>>> tested on a hellishly obsolete device that the issue appeared. ;)
>>>>>>
>>>>>>
>>>>>>
>>>>>>> Passos have you been able to test the lib with Aerodoc ?
>>>>>>>
>>>>>>> Sebi
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Tue, Jun 16, 2015 at 4:50 PM, Daniel Passos <dpassos at redhat.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Seems the problem was in the app not in the library. For more
>>>>>>>> details please see my comment[1] in Jira and the fix in this PR[2]
>>>>>>>>
>>>>>>>> [1]
>>>>>>>> https://issues.jboss.org/browse/AGDROID-425?focusedCommentId=13079805&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13079805
>>>>>>>> [2] https://github.com/jboss-mobile/unified-push-helloworld/pull/14
>>>>>>>>
>>>>>>>> On Mon, Jun 15, 2015 at 9:42 AM, Matthias Wessendorf <
>>>>>>>> matzew at apache.org> wrote:
>>>>>>>>
>>>>>>>>> I noticed a little bug w/ the current libray
>>>>>>>>>
>>>>>>>>> https://issues.jboss.org/browse/AGDROID-425
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Mon, Jun 15, 2015 at 2:42 AM, Daniel Passos <dpassos at redhat.com
>>>>>>>>> > wrote:
>>>>>>>>>
>>>>>>>>>> Hey Everyone,
>>>>>>>>>>
>>>>>>>>>> We are ready to release AeroGear Android Push 2.2.0, we staged[1]
>>>>>>>>>> it on Nexus.
>>>>>>>>>>
>>>>>>>>>> What is new in this version?
>>>>>>>>>>
>>>>>>>>>>    - AGDROID-422 <https://issues.jboss.org/browse/AGDROID-422> -
>>>>>>>>>>    Add support for push-config.json for Android Push SDK
>>>>>>>>>>    - AGDROID-423 <https://issues.jboss.org/browse/AGDROID-423> -
>>>>>>>>>>    Android SDK hook for notifying the server if app has been opened due to a
>>>>>>>>>>    push
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> We?re planning to release it next Thursday.
>>>>>>>>>>
>>>>>>>>>> Fell free to test it and let us know if you find any issues.
>>>>>>>>>>
>>>>>>>>>> [1]
>>>>>>>>>> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-5783/
>>>>>>>>>> ?
>>>>>>>>>> --
>>>>>>>>>> -- Passos
>>>>>>>>>>
>>>>>>>>>> _______________________________________________
>>>>>>>>>> aerogear-dev mailing list
>>>>>>>>>> aerogear-dev at lists.jboss.org
>>>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Matthias Wessendorf
>>>>>>>>>
>>>>>>>>> blog: http://matthiaswessendorf.wordpress.com/
>>>>>>>>> sessions: http://www.slideshare.net/mwessendorf
>>>>>>>>> twitter: http://twitter.com/mwessendorf
>>>>>>>>>
>>>>>>>>> _______________________________________________
>>>>>>>>> aerogear-dev mailing list
>>>>>>>>> aerogear-dev at lists.jboss.org
>>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> -- Passos
>>>>>>>>
>>>>>>>> _______________________________________________
>>>>>>>> aerogear-dev mailing list
>>>>>>>> aerogear-dev at lists.jboss.org
>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> aerogear-dev mailing list
>>>>>>> aerogear-dev at lists.jboss.org
>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>>>>
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> aerogear-dev mailing list
>>>>>> aerogear-dev at lists.jboss.org
>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> -- Passos
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> -- Passos
>>>>
>>>> _______________________________________________
>>>> aerogear-dev mailing list
>>>> aerogear-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>
>>>
>>>
>>>
>>> --
>>> Matthias Wessendorf
>>>
>>> blog: http://matthiaswessendorf.wordpress.com/
>>> sessions: http://www.slideshare.net/mwessendorf
>>> twitter: http://twitter.com/mwessendorf
>>>
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>
>>
>>
>> --
>> -- Passos
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 
-- Passos
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150623/6ffc862b/attachment.html 

From matzew at apache.org  Tue Jun 23 12:59:11 2015
From: matzew at apache.org (Matthias Wessendorf)
Date: Tue, 23 Jun 2015 18:59:11 +0200
Subject: [aerogear-dev] AeroGear Android Push 2.2.0
In-Reply-To: <CAAg5f2S6+q7g=rc7KXne3tnDOhC725peG5e-Nsm3osZdDxkX+A@mail.gmail.com>
References: <CADF=h2vVgw1UUGXHs+x=4zr12ZnC9Q=iAuw1z+OtVGQDtO=LFA@mail.gmail.com>
	<CAAg5f2QcCaXJjNUgjG3BmGuPDkRbzVx75EAYJ2rVErZiifMx=g@mail.gmail.com>
	<CADF=h2vO6zErixrULXSim_-PGTQaFcRsJ=y4n3BfJa5VreQZwg@mail.gmail.com>
	<CAD_dpu2u8iENYLASAOAD-EmmQp-nhT0qgCxt8sfvrxjr5y0v+w@mail.gmail.com>
	<CAEQz2Ctkv3AMQbSgbKu8Ugy8WbGY9o44E6xa22TEX8Jyenaxmg@mail.gmail.com>
	<CADF=h2u0kc8d9O93VqHSWazqWtGOQ=Acb=AaOrByYW+d7rNY0g@mail.gmail.com>
	<CADF=h2tm7Ccrdhrje3NhW7XshXiREq=uRdKE3wqbCQNiNP1wFA@mail.gmail.com>
	<CAAg5f2S8O-OQXJHW1LEUZEiF7_CUPXtNvK31=SCnXav2oNSyXA@mail.gmail.com>
	<CADF=h2tAqSZvdobU_6Kg1U2N7cc6h=-MMxKww3tjCxmQo+YnsA@mail.gmail.com>
	<CAAg5f2S6+q7g=rc7KXne3tnDOhC725peG5e-Nsm3osZdDxkX+A@mail.gmail.com>
Message-ID: <CAAg5f2SUWrymfpku8_dspD5zrN4QWj8xD7LMRJy111K_1FX2Ug@mail.gmail.com>

Actually - this makes the TAG unusable :-)

The tests are not compinging, since pointing to the -SNAPSHOT version of
the actual push lib, here:
https://github.com/aerogear/aerogear-android-push/blob/2.2.0/aerogear-android-push-test/pom.xml#L50

Changing that to 2.2.0 makes it work.

Again, not a show stopper, but something nice to have e.g. for 2.3.0


+1 on the release


On Tue, Jun 23, 2015 at 6:53 PM, Matthias Wessendorf <matzew at apache.org>
wrote:

> ah, I thought it would be still make sense to update the version there :-)
>
> That's not a blocker ;-) Just noticed
>
> On Tue, Jun 23, 2015 at 6:49 PM, Daniel Passos <dpassos at redhat.com> wrote:
>
>> Because test is not part of the release.
>>
>> On Tue, Jun 23, 2015 at 12:52 PM, Matthias Wessendorf <matzew at apache.org>
>> wrote:
>>
>>> this pom.xml, on the 2.2.0 tag has incorrect version nr:
>>> https://github.com/aerogear/aerogear-android-push/blob/2.2.0/aerogear-android-push-test/pom.xml#L29
>>>
>>>
>>> On Fri, Jun 19, 2015 at 12:53 AM, Daniel Passos <dpassos at redhat.com>
>>> wrote:
>>>
>>>> Hi,
>>>>
>>>> I've staged[1] the Push library 2.2.0 again and send a PR for
>>>> UnifiedPush helloworld[2] using it.
>>>>
>>>> We?re planning to release it next Wednesday
>>>>
>>>> Fell free to test it and let us know if you find any issues.
>>>> [1]
>>>> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-5856/
>>>> [2] https://github.com/jboss-mobile/unified-push-helloworld/pull/15
>>>>
>>>>
>>>> On Wed, Jun 17, 2015 at 10:36 PM, Daniel Passos <dpassos at redhat.com>
>>>> wrote:
>>>>
>>>>> Hey Guys,
>>>>>
>>>>> We are postpone it to fix the bug Matthias found. I just send a PR[1]
>>>>> to fix it.
>>>>>
>>>>> [1] https://github.com/aerogear/aerogear-android-push/pull/38
>>>>>
>>>>> On Wed, Jun 17, 2015 at 11:32 AM, Summers Pittman <supittma at redhat.com
>>>>> > wrote:
>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Wed, Jun 17, 2015 at 3:17 AM, Sebastien Blanc <scm.blanc at gmail.com
>>>>>> > wrote:
>>>>>>
>>>>>>> This fix is more a workaround since it was not needed with the
>>>>>>> previous versions.  so we need to be sure to check if :
>>>>>>>
>>>>>> No.  The hello world app is broken.
>>>>>>
>>>>>>>
>>>>>>> - This fix was needed because of other commits on the helloworld
>>>>>>>
>>>>>> - This fix was needed because of the new version of the library
>>>>>>> - This fix was needed because of a change from GCM server
>>>>>>> - This fix was needed because of a mix/combination of all the
>>>>>>> previous potential causes
>>>>>>>
>>>>>>
>>>>>> TL;DR: We never needed information from the PushRegistrar to handle
>>>>>> messages until metrics were added.  Now we do.  However, if the app is
>>>>>> garbage collected then the registration information is cleared from memory
>>>>>> (it is persisted on the device of course).  Because the notification
>>>>>> handler is invoked by android it bypasses the RegisterActivity.  When we
>>>>>> try to fetch the registration information to send the metric message it
>>>>>> isn't loaded and the NPE is thrown.  Previously had enabled the ability to
>>>>>> unregister the client from the message list screen we would have seen
>>>>>> similar results.
>>>>>>
>>>>>> The application work by happy coincidence.  It wasn't until matz
>>>>>> tested on a hellishly obsolete device that the issue appeared. ;)
>>>>>>
>>>>>>
>>>>>>
>>>>>>> Passos have you been able to test the lib with Aerodoc ?
>>>>>>>
>>>>>>> Sebi
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Tue, Jun 16, 2015 at 4:50 PM, Daniel Passos <dpassos at redhat.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Seems the problem was in the app not in the library. For more
>>>>>>>> details please see my comment[1] in Jira and the fix in this PR[2]
>>>>>>>>
>>>>>>>> [1]
>>>>>>>> https://issues.jboss.org/browse/AGDROID-425?focusedCommentId=13079805&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13079805
>>>>>>>> [2] https://github.com/jboss-mobile/unified-push-helloworld/pull/14
>>>>>>>>
>>>>>>>> On Mon, Jun 15, 2015 at 9:42 AM, Matthias Wessendorf <
>>>>>>>> matzew at apache.org> wrote:
>>>>>>>>
>>>>>>>>> I noticed a little bug w/ the current libray
>>>>>>>>>
>>>>>>>>> https://issues.jboss.org/browse/AGDROID-425
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Mon, Jun 15, 2015 at 2:42 AM, Daniel Passos <dpassos at redhat.com
>>>>>>>>> > wrote:
>>>>>>>>>
>>>>>>>>>> Hey Everyone,
>>>>>>>>>>
>>>>>>>>>> We are ready to release AeroGear Android Push 2.2.0, we staged[1]
>>>>>>>>>> it on Nexus.
>>>>>>>>>>
>>>>>>>>>> What is new in this version?
>>>>>>>>>>
>>>>>>>>>>    - AGDROID-422 <https://issues.jboss.org/browse/AGDROID-422> -
>>>>>>>>>>    Add support for push-config.json for Android Push SDK
>>>>>>>>>>    - AGDROID-423 <https://issues.jboss.org/browse/AGDROID-423> -
>>>>>>>>>>    Android SDK hook for notifying the server if app has been opened due to a
>>>>>>>>>>    push
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> We?re planning to release it next Thursday.
>>>>>>>>>>
>>>>>>>>>> Fell free to test it and let us know if you find any issues.
>>>>>>>>>>
>>>>>>>>>> [1]
>>>>>>>>>> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-5783/
>>>>>>>>>> ?
>>>>>>>>>> --
>>>>>>>>>> -- Passos
>>>>>>>>>>
>>>>>>>>>> _______________________________________________
>>>>>>>>>> aerogear-dev mailing list
>>>>>>>>>> aerogear-dev at lists.jboss.org
>>>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Matthias Wessendorf
>>>>>>>>>
>>>>>>>>> blog: http://matthiaswessendorf.wordpress.com/
>>>>>>>>> sessions: http://www.slideshare.net/mwessendorf
>>>>>>>>> twitter: http://twitter.com/mwessendorf
>>>>>>>>>
>>>>>>>>> _______________________________________________
>>>>>>>>> aerogear-dev mailing list
>>>>>>>>> aerogear-dev at lists.jboss.org
>>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> -- Passos
>>>>>>>>
>>>>>>>> _______________________________________________
>>>>>>>> aerogear-dev mailing list
>>>>>>>> aerogear-dev at lists.jboss.org
>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> aerogear-dev mailing list
>>>>>>> aerogear-dev at lists.jboss.org
>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>>>>
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> aerogear-dev mailing list
>>>>>> aerogear-dev at lists.jboss.org
>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> -- Passos
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> -- Passos
>>>>
>>>> _______________________________________________
>>>> aerogear-dev mailing list
>>>> aerogear-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>
>>>
>>>
>>>
>>> --
>>> Matthias Wessendorf
>>>
>>> blog: http://matthiaswessendorf.wordpress.com/
>>> sessions: http://www.slideshare.net/mwessendorf
>>> twitter: http://twitter.com/mwessendorf
>>>
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>
>>
>>
>> --
>> -- Passos
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>



-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150623/565d3078/attachment-0001.html 

From matzew at apache.org  Wed Jun 24 10:00:18 2015
From: matzew at apache.org (Matthias Wessendorf)
Date: Wed, 24 Jun 2015 16:00:18 +0200
Subject: [aerogear-dev] UPS: Wizard usage issue?
Message-ID: <CAAg5f2QSs0VCKcFSwXMzpQ+P-0FwgzNTGVfxTJR95a4-20O8aw@mail.gmail.com>

Hi,

I just noticed (working on the doc) that when clicking through the wizard,
I can only add one variant

Now, I am wondering if we should update the wizard, so that I can also add
another vairant, inside of the wizard ?

Or is that something we have done on design? That we just want just one
variant to be created on the wizard - and for a second (and third, etc)
variant, the user must go to the puah-app and add it there ?

Thanks,
Matze


-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150624/20f004b8/attachment.html 

From scm.blanc at gmail.com  Wed Jun 24 10:30:43 2015
From: scm.blanc at gmail.com (Sebastien Blanc)
Date: Wed, 24 Jun 2015 16:30:43 +0200
Subject: [aerogear-dev] UPS: Wizard usage issue?
In-Reply-To: <CAAg5f2QSs0VCKcFSwXMzpQ+P-0FwgzNTGVfxTJR95a4-20O8aw@mail.gmail.com>
References: <CAAg5f2QSs0VCKcFSwXMzpQ+P-0FwgzNTGVfxTJR95a4-20O8aw@mail.gmail.com>
Message-ID: <CAD_dpu0gigVyBkfJ8nB+uDO07WbQ8jEX_M1ZeaPd3G=gqM1vow@mail.gmail.com>

I can see the need but honestly I think that 90% of the time when someone
sets up a Push Application, he will start with only one variant to test.
Then since he already knows how it works, he can add another variant the
"raw" way.
We could add it but that could happen later (1.2 ?) but that is just my
opinion.

Sebi


On Wed, Jun 24, 2015 at 4:00 PM, Matthias Wessendorf <matzew at apache.org>
wrote:

> Hi,
>
> I just noticed (working on the doc) that when clicking through the wizard,
> I can only add one variant
>
> Now, I am wondering if we should update the wizard, so that I can also add
> another vairant, inside of the wizard ?
>
> Or is that something we have done on design? That we just want just one
> variant to be created on the wizard - and for a second (and third, etc)
> variant, the user must go to the puah-app and add it there ?
>
> Thanks,
> Matze
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150624/a5d1da84/attachment.html 

From dpassos at redhat.com  Wed Jun 24 10:42:02 2015
From: dpassos at redhat.com (Daniel Passos)
Date: Wed, 24 Jun 2015 11:42:02 -0300
Subject: [aerogear-dev] UPS: Wizard usage issue?
In-Reply-To: <CAD_dpu0gigVyBkfJ8nB+uDO07WbQ8jEX_M1ZeaPd3G=gqM1vow@mail.gmail.com>
References: <CAAg5f2QSs0VCKcFSwXMzpQ+P-0FwgzNTGVfxTJR95a4-20O8aw@mail.gmail.com>
	<CAD_dpu0gigVyBkfJ8nB+uDO07WbQ8jEX_M1ZeaPd3G=gqM1vow@mail.gmail.com>
Message-ID: <CADF=h2sRP+1sx8y5ptKBd3qH20rS9JQh-5R5utQrASXasB_OGw@mail.gmail.com>

I agree with Sebi. 90% (or more) will add only only variant, anyway I can't
see any problem in go to the app and add another only (after wizard
finished)

On Wed, Jun 24, 2015 at 11:30 AM, Sebastien Blanc <scm.blanc at gmail.com>
wrote:

> I can see the need but honestly I think that 90% of the time when someone
> sets up a Push Application, he will start with only one variant to test.
> Then since he already knows how it works, he can add another variant the
> "raw" way.
> We could add it but that could happen later (1.2 ?) but that is just my
> opinion.
>
> Sebi
>
>
> On Wed, Jun 24, 2015 at 4:00 PM, Matthias Wessendorf <matzew at apache.org>
> wrote:
>
>> Hi,
>>
>> I just noticed (working on the doc) that when clicking through the
>> wizard, I can only add one variant
>>
>> Now, I am wondering if we should update the wizard, so that I can also
>> add another vairant, inside of the wizard ?
>>
>> Or is that something we have done on design? That we just want just one
>> variant to be created on the wizard - and for a second (and third, etc)
>> variant, the user must go to the puah-app and add it there ?
>>
>> Thanks,
>> Matze
>>
>>
>> --
>> Matthias Wessendorf
>>
>> blog: http://matthiaswessendorf.wordpress.com/
>> sessions: http://www.slideshare.net/mwessendorf
>> twitter: http://twitter.com/mwessendorf
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 
-- Passos
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150624/9ded57b2/attachment.html 

From matzew at apache.org  Wed Jun 24 10:48:17 2015
From: matzew at apache.org (Matthias Wessendorf)
Date: Wed, 24 Jun 2015 16:48:17 +0200
Subject: [aerogear-dev] UPS: Wizard usage issue?
In-Reply-To: <CADF=h2sRP+1sx8y5ptKBd3qH20rS9JQh-5R5utQrASXasB_OGw@mail.gmail.com>
References: <CAAg5f2QSs0VCKcFSwXMzpQ+P-0FwgzNTGVfxTJR95a4-20O8aw@mail.gmail.com>
	<CAD_dpu0gigVyBkfJ8nB+uDO07WbQ8jEX_M1ZeaPd3G=gqM1vow@mail.gmail.com>
	<CADF=h2sRP+1sx8y5ptKBd3qH20rS9JQh-5R5utQrASXasB_OGw@mail.gmail.com>
Message-ID: <CAAg5f2Roc-DwhZoX=-q56k=65oX2KjQG4WK2b_wMO=5Xa3Ljpg@mail.gmail.com>

Ok, fair enough - I was just wondering, since we discussed that earlier and
I just realized it, while working on the doc



On Wed, Jun 24, 2015 at 4:42 PM, Daniel Passos <dpassos at redhat.com> wrote:

> I agree with Sebi. 90% (or more) will add only only variant, anyway I
> can't see any problem in go to the app and add another only (after wizard
> finished)
>
> On Wed, Jun 24, 2015 at 11:30 AM, Sebastien Blanc <scm.blanc at gmail.com>
> wrote:
>
>> I can see the need but honestly I think that 90% of the time when someone
>> sets up a Push Application, he will start with only one variant to test.
>> Then since he already knows how it works, he can add another variant the
>> "raw" way.
>> We could add it but that could happen later (1.2 ?) but that is just my
>> opinion.
>>
>> Sebi
>>
>>
>> On Wed, Jun 24, 2015 at 4:00 PM, Matthias Wessendorf <matzew at apache.org>
>> wrote:
>>
>>> Hi,
>>>
>>> I just noticed (working on the doc) that when clicking through the
>>> wizard, I can only add one variant
>>>
>>> Now, I am wondering if we should update the wizard, so that I can also
>>> add another vairant, inside of the wizard ?
>>>
>>> Or is that something we have done on design? That we just want just one
>>> variant to be created on the wizard - and for a second (and third, etc)
>>> variant, the user must go to the puah-app and add it there ?
>>>
>>> Thanks,
>>> Matze
>>>
>>>
>>> --
>>> Matthias Wessendorf
>>>
>>> blog: http://matthiaswessendorf.wordpress.com/
>>> sessions: http://www.slideshare.net/mwessendorf
>>> twitter: http://twitter.com/mwessendorf
>>>
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
>
> --
> -- Passos
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150624/3c2f77ae/attachment.html 

From matzew at apache.org  Wed Jun 24 11:20:20 2015
From: matzew at apache.org (Matthias Wessendorf)
Date: Wed, 24 Jun 2015 17:20:20 +0200
Subject: [aerogear-dev] UPS: Console - Visibility issues
Message-ID: <CAAg5f2SF6bo8yuhj5gvdx6prY8Srreevrqp2XKLVNsmFne-+aQ@mail.gmail.com>

Hi,

on our old design the PushApplicationID/MasterSecret was very good to
notice:
https://aerogear.org/docs/unifiedpush/ups_userguide//img/applications_variant.png

Now it's a bit more hidden (one has to click on the "Sender API" tab of the
Application).

Similar w/ the VariantID/Secret pair, IMO it is also a bit hidden, since
this is only visible in the source snippets for the variant.

They used to be a bit more present:
https://aerogear.org/docs/unifiedpush/ups_userguide//img/applications_variant_details.png

Since I find that suboptimal, I am wondering if that's done for a good
reason, or if something (in a future version?) should be changed ?

-M

-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150624/9d1493a8/attachment-0001.html 

From lukas at fryc.eu  Wed Jun 24 13:12:20 2015
From: lukas at fryc.eu (=?UTF-8?B?THVrw6HFoSBGcnnEjQ==?=)
Date: Wed, 24 Jun 2015 17:12:20 +0000
Subject: [aerogear-dev] UPS: Console - Visibility issues
In-Reply-To: <CAAg5f2SF6bo8yuhj5gvdx6prY8Srreevrqp2XKLVNsmFne-+aQ@mail.gmail.com>
References: <CAAg5f2SF6bo8yuhj5gvdx6prY8Srreevrqp2XKLVNsmFne-+aQ@mail.gmail.com>
Message-ID: <CAEroY369GzXXTeAPyDsY=x3_zC_5iOF=9_p+xHmvcBQF3LUzOg@mail.gmail.com>

Basically it is something that we "agreed on" (or rather didn't catch)
during mockup reviews and that never changed from that time.

@Andres: did it have some reason to hide the details?

I'm all for exposing it more visibly.

st 24. 6. 2015 v 17:21 odes?latel Matthias Wessendorf <matzew at apache.org>
napsal:

> Hi,
>
> on our old design the PushApplicationID/MasterSecret was very good to
> notice:
>
> https://aerogear.org/docs/unifiedpush/ups_userguide//img/applications_variant.png
>
> Now it's a bit more hidden (one has to click on the "Sender API" tab of
> the Application).
>
> Similar w/ the VariantID/Secret pair, IMO it is also a bit hidden, since
> this is only visible in the source snippets for the variant.
>
> They used to be a bit more present:
>
> https://aerogear.org/docs/unifiedpush/ups_userguide//img/applications_variant_details.png
>
> Since I find that suboptimal, I am wondering if that's done for a good
> reason, or if something (in a future version?) should be changed ?
>
> -M
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>  _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150624/bb78eb40/attachment.html 

From lukas.fryc at gmail.com  Wed Jun 24 13:13:37 2015
From: lukas.fryc at gmail.com (=?UTF-8?B?THVrw6HFoSBGcnnEjQ==?=)
Date: Wed, 24 Jun 2015 17:13:37 +0000
Subject: [aerogear-dev] UPS: Wizard usage issue?
In-Reply-To: <CAAg5f2Roc-DwhZoX=-q56k=65oX2KjQG4WK2b_wMO=5Xa3Ljpg@mail.gmail.com>
References: <CAAg5f2QSs0VCKcFSwXMzpQ+P-0FwgzNTGVfxTJR95a4-20O8aw@mail.gmail.com>
	<CAD_dpu0gigVyBkfJ8nB+uDO07WbQ8jEX_M1ZeaPd3G=gqM1vow@mail.gmail.com>
	<CADF=h2sRP+1sx8y5ptKBd3qH20rS9JQh-5R5utQrASXasB_OGw@mail.gmail.com>
	<CAAg5f2Roc-DwhZoX=-q56k=65oX2KjQG4WK2b_wMO=5Xa3Ljpg@mail.gmail.com>
Message-ID: <CAEroY34jecbHWKeB+WJ_YDS6cr1xd=ziNefW2HTMTM89PYzjPw@mail.gmail.com>

+1 agree with Sebi

we can add a note that more variants can be added later once the wizard is
finished

st 24. 6. 2015 v 16:48 odes?latel Matthias Wessendorf <matzew at apache.org>
napsal:

> Ok, fair enough - I was just wondering, since we discussed that earlier
> and I just realized it, while working on the doc
>
>
>
> On Wed, Jun 24, 2015 at 4:42 PM, Daniel Passos <dpassos at redhat.com> wrote:
>
>> I agree with Sebi. 90% (or more) will add only only variant, anyway I
>> can't see any problem in go to the app and add another only (after wizard
>> finished)
>>
>> On Wed, Jun 24, 2015 at 11:30 AM, Sebastien Blanc <scm.blanc at gmail.com>
>> wrote:
>>
>>> I can see the need but honestly I think that 90% of the time when
>>> someone sets up a Push Application, he will start with only one variant to
>>> test. Then since he already knows how it works, he can add another variant
>>> the "raw" way.
>>> We could add it but that could happen later (1.2 ?) but that is just my
>>> opinion.
>>>
>>> Sebi
>>>
>>>
>>> On Wed, Jun 24, 2015 at 4:00 PM, Matthias Wessendorf <matzew at apache.org>
>>> wrote:
>>>
>>>> Hi,
>>>>
>>>> I just noticed (working on the doc) that when clicking through the
>>>> wizard, I can only add one variant
>>>>
>>>> Now, I am wondering if we should update the wizard, so that I can also
>>>> add another vairant, inside of the wizard ?
>>>>
>>>> Or is that something we have done on design? That we just want just one
>>>> variant to be created on the wizard - and for a second (and third, etc)
>>>> variant, the user must go to the puah-app and add it there ?
>>>>
>>>> Thanks,
>>>> Matze
>>>>
>>>>
>>>> --
>>>> Matthias Wessendorf
>>>>
>>>> blog: http://matthiaswessendorf.wordpress.com/
>>>> sessions: http://www.slideshare.net/mwessendorf
>>>> twitter: http://twitter.com/mwessendorf
>>>>
>>>> _______________________________________________
>>>> aerogear-dev mailing list
>>>> aerogear-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>
>>>
>>>
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>
>>
>>
>> --
>> -- Passos
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>  _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150624/87f92be0/attachment.html 

From scm.blanc at gmail.com  Wed Jun 24 13:18:13 2015
From: scm.blanc at gmail.com (=?utf-8?Q?S=C3=A9bastien_Blanc?=)
Date: Wed, 24 Jun 2015 19:18:13 +0200
Subject: [aerogear-dev] UPS: Wizard usage issue?
In-Reply-To: <CAEroY34jecbHWKeB+WJ_YDS6cr1xd=ziNefW2HTMTM89PYzjPw@mail.gmail.com>
References: <CAAg5f2QSs0VCKcFSwXMzpQ+P-0FwgzNTGVfxTJR95a4-20O8aw@mail.gmail.com>
	<CAD_dpu0gigVyBkfJ8nB+uDO07WbQ8jEX_M1ZeaPd3G=gqM1vow@mail.gmail.com>
	<CADF=h2sRP+1sx8y5ptKBd3qH20rS9JQh-5R5utQrASXasB_OGw@mail.gmail.com>
	<CAAg5f2Roc-DwhZoX=-q56k=65oX2KjQG4WK2b_wMO=5Xa3Ljpg@mail.gmail.com>
	<CAEroY34jecbHWKeB+WJ_YDS6cr1xd=ziNefW2HTMTM89PYzjPw@mail.gmail.com>
Message-ID: <42439BF5-FE75-4505-9AF0-361B3B6D643B@gmail.com>



Envoy? de mon iPhone

> Le 24 juin 2015 ? 19:13, Luk?? Fry? <lukas.fryc at gmail.com> a ?crit :
> 
> +1 agree with Sebi
> 
> we can add a note that more variants can be added later once the wizard is finished
+1 good idea
> 
> st 24. 6. 2015 v 16:48 odes?latel Matthias Wessendorf <matzew at apache.org> napsal:
>> Ok, fair enough - I was just wondering, since we discussed that earlier and I just realized it, while working on the doc
>> 
>> 
>> 
>>> On Wed, Jun 24, 2015 at 4:42 PM, Daniel Passos <dpassos at redhat.com> wrote:
>>> I agree with Sebi. 90% (or more) will add only only variant, anyway I can't see any problem in go to the app and add another only (after wizard finished)
>>> 
>>>> On Wed, Jun 24, 2015 at 11:30 AM, Sebastien Blanc <scm.blanc at gmail.com> wrote:
>>>> I can see the need but honestly I think that 90% of the time when someone sets up a Push Application, he will start with only one variant to test. Then since he already knows how it works, he can add another variant the "raw" way.
>>>> We could add it but that could happen later (1.2 ?) but that is just my opinion.
>>>> 
>>>> Sebi
>>>> 
>>>> 
>>>>> On Wed, Jun 24, 2015 at 4:00 PM, Matthias Wessendorf <matzew at apache.org> wrote:
>>>>> Hi,
>>>>> 
>>>>> I just noticed (working on the doc) that when clicking through the wizard, I can only add one variant
>>>>> 
>>>>> Now, I am wondering if we should update the wizard, so that I can also add another vairant, inside of the wizard ? 
>>>>> 
>>>>> Or is that something we have done on design? That we just want just one variant to be created on the wizard - and for a second (and third, etc) variant, the user must go to the puah-app and add it there ? 
>>>>> 
>>>>> Thanks,
>>>>> Matze
>>>>> 
>>>>> 
>>>>> -- 
>>>>> Matthias Wessendorf 
>>>>> 
>>>>> blog: http://matthiaswessendorf.wordpress.com/
>>>>> sessions: http://www.slideshare.net/mwessendorf
>>>>> twitter: http://twitter.com/mwessendorf
>>>>> 
>>>>> _______________________________________________
>>>>> aerogear-dev mailing list
>>>>> aerogear-dev at lists.jboss.org
>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>> 
>>>> 
>>>> _______________________________________________
>>>> aerogear-dev mailing list
>>>> aerogear-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>> 
>>> 
>>> 
>>> -- 
>>> -- Passos
>>> 
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>> 
>> 
>> 
>> -- 
>> Matthias Wessendorf 
>> 
>> blog: http://matthiaswessendorf.wordpress.com/
>> sessions: http://www.slideshare.net/mwessendorf
>> twitter: http://twitter.com/mwessendorf
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150624/b6c76c9e/attachment-0001.html 

From matzew at apache.org  Wed Jun 24 13:40:50 2015
From: matzew at apache.org (Matthias Wessendorf)
Date: Wed, 24 Jun 2015 19:40:50 +0200
Subject: [aerogear-dev] UPS: Wizard usage issue?
In-Reply-To: <42439BF5-FE75-4505-9AF0-361B3B6D643B@gmail.com>
References: <CAAg5f2QSs0VCKcFSwXMzpQ+P-0FwgzNTGVfxTJR95a4-20O8aw@mail.gmail.com>
	<CAD_dpu0gigVyBkfJ8nB+uDO07WbQ8jEX_M1ZeaPd3G=gqM1vow@mail.gmail.com>
	<CADF=h2sRP+1sx8y5ptKBd3qH20rS9JQh-5R5utQrASXasB_OGw@mail.gmail.com>
	<CAAg5f2Roc-DwhZoX=-q56k=65oX2KjQG4WK2b_wMO=5Xa3Ljpg@mail.gmail.com>
	<CAEroY34jecbHWKeB+WJ_YDS6cr1xd=ziNefW2HTMTM89PYzjPw@mail.gmail.com>
	<42439BF5-FE75-4505-9AF0-361B3B6D643B@gmail.com>
Message-ID: <CAAg5f2SLoN1KAGqdz2aMw5fgWf2XrXW=cTMde+6xL6XbOkuHZw@mail.gmail.com>

On Wednesday, June 24, 2015, S?bastien Blanc <scm.blanc at gmail.com> wrote:

>
>
> Envoy? de mon iPhone
>
> Le 24 juin 2015 ? 19:13, Luk?? Fry? <lukas.fryc at gmail.com
> <javascript:_e(%7B%7D,'cvml','lukas.fryc at gmail.com');>> a ?crit :
>
> +1 agree with Sebi
>
> we can add a note that more variants can be added later once the wizard is
> finished
>
> +1 good idea
>
like that too
+1



>
>
> st 24. 6. 2015 v 16:48 odes?latel Matthias Wessendorf <matzew at apache.org
> <javascript:_e(%7B%7D,'cvml','matzew at apache.org');>> napsal:
>
>> Ok, fair enough - I was just wondering, since we discussed that earlier
>> and I just realized it, while working on the doc
>>
>>
>>
>> On Wed, Jun 24, 2015 at 4:42 PM, Daniel Passos <dpassos at redhat.com
>> <javascript:_e(%7B%7D,'cvml','dpassos at redhat.com');>> wrote:
>>
>>> I agree with Sebi. 90% (or more) will add only only variant, anyway I
>>> can't see any problem in go to the app and add another only (after wizard
>>> finished)
>>>
>>> On Wed, Jun 24, 2015 at 11:30 AM, Sebastien Blanc <scm.blanc at gmail.com
>>> <javascript:_e(%7B%7D,'cvml','scm.blanc at gmail.com');>> wrote:
>>>
>>>> I can see the need but honestly I think that 90% of the time when
>>>> someone sets up a Push Application, he will start with only one variant to
>>>> test. Then since he already knows how it works, he can add another variant
>>>> the "raw" way.
>>>> We could add it but that could happen later (1.2 ?) but that is just my
>>>> opinion.
>>>>
>>>> Sebi
>>>>
>>>>
>>>> On Wed, Jun 24, 2015 at 4:00 PM, Matthias Wessendorf <matzew at apache.org
>>>> <javascript:_e(%7B%7D,'cvml','matzew at apache.org');>> wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> I just noticed (working on the doc) that when clicking through the
>>>>> wizard, I can only add one variant
>>>>>
>>>>> Now, I am wondering if we should update the wizard, so that I can also
>>>>> add another vairant, inside of the wizard ?
>>>>>
>>>>> Or is that something we have done on design? That we just want just
>>>>> one variant to be created on the wizard - and for a second (and third, etc)
>>>>> variant, the user must go to the puah-app and add it there ?
>>>>>
>>>>> Thanks,
>>>>> Matze
>>>>>
>>>>>
>>>>> --
>>>>> Matthias Wessendorf
>>>>>
>>>>> blog: http://matthiaswessendorf.wordpress.com/
>>>>> sessions: http://www.slideshare.net/mwessendorf
>>>>> twitter: http://twitter.com/mwessendorf
>>>>>
>>>>> _______________________________________________
>>>>> aerogear-dev mailing list
>>>>> aerogear-dev at lists.jboss.org
>>>>> <javascript:_e(%7B%7D,'cvml','aerogear-dev at lists.jboss.org');>
>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> aerogear-dev mailing list
>>>> aerogear-dev at lists.jboss.org
>>>> <javascript:_e(%7B%7D,'cvml','aerogear-dev at lists.jboss.org');>
>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>
>>>
>>>
>>>
>>> --
>>> -- Passos
>>>
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> <javascript:_e(%7B%7D,'cvml','aerogear-dev at lists.jboss.org');>
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>
>>
>>
>> --
>> Matthias Wessendorf
>>
>> blog: http://matthiaswessendorf.wordpress.com/
>> sessions: http://www.slideshare.net/mwessendorf
>> twitter: http://twitter.com/mwessendorf
>>  _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> <javascript:_e(%7B%7D,'cvml','aerogear-dev at lists.jboss.org');>
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> <javascript:_e(%7B%7D,'cvml','aerogear-dev at lists.jboss.org');>
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>


-- 
Sent from Gmail Mobile
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150624/88b48592/attachment.html 

From matzew at apache.org  Thu Jun 25 05:43:16 2015
From: matzew at apache.org (Matthias Wessendorf)
Date: Thu, 25 Jun 2015 11:43:16 +0200
Subject: [aerogear-dev] UPS Console:
Message-ID: <CAAg5f2SoK5e176ZvJdGucKL1c0UAqc0PvNOJm=neU7Mfp7RghA@mail.gmail.com>

We used to show the client identifier header on the UI:
https://aerogear.org/docs/unifiedpush/ups_userguide//img/dashboard_activity_full_message.png

Looking at the "Activity Log" tab of a PushApplication, I am no longer
seeing that. I think it would be nice to have that being included in the
table ?

-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150625/80d0ab9e/attachment.html 

From agalante at redhat.com  Thu Jun 25 09:23:53 2015
From: agalante at redhat.com (Andres Galante)
Date: Thu, 25 Jun 2015 09:23:53 -0400
Subject: [aerogear-dev] UPS: Wizard usage issue?
In-Reply-To: <CAAg5f2SLoN1KAGqdz2aMw5fgWf2XrXW=cTMde+6xL6XbOkuHZw@mail.gmail.com>
References: <CAAg5f2QSs0VCKcFSwXMzpQ+P-0FwgzNTGVfxTJR95a4-20O8aw@mail.gmail.com>
	<CAD_dpu0gigVyBkfJ8nB+uDO07WbQ8jEX_M1ZeaPd3G=gqM1vow@mail.gmail.com>
	<CADF=h2sRP+1sx8y5ptKBd3qH20rS9JQh-5R5utQrASXasB_OGw@mail.gmail.com>
	<CAAg5f2Roc-DwhZoX=-q56k=65oX2KjQG4WK2b_wMO=5Xa3Ljpg@mail.gmail.com>
	<CAEroY34jecbHWKeB+WJ_YDS6cr1xd=ziNefW2HTMTM89PYzjPw@mail.gmail.com>
	<42439BF5-FE75-4505-9AF0-361B3B6D643B@gmail.com>
	<CAAg5f2SLoN1KAGqdz2aMw5fgWf2XrXW=cTMde+6xL6XbOkuHZw@mail.gmail.com>
Message-ID: <CACAO5hd3KsP90ny9ZGWrEw7O=tKgFBaaViL8LjxHhiD_BCgkhA@mail.gmail.com>

Hi, I did some of thinking about that and tested it with more than one
variant.

The wizard goal is to guide the users take the most basic steps to get push
up and running. We don't want to add more than the absolute necessary.

Having said that we should probably fix the text at step 3 to something
like "...Lets create a variant now, you will be able to crate more later
on..."



On Wed, Jun 24, 2015 at 1:40 PM, Matthias Wessendorf <matzew at apache.org>
wrote:

>
>
> On Wednesday, June 24, 2015, S?bastien Blanc <scm.blanc at gmail.com> wrote:
>
>>
>>
>> Envoy? de mon iPhone
>>
>> Le 24 juin 2015 ? 19:13, Luk?? Fry? <lukas.fryc at gmail.com> a ?crit :
>>
>> +1 agree with Sebi
>>
>> we can add a note that more variants can be added later once the wizard
>> is finished
>>
>> +1 good idea
>>
> like that too
> +1
>
>
>
>>
>>
>> st 24. 6. 2015 v 16:48 odes?latel Matthias Wessendorf <matzew at apache.org>
>> napsal:
>>
>>> Ok, fair enough - I was just wondering, since we discussed that earlier
>>> and I just realized it, while working on the doc
>>>
>>>
>>>
>>> On Wed, Jun 24, 2015 at 4:42 PM, Daniel Passos <dpassos at redhat.com>
>>> wrote:
>>>
>>>> I agree with Sebi. 90% (or more) will add only only variant, anyway I
>>>> can't see any problem in go to the app and add another only (after wizard
>>>> finished)
>>>>
>>>> On Wed, Jun 24, 2015 at 11:30 AM, Sebastien Blanc <scm.blanc at gmail.com>
>>>> wrote:
>>>>
>>>>> I can see the need but honestly I think that 90% of the time when
>>>>> someone sets up a Push Application, he will start with only one variant to
>>>>> test. Then since he already knows how it works, he can add another variant
>>>>> the "raw" way.
>>>>> We could add it but that could happen later (1.2 ?) but that is just
>>>>> my opinion.
>>>>>
>>>>> Sebi
>>>>>
>>>>>
>>>>> On Wed, Jun 24, 2015 at 4:00 PM, Matthias Wessendorf <
>>>>> matzew at apache.org> wrote:
>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> I just noticed (working on the doc) that when clicking through the
>>>>>> wizard, I can only add one variant
>>>>>>
>>>>>> Now, I am wondering if we should update the wizard, so that I can
>>>>>> also add another vairant, inside of the wizard ?
>>>>>>
>>>>>> Or is that something we have done on design? That we just want just
>>>>>> one variant to be created on the wizard - and for a second (and third, etc)
>>>>>> variant, the user must go to the puah-app and add it there ?
>>>>>>
>>>>>> Thanks,
>>>>>> Matze
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Matthias Wessendorf
>>>>>>
>>>>>> blog: http://matthiaswessendorf.wordpress.com/
>>>>>> sessions: http://www.slideshare.net/mwessendorf
>>>>>> twitter: http://twitter.com/mwessendorf
>>>>>>
>>>>>> _______________________________________________
>>>>>> aerogear-dev mailing list
>>>>>> aerogear-dev at lists.jboss.org
>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>>>
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> aerogear-dev mailing list
>>>>> aerogear-dev at lists.jboss.org
>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> -- Passos
>>>>
>>>> _______________________________________________
>>>> aerogear-dev mailing list
>>>> aerogear-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>
>>>
>>>
>>>
>>> --
>>> Matthias Wessendorf
>>>
>>> blog: http://matthiaswessendorf.wordpress.com/
>>> sessions: http://www.slideshare.net/mwessendorf
>>> twitter: http://twitter.com/mwessendorf
>>>  _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>>
>
>
> --
> Sent from Gmail Mobile
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150625/bbdde7e2/attachment-0001.html 

From matzew at apache.org  Thu Jun 25 09:32:41 2015
From: matzew at apache.org (Matthias Wessendorf)
Date: Thu, 25 Jun 2015 15:32:41 +0200
Subject: [aerogear-dev] UPS: Wizard usage issue?
In-Reply-To: <CACAO5hd3KsP90ny9ZGWrEw7O=tKgFBaaViL8LjxHhiD_BCgkhA@mail.gmail.com>
References: <CAAg5f2QSs0VCKcFSwXMzpQ+P-0FwgzNTGVfxTJR95a4-20O8aw@mail.gmail.com>
	<CAD_dpu0gigVyBkfJ8nB+uDO07WbQ8jEX_M1ZeaPd3G=gqM1vow@mail.gmail.com>
	<CADF=h2sRP+1sx8y5ptKBd3qH20rS9JQh-5R5utQrASXasB_OGw@mail.gmail.com>
	<CAAg5f2Roc-DwhZoX=-q56k=65oX2KjQG4WK2b_wMO=5Xa3Ljpg@mail.gmail.com>
	<CAEroY34jecbHWKeB+WJ_YDS6cr1xd=ziNefW2HTMTM89PYzjPw@mail.gmail.com>
	<42439BF5-FE75-4505-9AF0-361B3B6D643B@gmail.com>
	<CAAg5f2SLoN1KAGqdz2aMw5fgWf2XrXW=cTMde+6xL6XbOkuHZw@mail.gmail.com>
	<CACAO5hd3KsP90ny9ZGWrEw7O=tKgFBaaViL8LjxHhiD_BCgkhA@mail.gmail.com>
Message-ID: <CAAg5f2S2YoU32RJCFGH+AygRrsvS3YqwdgjhvddsczvHp5m+JQ@mail.gmail.com>

On Thu, Jun 25, 2015 at 3:23 PM, Andres Galante <agalante at redhat.com> wrote:

> Hi, I did some of thinking about that and tested it with more than one
> variant.
>
> The wizard goal is to guide the users take the most basic steps to get
> push up and running. We don't want to add more than the absolute necessary.
>
> Having said that we should probably fix the text at step 3 to something
> like "...Lets create a variant now, you will be able to crate more later
> on..."
>

that's good call


>
>
>
> On Wed, Jun 24, 2015 at 1:40 PM, Matthias Wessendorf <matzew at apache.org>
> wrote:
>
>>
>>
>> On Wednesday, June 24, 2015, S?bastien Blanc <scm.blanc at gmail.com> wrote:
>>
>>>
>>>
>>> Envoy? de mon iPhone
>>>
>>> Le 24 juin 2015 ? 19:13, Luk?? Fry? <lukas.fryc at gmail.com> a ?crit :
>>>
>>> +1 agree with Sebi
>>>
>>> we can add a note that more variants can be added later once the wizard
>>> is finished
>>>
>>> +1 good idea
>>>
>> like that too
>> +1
>>
>>
>>
>>>
>>>
>>> st 24. 6. 2015 v 16:48 odes?latel Matthias Wessendorf <matzew at apache.org>
>>> napsal:
>>>
>>>> Ok, fair enough - I was just wondering, since we discussed that earlier
>>>> and I just realized it, while working on the doc
>>>>
>>>>
>>>>
>>>> On Wed, Jun 24, 2015 at 4:42 PM, Daniel Passos <dpassos at redhat.com>
>>>> wrote:
>>>>
>>>>> I agree with Sebi. 90% (or more) will add only only variant, anyway I
>>>>> can't see any problem in go to the app and add another only (after wizard
>>>>> finished)
>>>>>
>>>>> On Wed, Jun 24, 2015 at 11:30 AM, Sebastien Blanc <scm.blanc at gmail.com
>>>>> > wrote:
>>>>>
>>>>>> I can see the need but honestly I think that 90% of the time when
>>>>>> someone sets up a Push Application, he will start with only one variant to
>>>>>> test. Then since he already knows how it works, he can add another variant
>>>>>> the "raw" way.
>>>>>> We could add it but that could happen later (1.2 ?) but that is just
>>>>>> my opinion.
>>>>>>
>>>>>> Sebi
>>>>>>
>>>>>>
>>>>>> On Wed, Jun 24, 2015 at 4:00 PM, Matthias Wessendorf <
>>>>>> matzew at apache.org> wrote:
>>>>>>
>>>>>>> Hi,
>>>>>>>
>>>>>>> I just noticed (working on the doc) that when clicking through the
>>>>>>> wizard, I can only add one variant
>>>>>>>
>>>>>>> Now, I am wondering if we should update the wizard, so that I can
>>>>>>> also add another vairant, inside of the wizard ?
>>>>>>>
>>>>>>> Or is that something we have done on design? That we just want just
>>>>>>> one variant to be created on the wizard - and for a second (and third, etc)
>>>>>>> variant, the user must go to the puah-app and add it there ?
>>>>>>>
>>>>>>> Thanks,
>>>>>>> Matze
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Matthias Wessendorf
>>>>>>>
>>>>>>> blog: http://matthiaswessendorf.wordpress.com/
>>>>>>> sessions: http://www.slideshare.net/mwessendorf
>>>>>>> twitter: http://twitter.com/mwessendorf
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> aerogear-dev mailing list
>>>>>>> aerogear-dev at lists.jboss.org
>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>>>>
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> aerogear-dev mailing list
>>>>>> aerogear-dev at lists.jboss.org
>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> -- Passos
>>>>>
>>>>> _______________________________________________
>>>>> aerogear-dev mailing list
>>>>> aerogear-dev at lists.jboss.org
>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Matthias Wessendorf
>>>>
>>>> blog: http://matthiaswessendorf.wordpress.com/
>>>> sessions: http://www.slideshare.net/mwessendorf
>>>> twitter: http://twitter.com/mwessendorf
>>>>  _______________________________________________
>>>> aerogear-dev mailing list
>>>> aerogear-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>>
>>
>>
>> --
>> Sent from Gmail Mobile
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150625/de0fbea0/attachment.html 

From lholmqui at redhat.com  Thu Jun 25 10:13:11 2015
From: lholmqui at redhat.com (Luke Holmquist)
Date: Thu, 25 Jun 2015 10:13:11 -0400
Subject: [aerogear-dev] UPS Endpoint docs
Message-ID: <CALD3Fd3OknGOseDL2a5G_OY8HtLgp4jPBnS-KFN7EWpxU27TEQ@mail.gmail.com>

i remember there was a "readme" that showed the different endpoints on the
UPS and what they expected for payload(on POST, PUT) and what they
returned(format, http status codes)

i can't seem to find it now,  it's possible that it is really out of date,
but i was randomly doing something that this might have helped with

-Luke
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150625/0b11fd2b/attachment.html 

From matzew at apache.org  Thu Jun 25 10:32:08 2015
From: matzew at apache.org (Matthias Wessendorf)
Date: Thu, 25 Jun 2015 16:32:08 +0200
Subject: [aerogear-dev] UPS Endpoint docs
In-Reply-To: <CALD3Fd3OknGOseDL2a5G_OY8HtLgp4jPBnS-KFN7EWpxU27TEQ@mail.gmail.com>
References: <CALD3Fd3OknGOseDL2a5G_OY8HtLgp4jPBnS-KFN7EWpxU27TEQ@mail.gmail.com>
Message-ID: <CAAg5f2RPWkdQALts4P3s5=tS6E5HWbL3thNHv1gdoqYU6daJSA@mail.gmail.com>

public APIs are documented here:
https://aerogear.org/docs/specs/aerogear-unifiedpush-rest/overview-index.html

that said Idel started on Miredoc (see JAX-RS module), after the build
there is sommething on target folder, generated using miredot

On Thu, Jun 25, 2015 at 4:13 PM, Luke Holmquist <lholmqui at redhat.com> wrote:

> i remember there was a "readme" that showed the different endpoints on the
> UPS and what they expected for payload(on POST, PUT) and what they
> returned(format, http status codes)
>
> i can't seem to find it now,  it's possible that it is really out of date,
> but i was randomly doing something that this might have helped with
>
> -Luke
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150625/441fa105/attachment.html 

From edewit at redhat.com  Fri Jun 26 09:18:04 2015
From: edewit at redhat.com (Erik Jan de Wit)
Date: Fri, 26 Jun 2015 15:18:04 +0200
Subject: [aerogear-dev] Cordova plush plugin release
Message-ID: <CAO2B-fb7AOjMn1+xHE0G0tM_oKUe2ozLY6toa4n=VK4nB1cg_w@mail.gmail.com>

We are pleased to announce that version 2.0.0 of the cordova push plugin
has been release.  Here is what has been updated:

Bug

   - [AGCORDOVA-36 <https://issues.jboss.org/browse/AGCORDOVA-36>] - Make
   Push Plugin work again with Android < 4.4
   - [AGCORDOVA-38 <https://issues.jboss.org/browse/AGCORDOVA-38>] -
   Authorisation error iOS is to big
   - [AGCORDOVA-43 <https://issues.jboss.org/browse/AGCORDOVA-43>] -
   cordova android app in the background crashes when a notification arrives
   - [AGCORDOVA-47 <https://issues.jboss.org/browse/AGCORDOVA-47>] -
   Windows push registration done called to soon
   - [AGCORDOVA-48 <https://issues.jboss.org/browse/AGCORDOVA-48>] - No
   alert in notification area when app is in background
   - [AGCORDOVA-53 <https://issues.jboss.org/browse/AGCORDOVA-53>] - New
   push channel id on windows throws exception
   - [AGCORDOVA-94 <https://issues.jboss.org/browse/AGCORDOVA-94>] -
   Foreground is always true on Android

Enhancement

   - [AGCORDOVA-92 <https://issues.jboss.org/browse/AGCORDOVA-92>] - Remove
   use of deprecated sendJavascript method

Feature Request

   - [AGCORDOVA-24 <https://issues.jboss.org/browse/AGCORDOVA-24>] -
   Windows/WNS support for cordova-push library
   - [AGCORDOVA-83 <https://issues.jboss.org/browse/AGCORDOVA-83>] - Change
   plugins namespace to include AG
   - [AGCORDOVA-103 <https://issues.jboss.org/browse/AGCORDOVA-103>] - Push
   Plugin Doc does not talk about JSON config file
   - [AGCORDOVA-106 <https://issues.jboss.org/browse/AGCORDOVA-106>] - with
   iOS 8.0 the 'alert' no longer just a string


-- 
Cheers,
       Erik Jan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150626/2bdfdadb/attachment-0001.html 

From supittma at redhat.com  Fri Jun 26 09:50:52 2015
From: supittma at redhat.com (Summers Pittman)
Date: Fri, 26 Jun 2015 09:50:52 -0400
Subject: [aerogear-dev] [Aerogear-users] Cordova plush plugin release
In-Reply-To: <CAO2B-fb7AOjMn1+xHE0G0tM_oKUe2ozLY6toa4n=VK4nB1cg_w@mail.gmail.com>
References: <CAO2B-fb7AOjMn1+xHE0G0tM_oKUe2ozLY6toa4n=VK4nB1cg_w@mail.gmail.com>
Message-ID: <CAEQz2CuQdUcDXw2iT1kU3-hOdpw3w9N9fsEmiYZE0bhH-2A_-g@mail.gmail.com>

W00t!

On Fri, Jun 26, 2015 at 9:18 AM, Erik Jan de Wit <edewit at redhat.com> wrote:

> We are pleased to announce that version 2.0.0 of the cordova push plugin
> has been release.  Here is what has been updated:
>
> Bug
>
>    - [AGCORDOVA-36 <https://issues.jboss.org/browse/AGCORDOVA-36>] - Make
>    Push Plugin work again with Android < 4.4
>    - [AGCORDOVA-38 <https://issues.jboss.org/browse/AGCORDOVA-38>] -
>    Authorisation error iOS is to big
>    - [AGCORDOVA-43 <https://issues.jboss.org/browse/AGCORDOVA-43>] -
>    cordova android app in the background crashes when a notification arrives
>    - [AGCORDOVA-47 <https://issues.jboss.org/browse/AGCORDOVA-47>] -
>    Windows push registration done called to soon
>    - [AGCORDOVA-48 <https://issues.jboss.org/browse/AGCORDOVA-48>] - No
>    alert in notification area when app is in background
>    - [AGCORDOVA-53 <https://issues.jboss.org/browse/AGCORDOVA-53>] - New
>    push channel id on windows throws exception
>    - [AGCORDOVA-94 <https://issues.jboss.org/browse/AGCORDOVA-94>] -
>    Foreground is always true on Android
>
> Enhancement
>
>    - [AGCORDOVA-92 <https://issues.jboss.org/browse/AGCORDOVA-92>] -
>    Remove use of deprecated sendJavascript method
>
> Feature Request
>
>    - [AGCORDOVA-24 <https://issues.jboss.org/browse/AGCORDOVA-24>] -
>    Windows/WNS support for cordova-push library
>    - [AGCORDOVA-83 <https://issues.jboss.org/browse/AGCORDOVA-83>] -
>    Change plugins namespace to include AG
>    - [AGCORDOVA-103 <https://issues.jboss.org/browse/AGCORDOVA-103>] -
>    Push Plugin Doc does not talk about JSON config file
>    - [AGCORDOVA-106 <https://issues.jboss.org/browse/AGCORDOVA-106>] -
>    with iOS 8.0 the 'alert' no longer just a string
>
>
> --
> Cheers,
>        Erik Jan
>
> _______________________________________________
> Aerogear-users mailing list
> Aerogear-users at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-users
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150626/20ace779/attachment.html 

From dpassos at redhat.com  Fri Jun 26 10:32:16 2015
From: dpassos at redhat.com (Daniel Passos)
Date: Fri, 26 Jun 2015 11:32:16 -0300
Subject: [aerogear-dev] AeroGear Android Push 2.2.0
In-Reply-To: <CAAg5f2SUWrymfpku8_dspD5zrN4QWj8xD7LMRJy111K_1FX2Ug@mail.gmail.com>
References: <CADF=h2vVgw1UUGXHs+x=4zr12ZnC9Q=iAuw1z+OtVGQDtO=LFA@mail.gmail.com>
	<CAAg5f2QcCaXJjNUgjG3BmGuPDkRbzVx75EAYJ2rVErZiifMx=g@mail.gmail.com>
	<CADF=h2vO6zErixrULXSim_-PGTQaFcRsJ=y4n3BfJa5VreQZwg@mail.gmail.com>
	<CAD_dpu2u8iENYLASAOAD-EmmQp-nhT0qgCxt8sfvrxjr5y0v+w@mail.gmail.com>
	<CAEQz2Ctkv3AMQbSgbKu8Ugy8WbGY9o44E6xa22TEX8Jyenaxmg@mail.gmail.com>
	<CADF=h2u0kc8d9O93VqHSWazqWtGOQ=Acb=AaOrByYW+d7rNY0g@mail.gmail.com>
	<CADF=h2tm7Ccrdhrje3NhW7XshXiREq=uRdKE3wqbCQNiNP1wFA@mail.gmail.com>
	<CAAg5f2S8O-OQXJHW1LEUZEiF7_CUPXtNvK31=SCnXav2oNSyXA@mail.gmail.com>
	<CADF=h2tAqSZvdobU_6Kg1U2N7cc6h=-MMxKww3tjCxmQo+YnsA@mail.gmail.com>
	<CAAg5f2S6+q7g=rc7KXne3tnDOhC725peG5e-Nsm3osZdDxkX+A@mail.gmail.com>
	<CAAg5f2SUWrymfpku8_dspD5zrN4QWj8xD7LMRJy111K_1FX2Ug@mail.gmail.com>
Message-ID: <CADF=h2s58esgHs7eR_YLi7CsuYNS1isRoe+nf31kX8Bn7VoDTA@mail.gmail.com>

Released and available on maven central[1] \o/

[1]
http://search.maven.org/#artifactdetails|org.jboss.aerogear|aerogear-android-push|2.2.0|aar

On Tue, Jun 23, 2015 at 1:59 PM, Matthias Wessendorf <matzew at apache.org>
wrote:

> Actually - this makes the TAG unusable :-)
>
> The tests are not compinging, since pointing to the -SNAPSHOT version of
> the actual push lib, here:
>
> https://github.com/aerogear/aerogear-android-push/blob/2.2.0/aerogear-android-push-test/pom.xml#L50
>
> Changing that to 2.2.0 makes it work.
>
> Again, not a show stopper, but something nice to have e.g. for 2.3.0
>
>
> +1 on the release
>
>
> On Tue, Jun 23, 2015 at 6:53 PM, Matthias Wessendorf <matzew at apache.org>
> wrote:
>
>> ah, I thought it would be still make sense to update the version there :-)
>>
>> That's not a blocker ;-) Just noticed
>>
>> On Tue, Jun 23, 2015 at 6:49 PM, Daniel Passos <dpassos at redhat.com>
>> wrote:
>>
>>> Because test is not part of the release.
>>>
>>> On Tue, Jun 23, 2015 at 12:52 PM, Matthias Wessendorf <matzew at apache.org
>>> > wrote:
>>>
>>>> this pom.xml, on the 2.2.0 tag has incorrect version nr:
>>>> https://github.com/aerogear/aerogear-android-push/blob/2.2.0/aerogear-android-push-test/pom.xml#L29
>>>>
>>>>
>>>> On Fri, Jun 19, 2015 at 12:53 AM, Daniel Passos <dpassos at redhat.com>
>>>> wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> I've staged[1] the Push library 2.2.0 again and send a PR for
>>>>> UnifiedPush helloworld[2] using it.
>>>>>
>>>>> We?re planning to release it next Wednesday
>>>>>
>>>>> Fell free to test it and let us know if you find any issues.
>>>>> [1]
>>>>> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-5856/
>>>>> [2] https://github.com/jboss-mobile/unified-push-helloworld/pull/15
>>>>>
>>>>>
>>>>> On Wed, Jun 17, 2015 at 10:36 PM, Daniel Passos <dpassos at redhat.com>
>>>>> wrote:
>>>>>
>>>>>> Hey Guys,
>>>>>>
>>>>>> We are postpone it to fix the bug Matthias found. I just send a PR[1]
>>>>>> to fix it.
>>>>>>
>>>>>> [1] https://github.com/aerogear/aerogear-android-push/pull/38
>>>>>>
>>>>>> On Wed, Jun 17, 2015 at 11:32 AM, Summers Pittman <
>>>>>> supittma at redhat.com> wrote:
>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Wed, Jun 17, 2015 at 3:17 AM, Sebastien Blanc <
>>>>>>> scm.blanc at gmail.com> wrote:
>>>>>>>
>>>>>>>> This fix is more a workaround since it was not needed with the
>>>>>>>> previous versions.  so we need to be sure to check if :
>>>>>>>>
>>>>>>> No.  The hello world app is broken.
>>>>>>>
>>>>>>>>
>>>>>>>> - This fix was needed because of other commits on the helloworld
>>>>>>>>
>>>>>>> - This fix was needed because of the new version of the library
>>>>>>>> - This fix was needed because of a change from GCM server
>>>>>>>> - This fix was needed because of a mix/combination of all the
>>>>>>>> previous potential causes
>>>>>>>>
>>>>>>>
>>>>>>> TL;DR: We never needed information from the PushRegistrar to handle
>>>>>>> messages until metrics were added.  Now we do.  However, if the app is
>>>>>>> garbage collected then the registration information is cleared from memory
>>>>>>> (it is persisted on the device of course).  Because the notification
>>>>>>> handler is invoked by android it bypasses the RegisterActivity.  When we
>>>>>>> try to fetch the registration information to send the metric message it
>>>>>>> isn't loaded and the NPE is thrown.  Previously had enabled the ability to
>>>>>>> unregister the client from the message list screen we would have seen
>>>>>>> similar results.
>>>>>>>
>>>>>>> The application work by happy coincidence.  It wasn't until matz
>>>>>>> tested on a hellishly obsolete device that the issue appeared. ;)
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> Passos have you been able to test the lib with Aerodoc ?
>>>>>>>>
>>>>>>>> Sebi
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> On Tue, Jun 16, 2015 at 4:50 PM, Daniel Passos <dpassos at redhat.com>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> Seems the problem was in the app not in the library. For more
>>>>>>>>> details please see my comment[1] in Jira and the fix in this PR[2]
>>>>>>>>>
>>>>>>>>> [1]
>>>>>>>>> https://issues.jboss.org/browse/AGDROID-425?focusedCommentId=13079805&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13079805
>>>>>>>>> [2]
>>>>>>>>> https://github.com/jboss-mobile/unified-push-helloworld/pull/14
>>>>>>>>>
>>>>>>>>> On Mon, Jun 15, 2015 at 9:42 AM, Matthias Wessendorf <
>>>>>>>>> matzew at apache.org> wrote:
>>>>>>>>>
>>>>>>>>>> I noticed a little bug w/ the current libray
>>>>>>>>>>
>>>>>>>>>> https://issues.jboss.org/browse/AGDROID-425
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On Mon, Jun 15, 2015 at 2:42 AM, Daniel Passos <
>>>>>>>>>> dpassos at redhat.com> wrote:
>>>>>>>>>>
>>>>>>>>>>> Hey Everyone,
>>>>>>>>>>>
>>>>>>>>>>> We are ready to release AeroGear Android Push 2.2.0, we
>>>>>>>>>>> staged[1] it on Nexus.
>>>>>>>>>>>
>>>>>>>>>>> What is new in this version?
>>>>>>>>>>>
>>>>>>>>>>>    - AGDROID-422 <https://issues.jboss.org/browse/AGDROID-422>
>>>>>>>>>>>    - Add support for push-config.json for Android Push SDK
>>>>>>>>>>>    - AGDROID-423 <https://issues.jboss.org/browse/AGDROID-423>
>>>>>>>>>>>    - Android SDK hook for notifying the server if app has been opened due to a
>>>>>>>>>>>    push
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> We?re planning to release it next Thursday.
>>>>>>>>>>>
>>>>>>>>>>> Fell free to test it and let us know if you find any issues.
>>>>>>>>>>>
>>>>>>>>>>> [1]
>>>>>>>>>>> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-5783/
>>>>>>>>>>> ?
>>>>>>>>>>> --
>>>>>>>>>>> -- Passos
>>>>>>>>>>>
>>>>>>>>>>> _______________________________________________
>>>>>>>>>>> aerogear-dev mailing list
>>>>>>>>>>> aerogear-dev at lists.jboss.org
>>>>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> Matthias Wessendorf
>>>>>>>>>>
>>>>>>>>>> blog: http://matthiaswessendorf.wordpress.com/
>>>>>>>>>> sessions: http://www.slideshare.net/mwessendorf
>>>>>>>>>> twitter: http://twitter.com/mwessendorf
>>>>>>>>>>
>>>>>>>>>> _______________________________________________
>>>>>>>>>> aerogear-dev mailing list
>>>>>>>>>> aerogear-dev at lists.jboss.org
>>>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> -- Passos
>>>>>>>>>
>>>>>>>>> _______________________________________________
>>>>>>>>> aerogear-dev mailing list
>>>>>>>>> aerogear-dev at lists.jboss.org
>>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> _______________________________________________
>>>>>>>> aerogear-dev mailing list
>>>>>>>> aerogear-dev at lists.jboss.org
>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> aerogear-dev mailing list
>>>>>>> aerogear-dev at lists.jboss.org
>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> -- Passos
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> -- Passos
>>>>>
>>>>> _______________________________________________
>>>>> aerogear-dev mailing list
>>>>> aerogear-dev at lists.jboss.org
>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Matthias Wessendorf
>>>>
>>>> blog: http://matthiaswessendorf.wordpress.com/
>>>> sessions: http://www.slideshare.net/mwessendorf
>>>> twitter: http://twitter.com/mwessendorf
>>>>
>>>> _______________________________________________
>>>> aerogear-dev mailing list
>>>> aerogear-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>
>>>
>>>
>>>
>>> --
>>> -- Passos
>>>
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>
>>
>>
>> --
>> Matthias Wessendorf
>>
>> blog: http://matthiaswessendorf.wordpress.com/
>> sessions: http://www.slideshare.net/mwessendorf
>> twitter: http://twitter.com/mwessendorf
>>
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 
-- Passos
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150626/fdc469ac/attachment-0001.html 

From idel.pivnitskiy at gmail.com  Fri Jun 26 17:30:33 2015
From: idel.pivnitskiy at gmail.com (Idel Pivnitskiy)
Date: Sat, 27 Jun 2015 00:30:33 +0300
Subject: [aerogear-dev] [GSoC] WebPush Server updates
Message-ID: <CAN+BUJrNhS_DcB12fV63305Vq5Stb0nwfaLx+BSwGr80cWHaiw@mail.gmail.com>

Hi all!

I want to tell about my work on WebPush Server. I have 3 completed tasks:

1. Done some performance improvements and code clean up [1]. They are not
significant, but helped me to understand project code base better.
2. Updated Netty to the latest released beta version, which implements
http2-draft-17 [2]. Update wasn't be very simple, because this version has
significant changes of Netty http2-codec.
3. Removed usage of deprecated API of Netty SSL codec [3].

This month Kit Cambridge, who works on Node.js implementation of WebPush
server, updated our webpush console [4] to support the latest version of
WebPush protocol draft [5].

And I'm working on changes of WebPush server now. Here is my developing
branch [6]. The latest draft of WebPush protocol has too many changes. I
have implemented new subscription API, but pushes doesn't work now. When
all will be done, I'll squash all commits and send a new PR.

[1] https://github.com/aerogear/aerogear-webpush-server/pull/10
[2] https://github.com/aerogear/aerogear-webpush-server/pull/12
[3] https://github.com/aerogear/aerogear-webpush-server/pull/13
[4] https://github.com/aerogear/aerogear-webpush-server/pull/11
[5] https://www.ietf.org/id/draft-thomson-webpush-protocol-00.txt
[6]
https://github.com/idelpivnitskiy/aerogear-webpush-server/tree/draft-thomson-webpush-protocol-00

Best regards,
Idel Pivnitskiy
--
E-mail: Idel.Pivnitskiy at gmail.com
Twitter: @idelpivnitskiy <https://twitter.com/idelpivnitskiy>
GitHub: @idelpivnitskiy <https://github.com/idelpivnitskiy>



--
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150627/116a04df/attachment.html 

From daniel.bevenius at gmail.com  Sat Jun 27 02:46:43 2015
From: daniel.bevenius at gmail.com (Daniel Bevenius)
Date: Sat, 27 Jun 2015 08:46:43 +0200
Subject: [aerogear-dev] [GSoC] WebPush Server updates
In-Reply-To: <CAN+BUJrNhS_DcB12fV63305Vq5Stb0nwfaLx+BSwGr80cWHaiw@mail.gmail.com>
References: <CAN+BUJrNhS_DcB12fV63305Vq5Stb0nwfaLx+BSwGr80cWHaiw@mail.gmail.com>
Message-ID: <CAFJm-3HuTT+q9D4m_5W0RYdspZc6X=9Fj-rp8nSF-OiNm9MKMw@mail.gmail.com>

Thanks for the update!
Looking forward to seeing your updates and catching up on the latest
WebPush draft.

/Dan

On 26 June 2015 at 23:30, Idel Pivnitskiy <idel.pivnitskiy at gmail.com> wrote:

> Hi all!
>
> I want to tell about my work on WebPush Server. I have 3 completed tasks:
>
> 1. Done some performance improvements and code clean up [1]. They are not
> significant, but helped me to understand project code base better.
> 2. Updated Netty to the latest released beta version, which implements
> http2-draft-17 [2]. Update wasn't be very simple, because this version has
> significant changes of Netty http2-codec.
> 3. Removed usage of deprecated API of Netty SSL codec [3].
>
> This month Kit Cambridge, who works on Node.js implementation of WebPush
> server, updated our webpush console [4] to support the latest version of
> WebPush protocol draft [5].
>
> And I'm working on changes of WebPush server now. Here is my developing
> branch [6]. The latest draft of WebPush protocol has too many changes. I
> have implemented new subscription API, but pushes doesn't work now. When
> all will be done, I'll squash all commits and send a new PR.
>
> [1] https://github.com/aerogear/aerogear-webpush-server/pull/10
> [2] https://github.com/aerogear/aerogear-webpush-server/pull/12
> [3] https://github.com/aerogear/aerogear-webpush-server/pull/13
> [4] https://github.com/aerogear/aerogear-webpush-server/pull/11
> [5] https://www.ietf.org/id/draft-thomson-webpush-protocol-00.txt
> [6]
> https://github.com/idelpivnitskiy/aerogear-webpush-server/tree/draft-thomson-webpush-protocol-00
>
> Best regards,
> Idel Pivnitskiy
> --
> E-mail: Idel.Pivnitskiy at gmail.com
> Twitter: @idelpivnitskiy <https://twitter.com/idelpivnitskiy>
> GitHub: @idelpivnitskiy <https://github.com/idelpivnitskiy>
>
>
>
> --
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150627/3d1f5a01/attachment.html 

From agalante at redhat.com  Mon Jun 29 08:19:58 2015
From: agalante at redhat.com (Andres Galante)
Date: Mon, 29 Jun 2015 09:19:58 -0300
Subject: [aerogear-dev] UPS: Console - Visibility issues
In-Reply-To: <CAEroY369GzXXTeAPyDsY=x3_zC_5iOF=9_p+xHmvcBQF3LUzOg@mail.gmail.com>
References: <CAAg5f2SF6bo8yuhj5gvdx6prY8Srreevrqp2XKLVNsmFne-+aQ@mail.gmail.com>
	<CAEroY369GzXXTeAPyDsY=x3_zC_5iOF=9_p+xHmvcBQF3LUzOg@mail.gmail.com>
Message-ID: <CACAO5hcUBxTdEhrkQzXYBvzE1keoBYWRQdy5GH3azTMkziJG2w@mail.gmail.com>

Hi Matthias and Lukas,

During the user research time I've learn that there are almost none use
case where the user uses this information stand alone. The user would just
copy and paste the code snippet.

We use it a lot because we test it and set it up a bunch of times UPS. We
already have the code set up and we end up knowing where to look for the
data. Luke bring this same issue to me during Summit.

Let me think of a good way to highlight that information to make the expert
user life easier.



On Wed, Jun 24, 2015 at 2:12 PM, Luk?? Fry? <lukas at fryc.eu> wrote:

> Basically it is something that we "agreed on" (or rather didn't catch)
> during mockup reviews and that never changed from that time.
>
> @Andres: did it have some reason to hide the details?
>
> I'm all for exposing it more visibly.
>
> st 24. 6. 2015 v 17:21 odes?latel Matthias Wessendorf <matzew at apache.org>
> napsal:
>
>> Hi,
>>
>> on our old design the PushApplicationID/MasterSecret was very good to
>> notice:
>>
>> https://aerogear.org/docs/unifiedpush/ups_userguide//img/applications_variant.png
>>
>> Now it's a bit more hidden (one has to click on the "Sender API" tab of
>> the Application).
>>
>> Similar w/ the VariantID/Secret pair, IMO it is also a bit hidden, since
>> this is only visible in the source snippets for the variant.
>>
>> They used to be a bit more present:
>>
>> https://aerogear.org/docs/unifiedpush/ups_userguide//img/applications_variant_details.png
>>
>> Since I find that suboptimal, I am wondering if that's done for a good
>> reason, or if something (in a future version?) should be changed ?
>>
>> -M
>>
>> --
>> Matthias Wessendorf
>>
>> blog: http://matthiaswessendorf.wordpress.com/
>> sessions: http://www.slideshare.net/mwessendorf
>> twitter: http://twitter.com/mwessendorf
>>  _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150629/04c36f6c/attachment.html 

From agalante at redhat.com  Mon Jun 29 08:27:29 2015
From: agalante at redhat.com (Andres Galante)
Date: Mon, 29 Jun 2015 09:27:29 -0300
Subject: [aerogear-dev] UPS Console:
In-Reply-To: <CAAg5f2SoK5e176ZvJdGucKL1c0UAqc0PvNOJm=neU7Mfp7RghA@mail.gmail.com>
References: <CAAg5f2SoK5e176ZvJdGucKL1c0UAqc0PvNOJm=neU7Mfp7RghA@mail.gmail.com>
Message-ID: <CACAO5hcDOGY=vLmzLdLJuhmH=8dNsSJgRX7HPk_3H2Qn8Fu+ZA@mail.gmail.com>

Lukas, I think the interaction was ok as it was, can we add this in a modal?

On Thu, Jun 25, 2015 at 6:43 AM, Matthias Wessendorf <matzew at apache.org>
wrote:

> We used to show the client identifier header on the UI:
>
> https://aerogear.org/docs/unifiedpush/ups_userguide//img/dashboard_activity_full_message.png
>
> Looking at the "Activity Log" tab of a PushApplication, I am no longer
> seeing that. I think it would be nice to have that being included in the
> table ?
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150629/ae0b953a/attachment.html 

From matzew at apache.org  Mon Jun 29 08:58:04 2015
From: matzew at apache.org (Matthias Wessendorf)
Date: Mon, 29 Jun 2015 14:58:04 +0200
Subject: [aerogear-dev] UPS: Console - Visibility issues
In-Reply-To: <CACAO5hcUBxTdEhrkQzXYBvzE1keoBYWRQdy5GH3azTMkziJG2w@mail.gmail.com>
References: <CAAg5f2SF6bo8yuhj5gvdx6prY8Srreevrqp2XKLVNsmFne-+aQ@mail.gmail.com>
	<CAEroY369GzXXTeAPyDsY=x3_zC_5iOF=9_p+xHmvcBQF3LUzOg@mail.gmail.com>
	<CACAO5hcUBxTdEhrkQzXYBvzE1keoBYWRQdy5GH3azTMkziJG2w@mail.gmail.com>
Message-ID: <CAAg5f2R4eNW8XWEbMO7BB3rmN9F_e55mPv2MiEeBwN-k937t_w@mail.gmail.com>

On Mon, Jun 29, 2015 at 2:19 PM, Andres Galante <agalante at redhat.com> wrote:

> Hi Matthias and Lukas,
>
> During the user research time I've learn that there are almost none use
> case where the user uses this information stand alone. The user would just
> copy and paste the code snippet.
>

well, that does not always work (e.g. sligthly different structure of code).
Even our own Android HelloWorld Demo is not able to use the snippets and
paste them in (due to different code structure - which is good).

Having them visible give a bit more appreciation to these IDs (or call em
API keys), so it's easy to get the desired info quickly




>
> We use it a lot because we test it and set it up a bunch of times UPS. We
> already have the code set up and we end up knowing where to look for the
> data. Luke bring this same issue to me during Summit.
>
> Let me think of a good way to highlight that information to make the
> expert user life easier.
>
>
>
> On Wed, Jun 24, 2015 at 2:12 PM, Luk?? Fry? <lukas at fryc.eu> wrote:
>
>> Basically it is something that we "agreed on" (or rather didn't catch)
>> during mockup reviews and that never changed from that time.
>>
>> @Andres: did it have some reason to hide the details?
>>
>> I'm all for exposing it more visibly.
>>
>> st 24. 6. 2015 v 17:21 odes?latel Matthias Wessendorf <matzew at apache.org>
>> napsal:
>>
>>> Hi,
>>>
>>> on our old design the PushApplicationID/MasterSecret was very good to
>>> notice:
>>>
>>> https://aerogear.org/docs/unifiedpush/ups_userguide//img/applications_variant.png
>>>
>>> Now it's a bit more hidden (one has to click on the "Sender API" tab of
>>> the Application).
>>>
>>> Similar w/ the VariantID/Secret pair, IMO it is also a bit hidden, since
>>> this is only visible in the source snippets for the variant.
>>>
>>> They used to be a bit more present:
>>>
>>> https://aerogear.org/docs/unifiedpush/ups_userguide//img/applications_variant_details.png
>>>
>>> Since I find that suboptimal, I am wondering if that's done for a good
>>> reason, or if something (in a future version?) should be changed ?
>>>
>>> -M
>>>
>>> --
>>> Matthias Wessendorf
>>>
>>> blog: http://matthiaswessendorf.wordpress.com/
>>> sessions: http://www.slideshare.net/mwessendorf
>>> twitter: http://twitter.com/mwessendorf
>>>  _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150629/ea50906d/attachment-0001.html 

From matzew at apache.org  Mon Jun 29 08:59:01 2015
From: matzew at apache.org (Matthias Wessendorf)
Date: Mon, 29 Jun 2015 14:59:01 +0200
Subject: [aerogear-dev] UPS Console:
In-Reply-To: <CACAO5hcDOGY=vLmzLdLJuhmH=8dNsSJgRX7HPk_3H2Qn8Fu+ZA@mail.gmail.com>
References: <CAAg5f2SoK5e176ZvJdGucKL1c0UAqc0PvNOJm=neU7Mfp7RghA@mail.gmail.com>
	<CACAO5hcDOGY=vLmzLdLJuhmH=8dNsSJgRX7HPk_3H2Qn8Fu+ZA@mail.gmail.com>
Message-ID: <CAAg5f2QTFSnRJh2jJRG9k8d21EYW54TJ16Z2QMY2R=wYfGv0oQ@mail.gmail.com>

Not following :-)

On Mon, Jun 29, 2015 at 2:27 PM, Andres Galante <agalante at redhat.com> wrote:

> Lukas, I think the interaction was ok as it was, can we add this in a
> modal?
>
> On Thu, Jun 25, 2015 at 6:43 AM, Matthias Wessendorf <matzew at apache.org>
> wrote:
>
>> We used to show the client identifier header on the UI:
>>
>> https://aerogear.org/docs/unifiedpush/ups_userguide//img/dashboard_activity_full_message.png
>>
>> Looking at the "Activity Log" tab of a PushApplication, I am no longer
>> seeing that. I think it would be nice to have that being included in the
>> table ?
>>
>> --
>> Matthias Wessendorf
>>
>> blog: http://matthiaswessendorf.wordpress.com/
>> sessions: http://www.slideshare.net/mwessendorf
>> twitter: http://twitter.com/mwessendorf
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150629/092f64bc/attachment.html 

From scm.blanc at gmail.com  Mon Jun 29 09:05:01 2015
From: scm.blanc at gmail.com (Sebastien Blanc)
Date: Mon, 29 Jun 2015 15:05:01 +0200
Subject: [aerogear-dev] UPS: Console - Visibility issues
In-Reply-To: <CAAg5f2R4eNW8XWEbMO7BB3rmN9F_e55mPv2MiEeBwN-k937t_w@mail.gmail.com>
References: <CAAg5f2SF6bo8yuhj5gvdx6prY8Srreevrqp2XKLVNsmFne-+aQ@mail.gmail.com>
	<CAEroY369GzXXTeAPyDsY=x3_zC_5iOF=9_p+xHmvcBQF3LUzOg@mail.gmail.com>
	<CACAO5hcUBxTdEhrkQzXYBvzE1keoBYWRQdy5GH3azTMkziJG2w@mail.gmail.com>
	<CAAg5f2R4eNW8XWEbMO7BB3rmN9F_e55mPv2MiEeBwN-k937t_w@mail.gmail.com>
Message-ID: <CAD_dpu3=S2jL2rxQ5gaCHbVG4oy5+eeQXrnrRzy2H6_Hq4rixg@mail.gmail.com>

I would vote to have them along with the other variant details that are
already shown (like google's project number etc ...)


On Mon, Jun 29, 2015 at 2:58 PM, Matthias Wessendorf <matzew at apache.org>
wrote:

>
>
> On Mon, Jun 29, 2015 at 2:19 PM, Andres Galante <agalante at redhat.com>
> wrote:
>
>> Hi Matthias and Lukas,
>>
>> During the user research time I've learn that there are almost none use
>> case where the user uses this information stand alone. The user would just
>> copy and paste the code snippet.
>>
>
> well, that does not always work (e.g. sligthly different structure of
> code).
> Even our own Android HelloWorld Demo is not able to use the snippets and
> paste them in (due to different code structure - which is good).
>
> Having them visible give a bit more appreciation to these IDs (or call em
> API keys), so it's easy to get the desired info quickly
>
>
>
>
>>
>> We use it a lot because we test it and set it up a bunch of times UPS. We
>> already have the code set up and we end up knowing where to look for the
>> data. Luke bring this same issue to me during Summit.
>>
>> Let me think of a good way to highlight that information to make the
>> expert user life easier.
>>
>>
>>
>> On Wed, Jun 24, 2015 at 2:12 PM, Luk?? Fry? <lukas at fryc.eu> wrote:
>>
>>> Basically it is something that we "agreed on" (or rather didn't catch)
>>> during mockup reviews and that never changed from that time.
>>>
>>> @Andres: did it have some reason to hide the details?
>>>
>>> I'm all for exposing it more visibly.
>>>
>>> st 24. 6. 2015 v 17:21 odes?latel Matthias Wessendorf <matzew at apache.org>
>>> napsal:
>>>
>>>> Hi,
>>>>
>>>> on our old design the PushApplicationID/MasterSecret was very good to
>>>> notice:
>>>>
>>>> https://aerogear.org/docs/unifiedpush/ups_userguide//img/applications_variant.png
>>>>
>>>> Now it's a bit more hidden (one has to click on the "Sender API" tab of
>>>> the Application).
>>>>
>>>> Similar w/ the VariantID/Secret pair, IMO it is also a bit hidden,
>>>> since this is only visible in the source snippets for the variant.
>>>>
>>>> They used to be a bit more present:
>>>>
>>>> https://aerogear.org/docs/unifiedpush/ups_userguide//img/applications_variant_details.png
>>>>
>>>> Since I find that suboptimal, I am wondering if that's done for a good
>>>> reason, or if something (in a future version?) should be changed ?
>>>>
>>>> -M
>>>>
>>>> --
>>>> Matthias Wessendorf
>>>>
>>>> blog: http://matthiaswessendorf.wordpress.com/
>>>> sessions: http://www.slideshare.net/mwessendorf
>>>> twitter: http://twitter.com/mwessendorf
>>>>  _______________________________________________
>>>> aerogear-dev mailing list
>>>> aerogear-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>>
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150629/2e27fb37/attachment.html 

From agalante at redhat.com  Mon Jun 29 09:10:20 2015
From: agalante at redhat.com (Andres Galante)
Date: Mon, 29 Jun 2015 10:10:20 -0300
Subject: [aerogear-dev] UPS: Console - Visibility issues
In-Reply-To: <CAD_dpu3=S2jL2rxQ5gaCHbVG4oy5+eeQXrnrRzy2H6_Hq4rixg@mail.gmail.com>
References: <CAAg5f2SF6bo8yuhj5gvdx6prY8Srreevrqp2XKLVNsmFne-+aQ@mail.gmail.com>
	<CAEroY369GzXXTeAPyDsY=x3_zC_5iOF=9_p+xHmvcBQF3LUzOg@mail.gmail.com>
	<CACAO5hcUBxTdEhrkQzXYBvzE1keoBYWRQdy5GH3azTMkziJG2w@mail.gmail.com>
	<CAAg5f2R4eNW8XWEbMO7BB3rmN9F_e55mPv2MiEeBwN-k937t_w@mail.gmail.com>
	<CAD_dpu3=S2jL2rxQ5gaCHbVG4oy5+eeQXrnrRzy2H6_Hq4rixg@mail.gmail.com>
Message-ID: <CACAO5heAnFQvv_1ugSRsGS1Cf5X4dJ80Vi2hZw=LB=7-3jLzaQ@mail.gmail.com>

Good idea Sebastien! That is a good placement. I'll test it and see if we
need a line or something to mark a separation between them and the network
info.

On Mon, Jun 29, 2015 at 10:05 AM, Sebastien Blanc <scm.blanc at gmail.com>
wrote:

> I would vote to have them along with the other variant details that are
> already shown (like google's project number etc ...)
>
>
> On Mon, Jun 29, 2015 at 2:58 PM, Matthias Wessendorf <matzew at apache.org>
> wrote:
>
>>
>>
>> On Mon, Jun 29, 2015 at 2:19 PM, Andres Galante <agalante at redhat.com>
>> wrote:
>>
>>> Hi Matthias and Lukas,
>>>
>>> During the user research time I've learn that there are almost none use
>>> case where the user uses this information stand alone. The user would just
>>> copy and paste the code snippet.
>>>
>>
>> well, that does not always work (e.g. sligthly different structure of
>> code).
>> Even our own Android HelloWorld Demo is not able to use the snippets and
>> paste them in (due to different code structure - which is good).
>>
>> Having them visible give a bit more appreciation to these IDs (or call em
>> API keys), so it's easy to get the desired info quickly
>>
>>
>>
>>
>>>
>>> We use it a lot because we test it and set it up a bunch of times UPS.
>>> We already have the code set up and we end up knowing where to look for the
>>> data. Luke bring this same issue to me during Summit.
>>>
>>> Let me think of a good way to highlight that information to make the
>>> expert user life easier.
>>>
>>>
>>>
>>> On Wed, Jun 24, 2015 at 2:12 PM, Luk?? Fry? <lukas at fryc.eu> wrote:
>>>
>>>> Basically it is something that we "agreed on" (or rather didn't catch)
>>>> during mockup reviews and that never changed from that time.
>>>>
>>>> @Andres: did it have some reason to hide the details?
>>>>
>>>> I'm all for exposing it more visibly.
>>>>
>>>> st 24. 6. 2015 v 17:21 odes?latel Matthias Wessendorf <
>>>> matzew at apache.org> napsal:
>>>>
>>>>> Hi,
>>>>>
>>>>> on our old design the PushApplicationID/MasterSecret was very good to
>>>>> notice:
>>>>>
>>>>> https://aerogear.org/docs/unifiedpush/ups_userguide//img/applications_variant.png
>>>>>
>>>>> Now it's a bit more hidden (one has to click on the "Sender API" tab
>>>>> of the Application).
>>>>>
>>>>> Similar w/ the VariantID/Secret pair, IMO it is also a bit hidden,
>>>>> since this is only visible in the source snippets for the variant.
>>>>>
>>>>> They used to be a bit more present:
>>>>>
>>>>> https://aerogear.org/docs/unifiedpush/ups_userguide//img/applications_variant_details.png
>>>>>
>>>>> Since I find that suboptimal, I am wondering if that's done for a good
>>>>> reason, or if something (in a future version?) should be changed ?
>>>>>
>>>>> -M
>>>>>
>>>>> --
>>>>> Matthias Wessendorf
>>>>>
>>>>> blog: http://matthiaswessendorf.wordpress.com/
>>>>> sessions: http://www.slideshare.net/mwessendorf
>>>>> twitter: http://twitter.com/mwessendorf
>>>>>  _______________________________________________
>>>>> aerogear-dev mailing list
>>>>> aerogear-dev at lists.jboss.org
>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>
>>>>
>>>
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>
>>
>>
>> --
>> Matthias Wessendorf
>>
>> blog: http://matthiaswessendorf.wordpress.com/
>> sessions: http://www.slideshare.net/mwessendorf
>> twitter: http://twitter.com/mwessendorf
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150629/08a45a3a/attachment-0001.html 

From agalante at redhat.com  Mon Jun 29 10:30:03 2015
From: agalante at redhat.com (Andres Galante)
Date: Mon, 29 Jun 2015 11:30:03 -0300
Subject: [aerogear-dev] UPS: Console - Visibility issues
In-Reply-To: <CACAO5heAnFQvv_1ugSRsGS1Cf5X4dJ80Vi2hZw=LB=7-3jLzaQ@mail.gmail.com>
References: <CAAg5f2SF6bo8yuhj5gvdx6prY8Srreevrqp2XKLVNsmFne-+aQ@mail.gmail.com>
	<CAEroY369GzXXTeAPyDsY=x3_zC_5iOF=9_p+xHmvcBQF3LUzOg@mail.gmail.com>
	<CACAO5hcUBxTdEhrkQzXYBvzE1keoBYWRQdy5GH3azTMkziJG2w@mail.gmail.com>
	<CAAg5f2R4eNW8XWEbMO7BB3rmN9F_e55mPv2MiEeBwN-k937t_w@mail.gmail.com>
	<CAD_dpu3=S2jL2rxQ5gaCHbVG4oy5+eeQXrnrRzy2H6_Hq4rixg@mail.gmail.com>
	<CACAO5heAnFQvv_1ugSRsGS1Cf5X4dJ80Vi2hZw=LB=7-3jLzaQ@mail.gmail.com>
Message-ID: <CACAO5hd5JQhQ-M92otQuZK=T8ZuFhqbAnfZsP91JVSEEj9KgsA@mail.gmail.com>

Hi!

To solve the variant information I made this:
https://dl.dropboxusercontent.com/u/4371641/Screen%20Shot%202015-06-29%20at%2011.08.30%20AM.png

But we are already showing the sender info at the sender tab:
https://dl.dropboxusercontent.com/u/4371641/Screen%20Shot%202015-06-29%20at%2011.23.10%20AM.png

What do you think?

Andr?s



On Mon, Jun 29, 2015 at 10:10 AM, Andres Galante <agalante at redhat.com>
wrote:

> Good idea Sebastien! That is a good placement. I'll test it and see if we
> need a line or something to mark a separation between them and the network
> info.
>
> On Mon, Jun 29, 2015 at 10:05 AM, Sebastien Blanc <scm.blanc at gmail.com>
> wrote:
>
>> I would vote to have them along with the other variant details that are
>> already shown (like google's project number etc ...)
>>
>>
>> On Mon, Jun 29, 2015 at 2:58 PM, Matthias Wessendorf <matzew at apache.org>
>> wrote:
>>
>>>
>>>
>>> On Mon, Jun 29, 2015 at 2:19 PM, Andres Galante <agalante at redhat.com>
>>> wrote:
>>>
>>>> Hi Matthias and Lukas,
>>>>
>>>> During the user research time I've learn that there are almost none use
>>>> case where the user uses this information stand alone. The user would just
>>>> copy and paste the code snippet.
>>>>
>>>
>>> well, that does not always work (e.g. sligthly different structure of
>>> code).
>>> Even our own Android HelloWorld Demo is not able to use the snippets and
>>> paste them in (due to different code structure - which is good).
>>>
>>> Having them visible give a bit more appreciation to these IDs (or call
>>> em API keys), so it's easy to get the desired info quickly
>>>
>>>
>>>
>>>
>>>>
>>>> We use it a lot because we test it and set it up a bunch of times UPS.
>>>> We already have the code set up and we end up knowing where to look for the
>>>> data. Luke bring this same issue to me during Summit.
>>>>
>>>> Let me think of a good way to highlight that information to make the
>>>> expert user life easier.
>>>>
>>>>
>>>>
>>>> On Wed, Jun 24, 2015 at 2:12 PM, Luk?? Fry? <lukas at fryc.eu> wrote:
>>>>
>>>>> Basically it is something that we "agreed on" (or rather didn't catch)
>>>>> during mockup reviews and that never changed from that time.
>>>>>
>>>>> @Andres: did it have some reason to hide the details?
>>>>>
>>>>> I'm all for exposing it more visibly.
>>>>>
>>>>> st 24. 6. 2015 v 17:21 odes?latel Matthias Wessendorf <
>>>>> matzew at apache.org> napsal:
>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> on our old design the PushApplicationID/MasterSecret was very good to
>>>>>> notice:
>>>>>>
>>>>>> https://aerogear.org/docs/unifiedpush/ups_userguide//img/applications_variant.png
>>>>>>
>>>>>> Now it's a bit more hidden (one has to click on the "Sender API" tab
>>>>>> of the Application).
>>>>>>
>>>>>> Similar w/ the VariantID/Secret pair, IMO it is also a bit hidden,
>>>>>> since this is only visible in the source snippets for the variant.
>>>>>>
>>>>>> They used to be a bit more present:
>>>>>>
>>>>>> https://aerogear.org/docs/unifiedpush/ups_userguide//img/applications_variant_details.png
>>>>>>
>>>>>> Since I find that suboptimal, I am wondering if that's done for a
>>>>>> good reason, or if something (in a future version?) should be changed ?
>>>>>>
>>>>>> -M
>>>>>>
>>>>>> --
>>>>>> Matthias Wessendorf
>>>>>>
>>>>>> blog: http://matthiaswessendorf.wordpress.com/
>>>>>> sessions: http://www.slideshare.net/mwessendorf
>>>>>> twitter: http://twitter.com/mwessendorf
>>>>>>  _______________________________________________
>>>>>> aerogear-dev mailing list
>>>>>> aerogear-dev at lists.jboss.org
>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>>
>>>>>
>>>>
>>>> _______________________________________________
>>>> aerogear-dev mailing list
>>>> aerogear-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>
>>>
>>>
>>>
>>> --
>>> Matthias Wessendorf
>>>
>>> blog: http://matthiaswessendorf.wordpress.com/
>>> sessions: http://www.slideshare.net/mwessendorf
>>> twitter: http://twitter.com/mwessendorf
>>>
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150629/21987a8a/attachment.html 

From matzew at apache.org  Mon Jun 29 11:03:17 2015
From: matzew at apache.org (Matthias Wessendorf)
Date: Mon, 29 Jun 2015 17:03:17 +0200
Subject: [aerogear-dev] UPS: Console - Visibility issues
In-Reply-To: <CACAO5hd5JQhQ-M92otQuZK=T8ZuFhqbAnfZsP91JVSEEj9KgsA@mail.gmail.com>
References: <CAAg5f2SF6bo8yuhj5gvdx6prY8Srreevrqp2XKLVNsmFne-+aQ@mail.gmail.com>
	<CAEroY369GzXXTeAPyDsY=x3_zC_5iOF=9_p+xHmvcBQF3LUzOg@mail.gmail.com>
	<CACAO5hcUBxTdEhrkQzXYBvzE1keoBYWRQdy5GH3azTMkziJG2w@mail.gmail.com>
	<CAAg5f2R4eNW8XWEbMO7BB3rmN9F_e55mPv2MiEeBwN-k937t_w@mail.gmail.com>
	<CAD_dpu3=S2jL2rxQ5gaCHbVG4oy5+eeQXrnrRzy2H6_Hq4rixg@mail.gmail.com>
	<CACAO5heAnFQvv_1ugSRsGS1Cf5X4dJ80Vi2hZw=LB=7-3jLzaQ@mail.gmail.com>
	<CACAO5hd5JQhQ-M92otQuZK=T8ZuFhqbAnfZsP91JVSEEj9KgsA@mail.gmail.com>
Message-ID: <CAAg5f2SjV8Ag6bv7V7b_OkOyyZwZ4iNHdb46LaLZ2EiUXNr6ZQ@mail.gmail.com>

I like it !

On Mon, Jun 29, 2015 at 4:30 PM, Andres Galante <agalante at redhat.com> wrote:

> Hi!
>
> To solve the variant information I made this:
>
> https://dl.dropboxusercontent.com/u/4371641/Screen%20Shot%202015-06-29%20at%2011.08.30%20AM.png
>
> But we are already showing the sender info at the sender tab:
>
> https://dl.dropboxusercontent.com/u/4371641/Screen%20Shot%202015-06-29%20at%2011.23.10%20AM.png
>
> What do you think?
>
> Andr?s
>
>
>
> On Mon, Jun 29, 2015 at 10:10 AM, Andres Galante <agalante at redhat.com>
> wrote:
>
>> Good idea Sebastien! That is a good placement. I'll test it and see if we
>> need a line or something to mark a separation between them and the network
>> info.
>>
>> On Mon, Jun 29, 2015 at 10:05 AM, Sebastien Blanc <scm.blanc at gmail.com>
>> wrote:
>>
>>> I would vote to have them along with the other variant details that are
>>> already shown (like google's project number etc ...)
>>>
>>>
>>> On Mon, Jun 29, 2015 at 2:58 PM, Matthias Wessendorf <matzew at apache.org>
>>> wrote:
>>>
>>>>
>>>>
>>>> On Mon, Jun 29, 2015 at 2:19 PM, Andres Galante <agalante at redhat.com>
>>>> wrote:
>>>>
>>>>> Hi Matthias and Lukas,
>>>>>
>>>>> During the user research time I've learn that there are almost none
>>>>> use case where the user uses this information stand alone. The user would
>>>>> just copy and paste the code snippet.
>>>>>
>>>>
>>>> well, that does not always work (e.g. sligthly different structure of
>>>> code).
>>>> Even our own Android HelloWorld Demo is not able to use the snippets
>>>> and paste them in (due to different code structure - which is good).
>>>>
>>>> Having them visible give a bit more appreciation to these IDs (or call
>>>> em API keys), so it's easy to get the desired info quickly
>>>>
>>>>
>>>>
>>>>
>>>>>
>>>>> We use it a lot because we test it and set it up a bunch of times UPS.
>>>>> We already have the code set up and we end up knowing where to look for the
>>>>> data. Luke bring this same issue to me during Summit.
>>>>>
>>>>> Let me think of a good way to highlight that information to make the
>>>>> expert user life easier.
>>>>>
>>>>>
>>>>>
>>>>> On Wed, Jun 24, 2015 at 2:12 PM, Luk?? Fry? <lukas at fryc.eu> wrote:
>>>>>
>>>>>> Basically it is something that we "agreed on" (or rather didn't
>>>>>> catch) during mockup reviews and that never changed from that time.
>>>>>>
>>>>>> @Andres: did it have some reason to hide the details?
>>>>>>
>>>>>> I'm all for exposing it more visibly.
>>>>>>
>>>>>> st 24. 6. 2015 v 17:21 odes?latel Matthias Wessendorf <
>>>>>> matzew at apache.org> napsal:
>>>>>>
>>>>>>> Hi,
>>>>>>>
>>>>>>> on our old design the PushApplicationID/MasterSecret was very good
>>>>>>> to notice:
>>>>>>>
>>>>>>> https://aerogear.org/docs/unifiedpush/ups_userguide//img/applications_variant.png
>>>>>>>
>>>>>>> Now it's a bit more hidden (one has to click on the "Sender API" tab
>>>>>>> of the Application).
>>>>>>>
>>>>>>> Similar w/ the VariantID/Secret pair, IMO it is also a bit hidden,
>>>>>>> since this is only visible in the source snippets for the variant.
>>>>>>>
>>>>>>> They used to be a bit more present:
>>>>>>>
>>>>>>> https://aerogear.org/docs/unifiedpush/ups_userguide//img/applications_variant_details.png
>>>>>>>
>>>>>>> Since I find that suboptimal, I am wondering if that's done for a
>>>>>>> good reason, or if something (in a future version?) should be changed ?
>>>>>>>
>>>>>>> -M
>>>>>>>
>>>>>>> --
>>>>>>> Matthias Wessendorf
>>>>>>>
>>>>>>> blog: http://matthiaswessendorf.wordpress.com/
>>>>>>> sessions: http://www.slideshare.net/mwessendorf
>>>>>>> twitter: http://twitter.com/mwessendorf
>>>>>>>  _______________________________________________
>>>>>>> aerogear-dev mailing list
>>>>>>> aerogear-dev at lists.jboss.org
>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>>>
>>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> aerogear-dev mailing list
>>>>> aerogear-dev at lists.jboss.org
>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Matthias Wessendorf
>>>>
>>>> blog: http://matthiaswessendorf.wordpress.com/
>>>> sessions: http://www.slideshare.net/mwessendorf
>>>> twitter: http://twitter.com/mwessendorf
>>>>
>>>> _______________________________________________
>>>> aerogear-dev mailing list
>>>> aerogear-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>
>>>
>>>
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>
>>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150629/e904ca2f/attachment-0001.html 

From scm.blanc at gmail.com  Mon Jun 29 11:08:19 2015
From: scm.blanc at gmail.com (Sebastien Blanc)
Date: Mon, 29 Jun 2015 17:08:19 +0200
Subject: [aerogear-dev] UPS: Console - Visibility issues
In-Reply-To: <CAAg5f2SjV8Ag6bv7V7b_OkOyyZwZ4iNHdb46LaLZ2EiUXNr6ZQ@mail.gmail.com>
References: <CAAg5f2SF6bo8yuhj5gvdx6prY8Srreevrqp2XKLVNsmFne-+aQ@mail.gmail.com>
	<CAEroY369GzXXTeAPyDsY=x3_zC_5iOF=9_p+xHmvcBQF3LUzOg@mail.gmail.com>
	<CACAO5hcUBxTdEhrkQzXYBvzE1keoBYWRQdy5GH3azTMkziJG2w@mail.gmail.com>
	<CAAg5f2R4eNW8XWEbMO7BB3rmN9F_e55mPv2MiEeBwN-k937t_w@mail.gmail.com>
	<CAD_dpu3=S2jL2rxQ5gaCHbVG4oy5+eeQXrnrRzy2H6_Hq4rixg@mail.gmail.com>
	<CACAO5heAnFQvv_1ugSRsGS1Cf5X4dJ80Vi2hZw=LB=7-3jLzaQ@mail.gmail.com>
	<CACAO5hd5JQhQ-M92otQuZK=T8ZuFhqbAnfZsP91JVSEEj9KgsA@mail.gmail.com>
	<CAAg5f2SjV8Ag6bv7V7b_OkOyyZwZ4iNHdb46LaLZ2EiUXNr6ZQ@mail.gmail.com>
Message-ID: <CAD_dpu24DcbPQevCjST8osU0bAiVVt1EuoUpSNT6XjGmYeWigQ@mail.gmail.com>

+1

On Mon, Jun 29, 2015 at 5:03 PM, Matthias Wessendorf <matzew at apache.org>
wrote:

> I like it !
>
> On Mon, Jun 29, 2015 at 4:30 PM, Andres Galante <agalante at redhat.com>
> wrote:
>
>> Hi!
>>
>> To solve the variant information I made this:
>>
>> https://dl.dropboxusercontent.com/u/4371641/Screen%20Shot%202015-06-29%20at%2011.08.30%20AM.png
>>
>> But we are already showing the sender info at the sender tab:
>>
>> https://dl.dropboxusercontent.com/u/4371641/Screen%20Shot%202015-06-29%20at%2011.23.10%20AM.png
>>
>> What do you think?
>>
>> Andr?s
>>
>>
>>
>> On Mon, Jun 29, 2015 at 10:10 AM, Andres Galante <agalante at redhat.com>
>> wrote:
>>
>>> Good idea Sebastien! That is a good placement. I'll test it and see if
>>> we need a line or something to mark a separation between them and the
>>> network info.
>>>
>>> On Mon, Jun 29, 2015 at 10:05 AM, Sebastien Blanc <scm.blanc at gmail.com>
>>> wrote:
>>>
>>>> I would vote to have them along with the other variant details that are
>>>> already shown (like google's project number etc ...)
>>>>
>>>>
>>>> On Mon, Jun 29, 2015 at 2:58 PM, Matthias Wessendorf <matzew at apache.org
>>>> > wrote:
>>>>
>>>>>
>>>>>
>>>>> On Mon, Jun 29, 2015 at 2:19 PM, Andres Galante <agalante at redhat.com>
>>>>> wrote:
>>>>>
>>>>>> Hi Matthias and Lukas,
>>>>>>
>>>>>> During the user research time I've learn that there are almost none
>>>>>> use case where the user uses this information stand alone. The user would
>>>>>> just copy and paste the code snippet.
>>>>>>
>>>>>
>>>>> well, that does not always work (e.g. sligthly different structure of
>>>>> code).
>>>>> Even our own Android HelloWorld Demo is not able to use the snippets
>>>>> and paste them in (due to different code structure - which is good).
>>>>>
>>>>> Having them visible give a bit more appreciation to these IDs (or call
>>>>> em API keys), so it's easy to get the desired info quickly
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>>
>>>>>> We use it a lot because we test it and set it up a bunch of times
>>>>>> UPS. We already have the code set up and we end up knowing where to look
>>>>>> for the data. Luke bring this same issue to me during Summit.
>>>>>>
>>>>>> Let me think of a good way to highlight that information to make the
>>>>>> expert user life easier.
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Wed, Jun 24, 2015 at 2:12 PM, Luk?? Fry? <lukas at fryc.eu> wrote:
>>>>>>
>>>>>>> Basically it is something that we "agreed on" (or rather didn't
>>>>>>> catch) during mockup reviews and that never changed from that time.
>>>>>>>
>>>>>>> @Andres: did it have some reason to hide the details?
>>>>>>>
>>>>>>> I'm all for exposing it more visibly.
>>>>>>>
>>>>>>> st 24. 6. 2015 v 17:21 odes?latel Matthias Wessendorf <
>>>>>>> matzew at apache.org> napsal:
>>>>>>>
>>>>>>>> Hi,
>>>>>>>>
>>>>>>>> on our old design the PushApplicationID/MasterSecret was very good
>>>>>>>> to notice:
>>>>>>>>
>>>>>>>> https://aerogear.org/docs/unifiedpush/ups_userguide//img/applications_variant.png
>>>>>>>>
>>>>>>>> Now it's a bit more hidden (one has to click on the "Sender API"
>>>>>>>> tab of the Application).
>>>>>>>>
>>>>>>>> Similar w/ the VariantID/Secret pair, IMO it is also a bit hidden,
>>>>>>>> since this is only visible in the source snippets for the variant.
>>>>>>>>
>>>>>>>> They used to be a bit more present:
>>>>>>>>
>>>>>>>> https://aerogear.org/docs/unifiedpush/ups_userguide//img/applications_variant_details.png
>>>>>>>>
>>>>>>>> Since I find that suboptimal, I am wondering if that's done for a
>>>>>>>> good reason, or if something (in a future version?) should be changed ?
>>>>>>>>
>>>>>>>> -M
>>>>>>>>
>>>>>>>> --
>>>>>>>> Matthias Wessendorf
>>>>>>>>
>>>>>>>> blog: http://matthiaswessendorf.wordpress.com/
>>>>>>>> sessions: http://www.slideshare.net/mwessendorf
>>>>>>>> twitter: http://twitter.com/mwessendorf
>>>>>>>>  _______________________________________________
>>>>>>>> aerogear-dev mailing list
>>>>>>>> aerogear-dev at lists.jboss.org
>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>>>>
>>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> aerogear-dev mailing list
>>>>>> aerogear-dev at lists.jboss.org
>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Matthias Wessendorf
>>>>>
>>>>> blog: http://matthiaswessendorf.wordpress.com/
>>>>> sessions: http://www.slideshare.net/mwessendorf
>>>>> twitter: http://twitter.com/mwessendorf
>>>>>
>>>>> _______________________________________________
>>>>> aerogear-dev mailing list
>>>>> aerogear-dev at lists.jboss.org
>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> aerogear-dev mailing list
>>>> aerogear-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>
>>>
>>>
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150629/a9e883cf/attachment.html 

From matzew at apache.org  Mon Jun 29 13:42:35 2015
From: matzew at apache.org (Matthias Wessendorf)
Date: Mon, 29 Jun 2015 19:42:35 +0200
Subject: [aerogear-dev] This week in AeroGear
Message-ID: <CAAg5f2RKGAM8jju7jt1Noz83nQSMwx3TQf+YO8M3Tz=HmqPqqA@mail.gmail.com>

Hello folks!

here is another issue of our weekly updates!

*Android
In Android land we have a new release of the Push 2.2.0 library:
http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-AeroGear-Android-Push-2-2-0-tp11781p11813.html
Very soon the team will be looking into GCM 3.0 support !

*iOS
The Swift2 train started for our own AeroGear iOS library. The
aerogear-ios-http has already been migrated to it:
https://github.com/aerogear/aerogear-ios-http/tree/swift-2.0
AeroGear iOS 2.4 is moving its release date to September. Its main focus
will be Swift2 and iOS9 support. Just in time for the big
Swift-OpenSource-release ;-)

Apache Cordova
Another push related release has been created, this time for our Cordova
library, moving up its version to 2.0.0:
https://issues.jboss.org/browse/AGCORDOVA/fixforversion/12325960/

AeroGear Push
For our WebPush project we have Idel working on it, for his GSoC project. A
few days ago he sent out a nice little summary
http://lists.jboss.org/pipermail/aerogear-dev/2015-June/011745.html

And later this week we plan to do code-freeze for the 1.1.0.Final version
of our UnifiedPush Server.

The team hopes you are enjoying the news!

Have a nice week, all!
-Matthias


-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150629/6511fc9c/attachment.html 

From matzew at apache.org  Mon Jun 29 14:50:37 2015
From: matzew at apache.org (Matthias Wessendorf)
Date: Mon, 29 Jun 2015 20:50:37 +0200
Subject: [aerogear-dev] UPS 1.1.0.Final: Code freeze later this week
Message-ID: <CAAg5f2Q-pSWL9nNoSu5kB56JaiBXdReh94-Teo0Od6nJa8GAKw@mail.gmail.com>

Hi folks,

a few items left on our 1.1.0.Final (see [1]) and hopefully later this week
(ideally on Thursday) we will a code-freeze, to have the release out next
week.

If you have any suggestions or questions, please let us know!

-Matthias

[1] https://issues.jboss.org/browse/AGPUSH/fixforversion/12326301/

-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150629/c265ca5f/attachment.html 

From supittma at redhat.com  Mon Jun 29 18:07:43 2015
From: supittma at redhat.com (Summers Pittman)
Date: Mon, 29 Jun 2015 18:07:43 -0400
Subject: [aerogear-dev] AGDroid issues with Java 6
Message-ID: <CAEQz2CtMn=KkJTJQnDX_Bbykd646C3=9J-Qitwr+bedsdnZPgw@mail.gmail.com>

So I discovered a bug in the android-maven-plugin which makes building
projects on JDK 6 fail if they consume AAR dependencies.  I've reported
this to the project and have a potential fix in mind.

My question to the list is, a) do we want to drop Java 6 support and b) if
not are we fine with disabling JDK6 in travis until this gets resolved?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150629/c518a8a3/attachment-0001.html 

From dpassos at redhat.com  Mon Jun 29 19:40:54 2015
From: dpassos at redhat.com (Daniel Passos)
Date: Mon, 29 Jun 2015 20:40:54 -0300
Subject: [aerogear-dev] AGDroid issues with Java 6
In-Reply-To: <CAEQz2CtMn=KkJTJQnDX_Bbykd646C3=9J-Qitwr+bedsdnZPgw@mail.gmail.com>
References: <CAEQz2CtMn=KkJTJQnDX_Bbykd646C3=9J-Qitwr+bedsdnZPgw@mail.gmail.com>
Message-ID: <CADF=h2uRhvjnrXDG2Phg=akvSN051XerkXbtpfw=gRTHe-GWbw@mail.gmail.com>

In related https://github.com/simpligility/android-maven-plugin/issues/647

On Mon, Jun 29, 2015 at 7:07 PM, Summers Pittman <supittma at redhat.com>
wrote:

> So I discovered a bug in the android-maven-plugin which makes building
> projects on JDK 6 fail if they consume AAR dependencies.  I've reported
> this to the project and have a potential fix in mind.
>
> My question to the list is, a) do we want to drop Java 6 support and b) if
> not are we fine with disabling JDK6 in travis until this gets resolved?
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 
-- Passos
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150629/aad05072/attachment.html 

From supittma at redhat.com  Tue Jun 30 07:55:42 2015
From: supittma at redhat.com (Summers Pittman)
Date: Tue, 30 Jun 2015 07:55:42 -0400
Subject: [aerogear-dev] AGDroid issues with Java 6
In-Reply-To: <CADF=h2uRhvjnrXDG2Phg=akvSN051XerkXbtpfw=gRTHe-GWbw@mail.gmail.com>
References: <CAEQz2CtMn=KkJTJQnDX_Bbykd646C3=9J-Qitwr+bedsdnZPgw@mail.gmail.com>
	<CADF=h2uRhvjnrXDG2Phg=akvSN051XerkXbtpfw=gRTHe-GWbw@mail.gmail.com>
Message-ID: <CAEQz2Ct1L3AvYtr6H=jxr9Cp-22FZR8or4wbhrnCT34mSEkkjQ@mail.gmail.com>

Quoth Manfred :
" Java 6 is EOL for a long time now and Java 7 is since April. I would
rather get the build and usage to work with Java 8 rather than worry about
Java 6 at this stage.."

So do we drop support for Java 6 in AGDroid or do I submit a patch to the
plugin to fix Java 6?  Is there some third option?

On Mon, Jun 29, 2015 at 7:40 PM, Daniel Passos <dpassos at redhat.com> wrote:

> In related https://github.com/simpligility/android-maven-plugin/issues/647
>
> On Mon, Jun 29, 2015 at 7:07 PM, Summers Pittman <supittma at redhat.com>
> wrote:
>
>> So I discovered a bug in the android-maven-plugin which makes building
>> projects on JDK 6 fail if they consume AAR dependencies.  I've reported
>> this to the project and have a potential fix in mind.
>>
>> My question to the list is, a) do we want to drop Java 6 support and b)
>> if not are we fine with disabling JDK6 in travis until this gets resolved?
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
>
> --
> -- Passos
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150630/f4ddd6c2/attachment.html 

From matzew at apache.org  Tue Jun 30 07:58:02 2015
From: matzew at apache.org (Matthias Wessendorf)
Date: Tue, 30 Jun 2015 13:58:02 +0200
Subject: [aerogear-dev] AGDroid issues with Java 6
In-Reply-To: <CAEQz2Ct1L3AvYtr6H=jxr9Cp-22FZR8or4wbhrnCT34mSEkkjQ@mail.gmail.com>
References: <CAEQz2CtMn=KkJTJQnDX_Bbykd646C3=9J-Qitwr+bedsdnZPgw@mail.gmail.com>
	<CADF=h2uRhvjnrXDG2Phg=akvSN051XerkXbtpfw=gRTHe-GWbw@mail.gmail.com>
	<CAEQz2Ct1L3AvYtr6H=jxr9Cp-22FZR8or4wbhrnCT34mSEkkjQ@mail.gmail.com>
Message-ID: <CAAg5f2SeT14A-8-h1SMsgKesDaYE7UPDzNOi5oBZUrL-sQNwcw@mail.gmail.com>

+1 on dropping java6 - especially for 2.x and later (of AGDroid)

On Tue, Jun 30, 2015 at 1:55 PM, Summers Pittman <supittma at redhat.com>
wrote:

> Quoth Manfred :
> " Java 6 is EOL for a long time now and Java 7 is since April. I would
> rather get the build and usage to work with Java 8 rather than worry about
> Java 6 at this stage.."
>
> So do we drop support for Java 6 in AGDroid or do I submit a patch to the
> plugin to fix Java 6?  Is there some third option?
>
> On Mon, Jun 29, 2015 at 7:40 PM, Daniel Passos <dpassos at redhat.com> wrote:
>
>> In related
>> https://github.com/simpligility/android-maven-plugin/issues/647
>>
>> On Mon, Jun 29, 2015 at 7:07 PM, Summers Pittman <supittma at redhat.com>
>> wrote:
>>
>>> So I discovered a bug in the android-maven-plugin which makes building
>>> projects on JDK 6 fail if they consume AAR dependencies.  I've reported
>>> this to the project and have a potential fix in mind.
>>>
>>> My question to the list is, a) do we want to drop Java 6 support and b)
>>> if not are we fine with disabling JDK6 in travis until this gets resolved?
>>>
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>
>>
>>
>> --
>> -- Passos
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150630/5cfa0100/attachment.html 

From dpassos at redhat.com  Tue Jun 30 08:19:15 2015
From: dpassos at redhat.com (Daniel Passos)
Date: Tue, 30 Jun 2015 09:19:15 -0300
Subject: [aerogear-dev] AGDroid issues with Java 6
In-Reply-To: <CAAg5f2SeT14A-8-h1SMsgKesDaYE7UPDzNOi5oBZUrL-sQNwcw@mail.gmail.com>
References: <CAEQz2CtMn=KkJTJQnDX_Bbykd646C3=9J-Qitwr+bedsdnZPgw@mail.gmail.com>
	<CADF=h2uRhvjnrXDG2Phg=akvSN051XerkXbtpfw=gRTHe-GWbw@mail.gmail.com>
	<CAEQz2Ct1L3AvYtr6H=jxr9Cp-22FZR8or4wbhrnCT34mSEkkjQ@mail.gmail.com>
	<CAAg5f2SeT14A-8-h1SMsgKesDaYE7UPDzNOi5oBZUrL-sQNwcw@mail.gmail.com>
Message-ID: <CADF=h2sCUtCnJuEVJaK1UMh5VmnMV+yn+fHsMwsmC5SbPvoPuw@mail.gmail.com>

+1 on dropping java6

On Tue, Jun 30, 2015 at 8:58 AM, Matthias Wessendorf <matzew at apache.org>
wrote:

> +1 on dropping java6 - especially for 2.x and later (of AGDroid)
>
> On Tue, Jun 30, 2015 at 1:55 PM, Summers Pittman <supittma at redhat.com>
> wrote:
>
>> Quoth Manfred :
>> " Java 6 is EOL for a long time now and Java 7 is since April. I would
>> rather get the build and usage to work with Java 8 rather than worry about
>> Java 6 at this stage.."
>>
>> So do we drop support for Java 6 in AGDroid or do I submit a patch to the
>> plugin to fix Java 6?  Is there some third option?
>>
>> On Mon, Jun 29, 2015 at 7:40 PM, Daniel Passos <dpassos at redhat.com>
>> wrote:
>>
>>> In related
>>> https://github.com/simpligility/android-maven-plugin/issues/647
>>>
>>> On Mon, Jun 29, 2015 at 7:07 PM, Summers Pittman <supittma at redhat.com>
>>> wrote:
>>>
>>>> So I discovered a bug in the android-maven-plugin which makes building
>>>> projects on JDK 6 fail if they consume AAR dependencies.  I've reported
>>>> this to the project and have a potential fix in mind.
>>>>
>>>> My question to the list is, a) do we want to drop Java 6 support and b)
>>>> if not are we fine with disabling JDK6 in travis until this gets resolved?
>>>>
>>>> _______________________________________________
>>>> aerogear-dev mailing list
>>>> aerogear-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>
>>>
>>>
>>>
>>> --
>>> -- Passos
>>>
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 
-- Passos
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150630/672b88a7/attachment-0001.html 

From dpassos at redhat.com  Tue Jun 30 10:26:48 2015
From: dpassos at redhat.com (Daniel Passos)
Date: Tue, 30 Jun 2015 11:26:48 -0300
Subject: [aerogear-dev] AeroGear Android Pipe 2.1.1
Message-ID: <CADF=h2uk17P2Z55xcyYFi68+myRSsOwLPz2wbM-hYgAUDE5uvw@mail.gmail.com>

Hey Guys,

Artur Dryomov <https://github.com/ming13> found a bug in our AeroGear
Android Pipe library doing some work on Hawkular Android Client
<https://github.com/hawkular/hawkular-android-client/>. It was fixed and
staged[1]

What is new in this version?

   - AGDROID-426 <https://issues.jboss.org/browse/AGDROID-426> - No Content
   Response

We?re planning to release it next Friday.

Fell free to test it and let us know if you find any issues.

[1]
https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-5954/
?
-- 
-- Passos
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150630/e7969f82/attachment.html 

From supittma at redhat.com  Tue Jun 30 10:30:26 2015
From: supittma at redhat.com (Summers Pittman)
Date: Tue, 30 Jun 2015 10:30:26 -0400
Subject: [aerogear-dev] AeroGear Android Pipe 2.1.1
In-Reply-To: <CADF=h2uk17P2Z55xcyYFi68+myRSsOwLPz2wbM-hYgAUDE5uvw@mail.gmail.com>
References: <CADF=h2uk17P2Z55xcyYFi68+myRSsOwLPz2wbM-hYgAUDE5uvw@mail.gmail.com>
Message-ID: <CAEQz2CsAjyqbMFztRsBKuwTHRMbX29ccBm6ukX=F-1t1yCz3HA@mail.gmail.com>

Any cool demos to go with WRT hawkular?

On Tue, Jun 30, 2015 at 10:26 AM, Daniel Passos <dpassos at redhat.com> wrote:

> Hey Guys,
>
> Artur Dryomov <https://github.com/ming13> found a bug in our AeroGear
> Android Pipe library doing some work on Hawkular Android Client
> <https://github.com/hawkular/hawkular-android-client/>. It was fixed and
> staged[1]
>
> What is new in this version?
>
>    - AGDROID-426 <https://issues.jboss.org/browse/AGDROID-426> - No
>    Content Response
>
> We?re planning to release it next Friday.
>
> Fell free to test it and let us know if you find any issues.
>
> [1]
> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-5954/
> ?
> --
> -- Passos
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150630/34852a54/attachment.html 

From dpassos at redhat.com  Tue Jun 30 10:40:08 2015
From: dpassos at redhat.com (Daniel Passos)
Date: Tue, 30 Jun 2015 11:40:08 -0300
Subject: [aerogear-dev] AeroGear Android Pipe 2.1.1
In-Reply-To: <CAEQz2CsAjyqbMFztRsBKuwTHRMbX29ccBm6ukX=F-1t1yCz3HA@mail.gmail.com>
References: <CADF=h2uk17P2Z55xcyYFi68+myRSsOwLPz2wbM-hYgAUDE5uvw@mail.gmail.com>
	<CAEQz2CsAjyqbMFztRsBKuwTHRMbX29ccBm6ukX=F-1t1yCz3HA@mail.gmail.com>
Message-ID: <CADF=h2vUGBjA_=cmYmj+G_pTYXaJ9KjNsw_F37DKUct2X2=k+g@mail.gmail.com>

Yes => https://github.com/hawkular/hawkular-android-client/

On Tue, Jun 30, 2015 at 11:30 AM, Summers Pittman <supittma at redhat.com>
wrote:

> Any cool demos to go with WRT hawkular?
>
> On Tue, Jun 30, 2015 at 10:26 AM, Daniel Passos <dpassos at redhat.com>
> wrote:
>
>> Hey Guys,
>>
>> Artur Dryomov <https://github.com/ming13> found a bug in our AeroGear
>> Android Pipe library doing some work on Hawkular Android Client
>> <https://github.com/hawkular/hawkular-android-client/>. It was fixed and
>> staged[1]
>>
>> What is new in this version?
>>
>>    - AGDROID-426 <https://issues.jboss.org/browse/AGDROID-426> - No
>>    Content Response
>>
>> We?re planning to release it next Friday.
>>
>> Fell free to test it and let us know if you find any issues.
>>
>> [1]
>> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-5954/
>> ?
>> --
>> -- Passos
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 
-- Passos
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150630/526a85a5/attachment.html 

From supittma at redhat.com  Tue Jun 30 15:47:48 2015
From: supittma at redhat.com (Summers Pittman)
Date: Tue, 30 Jun 2015 15:47:48 -0400
Subject: [aerogear-dev] AGDroid issues with Java 6
In-Reply-To: <CAAg5f2SeT14A-8-h1SMsgKesDaYE7UPDzNOi5oBZUrL-sQNwcw@mail.gmail.com>
References: <CAEQz2CtMn=KkJTJQnDX_Bbykd646C3=9J-Qitwr+bedsdnZPgw@mail.gmail.com>
	<CADF=h2uRhvjnrXDG2Phg=akvSN051XerkXbtpfw=gRTHe-GWbw@mail.gmail.com>
	<CAEQz2Ct1L3AvYtr6H=jxr9Cp-22FZR8or4wbhrnCT34mSEkkjQ@mail.gmail.com>
	<CAAg5f2SeT14A-8-h1SMsgKesDaYE7UPDzNOi5oBZUrL-sQNwcw@mail.gmail.com>
Message-ID: <CAEQz2CsV1LsgvUScqiJZNnmm8nWNnRbX5RUZgc0Di9WFFZk0Xg@mail.gmail.com>

So it seems like at some point Android officially dropped Java 6 support as
well.

On Tue, Jun 30, 2015 at 7:58 AM, Matthias Wessendorf <matzew at apache.org>
wrote:

> +1 on dropping java6 - especially for 2.x and later (of AGDroid)
>
> On Tue, Jun 30, 2015 at 1:55 PM, Summers Pittman <supittma at redhat.com>
> wrote:
>
>> Quoth Manfred :
>> " Java 6 is EOL for a long time now and Java 7 is since April. I would
>> rather get the build and usage to work with Java 8 rather than worry about
>> Java 6 at this stage.."
>>
>> So do we drop support for Java 6 in AGDroid or do I submit a patch to the
>> plugin to fix Java 6?  Is there some third option?
>>
>> On Mon, Jun 29, 2015 at 7:40 PM, Daniel Passos <dpassos at redhat.com>
>> wrote:
>>
>>> In related
>>> https://github.com/simpligility/android-maven-plugin/issues/647
>>>
>>> On Mon, Jun 29, 2015 at 7:07 PM, Summers Pittman <supittma at redhat.com>
>>> wrote:
>>>
>>>> So I discovered a bug in the android-maven-plugin which makes building
>>>> projects on JDK 6 fail if they consume AAR dependencies.  I've reported
>>>> this to the project and have a potential fix in mind.
>>>>
>>>> My question to the list is, a) do we want to drop Java 6 support and b)
>>>> if not are we fine with disabling JDK6 in travis until this gets resolved?
>>>>
>>>> _______________________________________________
>>>> aerogear-dev mailing list
>>>> aerogear-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>
>>>
>>>
>>>
>>> --
>>> -- Passos
>>>
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150630/e39fac5e/attachment-0001.html 

From matzew at apache.org  Tue Jun 30 16:04:21 2015
From: matzew at apache.org (Matthias Wessendorf)
Date: Tue, 30 Jun 2015 22:04:21 +0200
Subject: [aerogear-dev] AGDroid issues with Java 6
In-Reply-To: <CAEQz2CsV1LsgvUScqiJZNnmm8nWNnRbX5RUZgc0Di9WFFZk0Xg@mail.gmail.com>
References: <CAEQz2CtMn=KkJTJQnDX_Bbykd646C3=9J-Qitwr+bedsdnZPgw@mail.gmail.com>
	<CADF=h2uRhvjnrXDG2Phg=akvSN051XerkXbtpfw=gRTHe-GWbw@mail.gmail.com>
	<CAEQz2Ct1L3AvYtr6H=jxr9Cp-22FZR8or4wbhrnCT34mSEkkjQ@mail.gmail.com>
	<CAAg5f2SeT14A-8-h1SMsgKesDaYE7UPDzNOi5oBZUrL-sQNwcw@mail.gmail.com>
	<CAEQz2CsV1LsgvUScqiJZNnmm8nWNnRbX5RUZgc0Di9WFFZk0Xg@mail.gmail.com>
Message-ID: <CAAg5f2R7k9y6mqOkt+U0dKuPndKMz_GuwTWZo2GcLsaMrRUq9g@mail.gmail.com>

Cool - android++

I think its good to have a blog post on us getting rid if j6 for android
(and linking to android's statement of saying good bye to j6)

On Tuesday, June 30, 2015, Summers Pittman <supittma at redhat.com> wrote:

> So it seems like at some point Android officially dropped Java 6 support
> as well.
>
> On Tue, Jun 30, 2015 at 7:58 AM, Matthias Wessendorf <matzew at apache.org
> <javascript:_e(%7B%7D,'cvml','matzew at apache.org');>> wrote:
>
>> +1 on dropping java6 - especially for 2.x and later (of AGDroid)
>>
>> On Tue, Jun 30, 2015 at 1:55 PM, Summers Pittman <supittma at redhat.com
>> <javascript:_e(%7B%7D,'cvml','supittma at redhat.com');>> wrote:
>>
>>> Quoth Manfred :
>>> " Java 6 is EOL for a long time now and Java 7 is since April. I would
>>> rather get the build and usage to work with Java 8 rather than worry about
>>> Java 6 at this stage.."
>>>
>>> So do we drop support for Java 6 in AGDroid or do I submit a patch to
>>> the plugin to fix Java 6?  Is there some third option?
>>>
>>> On Mon, Jun 29, 2015 at 7:40 PM, Daniel Passos <dpassos at redhat.com
>>> <javascript:_e(%7B%7D,'cvml','dpassos at redhat.com');>> wrote:
>>>
>>>> In related
>>>> https://github.com/simpligility/android-maven-plugin/issues/647
>>>>
>>>> On Mon, Jun 29, 2015 at 7:07 PM, Summers Pittman <supittma at redhat.com
>>>> <javascript:_e(%7B%7D,'cvml','supittma at redhat.com');>> wrote:
>>>>
>>>>> So I discovered a bug in the android-maven-plugin which makes building
>>>>> projects on JDK 6 fail if they consume AAR dependencies.  I've reported
>>>>> this to the project and have a potential fix in mind.
>>>>>
>>>>> My question to the list is, a) do we want to drop Java 6 support and
>>>>> b) if not are we fine with disabling JDK6 in travis until this gets
>>>>> resolved?
>>>>>
>>>>> _______________________________________________
>>>>> aerogear-dev mailing list
>>>>> aerogear-dev at lists.jboss.org
>>>>> <javascript:_e(%7B%7D,'cvml','aerogear-dev at lists.jboss.org');>
>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> -- Passos
>>>>
>>>> _______________________________________________
>>>> aerogear-dev mailing list
>>>> aerogear-dev at lists.jboss.org
>>>> <javascript:_e(%7B%7D,'cvml','aerogear-dev at lists.jboss.org');>
>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>
>>>
>>>
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> <javascript:_e(%7B%7D,'cvml','aerogear-dev at lists.jboss.org');>
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>
>>
>>
>> --
>> Matthias Wessendorf
>>
>> blog: http://matthiaswessendorf.wordpress.com/
>> sessions: http://www.slideshare.net/mwessendorf
>> twitter: http://twitter.com/mwessendorf
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> <javascript:_e(%7B%7D,'cvml','aerogear-dev at lists.jboss.org');>
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>

-- 
Sent from Gmail Mobile
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150630/6c0227f8/attachment.html 

From artur.dryomov at gmail.com  Tue Jun 30 16:46:43 2015
From: artur.dryomov at gmail.com (Artur Dryomov)
Date: Tue, 30 Jun 2015 23:46:43 +0300
Subject: [aerogear-dev] AGDroid issues with Java 6
In-Reply-To: <CAAg5f2R7k9y6mqOkt+U0dKuPndKMz_GuwTWZo2GcLsaMrRUq9g@mail.gmail.com>
References: <CAEQz2CtMn=KkJTJQnDX_Bbykd646C3=9J-Qitwr+bedsdnZPgw@mail.gmail.com>
	<CADF=h2uRhvjnrXDG2Phg=akvSN051XerkXbtpfw=gRTHe-GWbw@mail.gmail.com>
	<CAEQz2Ct1L3AvYtr6H=jxr9Cp-22FZR8or4wbhrnCT34mSEkkjQ@mail.gmail.com>
	<CAAg5f2SeT14A-8-h1SMsgKesDaYE7UPDzNOi5oBZUrL-sQNwcw@mail.gmail.com>
	<CAEQz2CsV1LsgvUScqiJZNnmm8nWNnRbX5RUZgc0Di9WFFZk0Xg@mail.gmail.com>
	<CAAg5f2R7k9y6mqOkt+U0dKuPndKMz_GuwTWZo2GcLsaMrRUq9g@mail.gmail.com>
Message-ID: <CAC6O=UXe2Q8uy2jaUAWB165cPnyYjE+0aSJ77-ku-d69-BQ_6w@mail.gmail.com>

I may be totally wrong, but I probably saw JDK 7 requirement in times of L
preview. Or it was just a dream!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150630/b57b4e78/attachment.html 

From artur.dryomov at gmail.com  Tue Jun 30 16:50:12 2015
From: artur.dryomov at gmail.com (Artur Dryomov)
Date: Tue, 30 Jun 2015 23:50:12 +0300
Subject: [aerogear-dev] AeroGear Android Pipe 2.1.1
In-Reply-To: <CADF=h2vUGBjA_=cmYmj+G_pTYXaJ9KjNsw_F37DKUct2X2=k+g@mail.gmail.com>
References: <CADF=h2uk17P2Z55xcyYFi68+myRSsOwLPz2wbM-hYgAUDE5uvw@mail.gmail.com>
	<CAEQz2CsAjyqbMFztRsBKuwTHRMbX29ccBm6ukX=F-1t1yCz3HA@mail.gmail.com>
	<CADF=h2vUGBjA_=cmYmj+G_pTYXaJ9KjNsw_F37DKUct2X2=k+g@mail.gmail.com>
Message-ID: <CAC6O=UUTUZkiDVAx3FACdzPYVjVwFdviMGUt6YtHDKbekFEd9Q@mail.gmail.com>

As far as I can tell, the 2.2.1 version works great for my use case.

2.2.1 for 204 HTTP response returns valid empty list, i. e. Arrays.asList()
or new ArrayList<>().
2.2.0 for 204 HTTP response returns weird list with a single null element,
i. e. Arrays.asList(null).
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150630/69e86246/attachment.html