From eng.mmustafa84 at gmail.com  Sat Apr  2 17:53:57 2016
From: eng.mmustafa84 at gmail.com (Mohamed Mostafa)
Date: Sat, 2 Apr 2016 23:53:57 +0200
Subject: [Aerogear-users] Adding plugin aerogear-cordova-push is failing -
	dependency issues ?
Message-ID: <CABHuOg6Lu3oCPROCMdG39mWf7MaF6CwcXEeqK9hibaLs-MsFdA@mail.gmail.com>

Hello All, I hope this email finds you all well ...

I've been trying to add the aerogear cordova push plugin to my cordova app
for multiple days now, but it is always failing.
Just using the simple comand
cordova plugin add https://github.com/aerogear/aerogear-cordova-push.git
gives me the error:
Fetching plugin "https://github.com/vstirbu/PromisesPlugin.git" via git
clone
Error during processing of action! Attempting to revert...
Failed to install 'aerogear-cordova-push':Error: Uh oh!
cannot find
"C:\Work\g2g\git_repository\g2g-customer\platforms\android\aerogear-cordova-push\dependencies.gradle\project.properties"
referenced in <framework>
    at Object.AndroidProject.addSubProject
(C:\Users\IBM_ADMIN\AppData\Roaming\npm\node_modules\cordova\node_modules\cordova-lib\src\plugman\util\android-project.js:70:51)

Please help


Best Regards,
Mohamed Mostafa
IT Architect - IBM Egypt
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20160402/9403fb29/attachment.html 

From edewit at redhat.com  Mon Apr  4 03:36:32 2016
From: edewit at redhat.com (Erik Jan de Wit)
Date: Mon, 4 Apr 2016 09:36:32 +0200
Subject: [Aerogear-users] Adding plugin aerogear-cordova-push is failing
 - dependency issues ?
In-Reply-To: <CABHuOg6Lu3oCPROCMdG39mWf7MaF6CwcXEeqK9hibaLs-MsFdA@mail.gmail.com>
References: <CABHuOg6Lu3oCPROCMdG39mWf7MaF6CwcXEeqK9hibaLs-MsFdA@mail.gmail.com>
Message-ID: <CAO2B-fZeY38bXw1i_Xe4uN7Yv_shoSYhvV_Rg7+XnEfEa64Eww@mail.gmail.com>

Sorry to hear that, what version are you using? I did the following:

*?**?**?* cordova -v

6.1.1

*?**?* cordova create test

Creating a new cordova project.

/tmp *?**?**?* cd test

/t/test *?**?**?* cordova plugin add
https://github.com/aerogear/aerogear-cordova-push.git
                          ?

Fetching plugin "https://github.com/aerogear/aerogear-cordova-push.git" via
git clone

Repository "https://github.com/aerogear/aerogear-cordova-push.git" checked
out to git ref "master".

/t/test *?**?**?* cordova platform add android

Adding android project...

Creating Cordova project for the Android platform:

Path: ../../../tmp/test/platforms/android

Package: io.cordova.hellocordova

Name: HelloCordova

Activity: MainActivity

Android target: android-23

Android project created with cordova-android at 5.1.1

Installing "aerogear-cordova-push" for android

Fetching plugin "https://github.com/vstirbu/PromisesPlugin.git" via git
clone

Repository "https://github.com/vstirbu/PromisesPlugin.git" checked out to
git ref "master".

Installing "es6-promise-plugin" for android

Discovered plugin "cordova-plugin-whitelist" in config.xml. Installing to
the project

Fetching plugin "cordova-plugin-whitelist at 1" via npm

Installing "cordova-plugin-whitelist" for android


               This plugin is only applicable for versions of
cordova-android greater than 4.0. If you have a previous platform version,
you do *not* need this plugin since the whitelist will be built in.



/t/test *?**?**?* cordova build

ANDROID_HOME=/Users/edewit/Library/Developer/Xamarin/android-sdk-macosx

JAVA_HOME=/Library/Java/JavaVirtualMachines/jdk1.7.0_80.jdk/Contents/Home

:preBuild UP-TO-DATE

:preDebugBuild UP-TO-DATE

...

BUILD SUCCESSFUL


Total time: 2 mins 26.777 secs

Built the following apk(s):

/private/tmp/test/platforms/android/build/outputs/apk/android-debug.apk

On Sat, Apr 2, 2016 at 11:53 PM, Mohamed Mostafa <eng.mmustafa84 at gmail.com>
wrote:

> Hello All, I hope this email finds you all well ...
>
> I've been trying to add the aerogear cordova push plugin to my cordova app
> for multiple days now, but it is always failing.
> Just using the simple comand
> cordova plugin add https://github.com/aerogear/aerogear-cordova-push.git
> gives me the error:
> Fetching plugin "https://github.com/vstirbu/PromisesPlugin.git" via git
> clone
> Error during processing of action! Attempting to revert...
> Failed to install 'aerogear-cordova-push':Error: Uh oh!
> cannot find
> "C:\Work\g2g\git_repository\g2g-customer\platforms\android\aerogear-cordova-push\dependencies.gradle\project.properties"
> referenced in <framework>
>     at Object.AndroidProject.addSubProject
> (C:\Users\IBM_ADMIN\AppData\Roaming\npm\node_modules\cordova\node_modules\cordova-lib\src\plugman\util\android-project.js:70:51)
>
> Please help
>
>
> Best Regards,
> Mohamed Mostafa
> IT Architect - IBM Egypt
>
> _______________________________________________
> Aerogear-users mailing list
> Aerogear-users at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-users
>
>


-- 
Cheers,
       Erik Jan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20160404/a5fa3275/attachment.html 

From matzew at apache.org  Thu Apr  7 07:27:41 2016
From: matzew at apache.org (Matthias Wessendorf)
Date: Thu, 7 Apr 2016 13:27:41 +0200
Subject: [Aerogear-users] Titanium and UPS
Message-ID: <CAAg5f2R21JnWxjPzpLCJBRJSTYRaKep-f4JAKC48JdSQY_KTeg@mail.gmail.com>

Hi all,

I am very excited to see that our friends at Napp created another nice lib
for the UPS, supporting Titanium:
https://github.com/Napp/AeroGear-Push-Titanium

Cheers!
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-users/attachments/20160407/de87c752/attachment.html 

From aamagdi at ejada.com  Sun Apr 10 08:27:03 2016
From: aamagdi at ejada.com (aamagdi)
Date: Sun, 10 Apr 2016 05:27:03 -0700 (MST)
Subject: [Aerogear-users] UPS Server JVM Memory Recommendation
Message-ID: <1460291223677-591.post@n5.nabble.com>

Hello

I would like to ask about JVM memory size recommendation of Heap & Perm size
for UPS server 1.1.1 deployed on EAP 6.4

Regards



--
View this message in context: http://aerogear-users.1116366.n5.nabble.com/UPS-Server-JVM-Memory-Recommendation-tp591.html
Sent from the aerogear-users mailing list archive at Nabble.com.

From ffraticelli at unog.ch  Fri Apr 15 10:07:32 2016
From: ffraticelli at unog.ch (ffraticelli)
Date: Fri, 15 Apr 2016 07:07:32 -0700 (MST)
Subject: [Aerogear-users] bug (?) in the REST API
Message-ID: <1460729252031-592.post@n5.nabble.com>

Hello, I found this (blocking) issue using the REST API for registering
devices.It's a test container, you can use the commands below and I will
delete the variant once this issue is confirmed by your team.The following
curl works and registers the device token:   curl -u
"daa39c18-fdae-4696-b24f-041008f8a28a:a3186331-5e54-48b1-be2f-30b348d9dd40" 
\   -v -H "Accept: application/json" -H "Content-type: application/json" -H
"aerogear-push-id: someid" \   -X POST  -d \  '{     "deviceToken" :
"fffffffffffffffffffffffffffffffffffffe432da6199aa9b1c49f6ab99f7e20bdf9ae5df25569e7b43fc550c6c461aecd",    
"deviceType" : "iPad",     "operatingSystem" : "iOS",     "osVersion" :
"6.1.2"   }'  \  
https://aerogear-unog.rhcloud.com/ag-push/rest/registry/device*While the
following receives an HTTP 400 Bad Request. The only different between the 2
is an additional 'f' in the following token.*   curl -u
"daa39c18-fdae-4696-b24f-041008f8a28a:a3186331-5e54-48b1-be2f-30b348d9dd40" 
\   -v -H "Accept: application/json" -H "Content-type: application/json" -H
"aerogear-push-id: someid" \   -X POST  -d \  '{     "deviceToken" :
"ffffffffffffffffffffffffffffffffffffe432da6199aa9b1c49f6ab99f7e20bdf9ae5df25569e7b43fc550c6c461aecd",    
"deviceType" : "iPad",     "operatingSystem" : "iOS",     "osVersion" :
"6.1.2"   }'  \  
https://aerogear-unog.rhcloud.com/ag-push/rest/registry/deviceWith the
actual token (without the f list) t doesn't work either, 400 error.



--
View this message in context: http://aerogear-users.1116366.n5.nabble.com/bug-in-the-REST-API-tp592.html
Sent from the aerogear-users mailing list archive at Nabble.com.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20160415/f4ba0289/attachment-0001.html 

From scm.blanc at gmail.com  Fri Apr 15 10:23:16 2016
From: scm.blanc at gmail.com (Sebastien Blanc)
Date: Fri, 15 Apr 2016 16:23:16 +0200
Subject: [Aerogear-users] bug (?) in the REST API
In-Reply-To: <1460729252031-592.post@n5.nabble.com>
References: <1460729252031-592.post@n5.nabble.com>
Message-ID: <CAD_dpu2XcyFmVVHU+3XKi7Um26s+85S6FNu=Jcp+TfVExf4WpQ@mail.gmail.com>

Could it be that it does not pass the token validation
https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/model/api/src/main/java/org/jboss/aerogear/unifiedpush/api/validation/DeviceTokenValidator.java#L35
?

On Fri, Apr 15, 2016 at 4:07 PM, ffraticelli <ffraticelli at unog.ch> wrote:

> Hello, I found this (blocking) issue using the REST API for registering
> devices. It's a test container, you can use the commands below and I will
> delete the variant once this issue is confirmed by your team. The following
> curl works and registers the device token: curl -u
> "daa39c18-fdae-4696-b24f-041008f8a28a:a3186331-5e54-48b1-be2f-30b348d9dd40"
> \ -v -H "Accept: application/json" -H "Content-type: application/json" -H
> "aerogear-push-id: someid" \ -X POST -d \ '{ "deviceToken" :
> "fffffffffffffffffffffffffffffffffffffe432da6199aa9b1c49f6ab99f7e20bdf9ae5df25569e7b43fc550c6c461aecd",
> "deviceType" : "iPad", "operatingSystem" : "iOS", "osVersion" : "6.1.2" }'
> \ https://aerogear-unog.rhcloud.com/ag-push/rest/registry/device *While
> the following receives an HTTP 400 Bad Request. The only different between
> the 2 is an additional 'f' in the following token.* curl -u
> "daa39c18-fdae-4696-b24f-041008f8a28a:a3186331-5e54-48b1-be2f-30b348d9dd40"
> \ -v -H "Accept: application/json" -H "Content-type: application/json" -H
> "aerogear-push-id: someid" \ -X POST -d \ '{ "deviceToken" :
> "ffffffffffffffffffffffffffffffffffffe432da6199aa9b1c49f6ab99f7e20bdf9ae5df25569e7b43fc550c6c461aecd",
> "deviceType" : "iPad", "operatingSystem" : "iOS", "osVersion" : "6.1.2" }'
> \ https://aerogear-unog.rhcloud.com/ag-push/rest/registry/device With the
> actual token (without the f list) t doesn't work either, 400 error.
> ------------------------------
> View this message in context: bug (?) in the REST API
> <http://aerogear-users.1116366.n5.nabble.com/bug-in-the-REST-API-tp592.html>
> Sent from the aerogear-users mailing list archive
> <http://aerogear-users.1116366.n5.nabble.com/> at Nabble.com.
>
> _______________________________________________
> 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-users/attachments/20160415/e9275ee1/attachment.html 

From matzew at apache.org  Fri Apr 15 10:24:36 2016
From: matzew at apache.org (Matthias Wessendorf)
Date: Fri, 15 Apr 2016 16:24:36 +0200
Subject: [Aerogear-users] bug (?) in the REST API
In-Reply-To: <1460729252031-592.post@n5.nabble.com>
References: <1460729252031-592.post@n5.nabble.com>
Message-ID: <CAAg5f2R0JYugFGvd4HOTsV6BgJ1xUKLkOLag+EhACypUDqHjhQ@mail.gmail.com>

Hi,

I am unable to reproduce the problem, using latest 1.2.0-alpha.1, both
tokens worked, for an iOS variant:
*
fffffffffffffffffffffffffffffffffffffe432da6199aa9b1c49f6ab99f7e20bdf9ae5df25569e7b43fc550c6c461aecd
*
ffffffffffffffffffffffffffffffffffffe432da6199aa9b1c49f6ab99f7e20bdf9ae5df25569e7b43fc550c6c461aecd

What's the version you are on?

-Matthias



On Fri, Apr 15, 2016 at 4:07 PM, ffraticelli <ffraticelli at unog.ch> wrote:

> Hello, I found this (blocking) issue using the REST API for registering
> devices. It's a test container, you can use the commands below and I will
> delete the variant once this issue is confirmed by your team. The following
> curl works and registers the device token: curl -u
> "daa39c18-fdae-4696-b24f-041008f8a28a:a3186331-5e54-48b1-be2f-30b348d9dd40"
> \ -v -H "Accept: application/json" -H "Content-type: application/json" -H
> "aerogear-push-id: someid" \ -X POST -d \ '{ "deviceToken" :
> "fffffffffffffffffffffffffffffffffffffe432da6199aa9b1c49f6ab99f7e20bdf9ae5df25569e7b43fc550c6c461aecd",
> "deviceType" : "iPad", "operatingSystem" : "iOS", "osVersion" : "6.1.2" }'
> \ https://aerogear-unog.rhcloud.com/ag-push/rest/registry/device *While
> the following receives an HTTP 400 Bad Request. The only different between
> the 2 is an additional 'f' in the following token.* curl -u
> "daa39c18-fdae-4696-b24f-041008f8a28a:a3186331-5e54-48b1-be2f-30b348d9dd40"
> \ -v -H "Accept: application/json" -H "Content-type: application/json" -H
> "aerogear-push-id: someid" \ -X POST -d \ '{ "deviceToken" :
> "ffffffffffffffffffffffffffffffffffffe432da6199aa9b1c49f6ab99f7e20bdf9ae5df25569e7b43fc550c6c461aecd",
> "deviceType" : "iPad", "operatingSystem" : "iOS", "osVersion" : "6.1.2" }'
> \ https://aerogear-unog.rhcloud.com/ag-push/rest/registry/device With the
> actual token (without the f list) t doesn't work either, 400 error.
> ------------------------------
> View this message in context: bug (?) in the REST API
> <http://aerogear-users.1116366.n5.nabble.com/bug-in-the-REST-API-tp592.html>
> Sent from the aerogear-users mailing list archive
> <http://aerogear-users.1116366.n5.nabble.com/> at Nabble.com.
>
> _______________________________________________
> 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-users/attachments/20160415/2f390f24/attachment.html 

From ffraticelli at unog.ch  Fri Apr 15 10:29:40 2016
From: ffraticelli at unog.ch (ffraticelli)
Date: Fri, 15 Apr 2016 07:29:40 -0700 (MST)
Subject: [Aerogear-users] bug (?) in the REST API
In-Reply-To: <CAD_dpu2XcyFmVVHU+3XKi7Um26s+85S6FNu=Jcp+TfVExf4WpQ@mail.gmail.com>
References: <1460729252031-592.post@n5.nabble.com>
	<CAD_dpu2XcyFmVVHU+3XKi7Um26s+85S6FNu=Jcp+TfVExf4WpQ@mail.gmail.com>
Message-ID: <1460730580879-595.post@n5.nabble.com>

It could be the token validator, I don't have a developer platform and I
cannot debug it on my own. 

The real (following) token doesn't pass through:
fe432da6199aa9b1c49f6ab99f7e20bdf9ae5df25569e7b43fc550c6c461aecd

I tested the above token with other push servers and it works for both
registration and notification receiving.



--
View this message in context: http://aerogear-users.1116366.n5.nabble.com/bug-in-the-REST-API-tp592p595.html
Sent from the aerogear-users mailing list archive at Nabble.com.

From matzew at apache.org  Fri Apr 15 10:30:24 2016
From: matzew at apache.org (Matthias Wessendorf)
Date: Fri, 15 Apr 2016 16:30:24 +0200
Subject: [Aerogear-users] bug (?) in the REST API
In-Reply-To: <1460730580879-595.post@n5.nabble.com>
References: <1460729252031-592.post@n5.nabble.com>
	<CAD_dpu2XcyFmVVHU+3XKi7Um26s+85S6FNu=Jcp+TfVExf4WpQ@mail.gmail.com>
	<1460730580879-595.post@n5.nabble.com>
Message-ID: <CAAg5f2RqtKyMZ+1iAD_cGuXdzP7fphvCEv0gzzYRxaaQ4AzHmg@mail.gmail.com>

ok, looking!

Mind sharing the version ?


On Fri, Apr 15, 2016 at 4:29 PM, ffraticelli <ffraticelli at unog.ch> wrote:

> It could be the token validator, I don't have a developer platform and I
> cannot debug it on my own.
>
> The real (following) token doesn't pass through:
> fe432da6199aa9b1c49f6ab99f7e20bdf9ae5df25569e7b43fc550c6c461aecd
>
> I tested the above token with other push servers and it works for both
> registration and notification receiving.
>
>
>
> --
> View this message in context:
> http://aerogear-users.1116366.n5.nabble.com/bug-in-the-REST-API-tp592p595.html
> Sent from the aerogear-users mailing list archive at Nabble.com.
> _______________________________________________
> 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-users/attachments/20160415/b4835bd1/attachment.html 

From ffraticelli at unog.ch  Fri Apr 15 10:32:12 2016
From: ffraticelli at unog.ch (ffraticelli)
Date: Fri, 15 Apr 2016 07:32:12 -0700 (MST)
Subject: [Aerogear-users] bug (?) in the REST API
In-Reply-To: <CAAg5f2RqtKyMZ+1iAD_cGuXdzP7fphvCEv0gzzYRxaaQ4AzHmg@mail.gmail.com>
References: <1460729252031-592.post@n5.nabble.com>
	<CAD_dpu2XcyFmVVHU+3XKi7Um26s+85S6FNu=Jcp+TfVExf4WpQ@mail.gmail.com>
	<1460730580879-595.post@n5.nabble.com>
	<CAAg5f2RqtKyMZ+1iAD_cGuXdzP7fphvCEv0gzzYRxaaQ4AzHmg@mail.gmail.com>
Message-ID: <1460730732864-597.post@n5.nabble.com>

Sure.
 
AeroGear UnifiedPush Server 1.1.0.Final and WildFly





--
View this message in context: http://aerogear-users.1116366.n5.nabble.com/bug-in-the-REST-API-tp592p597.html
Sent from the aerogear-users mailing list archive at Nabble.com.

From matzew at apache.org  Fri Apr 15 10:32:46 2016
From: matzew at apache.org (Matthias Wessendorf)
Date: Fri, 15 Apr 2016 16:32:46 +0200
Subject: [Aerogear-users] bug (?) in the REST API
In-Reply-To: <1460730732864-597.post@n5.nabble.com>
References: <1460729252031-592.post@n5.nabble.com>
	<CAD_dpu2XcyFmVVHU+3XKi7Um26s+85S6FNu=Jcp+TfVExf4WpQ@mail.gmail.com>
	<1460730580879-595.post@n5.nabble.com>
	<CAAg5f2RqtKyMZ+1iAD_cGuXdzP7fphvCEv0gzzYRxaaQ4AzHmg@mail.gmail.com>
	<1460730732864-597.post@n5.nabble.com>
Message-ID: <CAAg5f2Q3qLUYvO_i6XcES7kM8TcqtjGdxm0F=B2Db0ED+hL0Sw@mail.gmail.com>

I am now checking 1.1.2 :)

will let you know in a bit

On Fri, Apr 15, 2016 at 4:32 PM, ffraticelli <ffraticelli at unog.ch> wrote:

> Sure.
>
> AeroGear UnifiedPush Server 1.1.0.Final and WildFly
>
>
>
>
>
> --
> View this message in context:
> http://aerogear-users.1116366.n5.nabble.com/bug-in-the-REST-API-tp592p597.html
> Sent from the aerogear-users mailing list archive at Nabble.com.
> _______________________________________________
> 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-users/attachments/20160415/eb1c21f3/attachment-0001.html 

From matzew at apache.org  Fri Apr 15 10:37:17 2016
From: matzew at apache.org (Matthias Wessendorf)
Date: Fri, 15 Apr 2016 16:37:17 +0200
Subject: [Aerogear-users] bug (?) in the REST API
In-Reply-To: <CAAg5f2Q3qLUYvO_i6XcES7kM8TcqtjGdxm0F=B2Db0ED+hL0Sw@mail.gmail.com>
References: <1460729252031-592.post@n5.nabble.com>
	<CAD_dpu2XcyFmVVHU+3XKi7Um26s+85S6FNu=Jcp+TfVExf4WpQ@mail.gmail.com>
	<1460730580879-595.post@n5.nabble.com>
	<CAAg5f2RqtKyMZ+1iAD_cGuXdzP7fphvCEv0gzzYRxaaQ4AzHmg@mail.gmail.com>
	<1460730732864-597.post@n5.nabble.com>
	<CAAg5f2Q3qLUYvO_i6XcES7kM8TcqtjGdxm0F=B2Db0ED+hL0Sw@mail.gmail.com>
Message-ID: <CAAg5f2TZ2o9J1msG1sUufjksBBeUJMHAVGMBG-t3K2TQpZJANw@mail.gmail.com>

On UPS 1.1.2, it works:

Here is my CURL:
curl -u
"96c9e3f4-f503-48a1-ab47-0c651df696ab:b62414df-4581-4d6d-92d0-5e9a249674ef"
-v -H "Accept: application/json" -H "Content-type: application/json" -X
POST -d '{"deviceToken" :
"fe432da6199aa9b1c49f6ab99f7e20bdf9ae5df25569e7b43fc550c6c461aecd",
"deviceType" : "iPhone"}'
https://tokentest-pushee.rhcloud.com/ag-push/rest/registry/device

and here is the variant, with that one token:
https://tokentest-pushee.rhcloud.com/ag-push/#/app/0d207278-bbb6-4308-81da-31e446f4ad0f/variants
(admin:123)


-Matthias



On Fri, Apr 15, 2016 at 4:32 PM, Matthias Wessendorf <matzew at apache.org>
wrote:

> I am now checking 1.1.2 :)
>
> will let you know in a bit
>
> On Fri, Apr 15, 2016 at 4:32 PM, ffraticelli <ffraticelli at unog.ch> wrote:
>
>> Sure.
>>
>> AeroGear UnifiedPush Server 1.1.0.Final and WildFly
>>
>>
>>
>>
>>
>> --
>> View this message in context:
>> http://aerogear-users.1116366.n5.nabble.com/bug-in-the-REST-API-tp592p597.html
>> Sent from the aerogear-users mailing list archive at Nabble.com.
>> _______________________________________________
>> 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
>



-- 
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-users/attachments/20160415/0873be8b/attachment.html 

From ffraticelli at unog.ch  Fri Apr 15 10:40:12 2016
From: ffraticelli at unog.ch (ffraticelli)
Date: Fri, 15 Apr 2016 07:40:12 -0700 (MST)
Subject: [Aerogear-users] bug (?) in the REST API
In-Reply-To: <CAAg5f2TZ2o9J1msG1sUufjksBBeUJMHAVGMBG-t3K2TQpZJANw@mail.gmail.com>
References: <1460729252031-592.post@n5.nabble.com>
	<CAD_dpu2XcyFmVVHU+3XKi7Um26s+85S6FNu=Jcp+TfVExf4WpQ@mail.gmail.com>
	<1460730580879-595.post@n5.nabble.com>
	<CAAg5f2RqtKyMZ+1iAD_cGuXdzP7fphvCEv0gzzYRxaaQ4AzHmg@mail.gmail.com>
	<1460730732864-597.post@n5.nabble.com>
	<CAAg5f2Q3qLUYvO_i6XcES7kM8TcqtjGdxm0F=B2Db0ED+hL0Sw@mail.gmail.com>
	<CAAg5f2TZ2o9J1msG1sUufjksBBeUJMHAVGMBG-t3K2TQpZJANw@mail.gmail.com>
Message-ID: <1460731212286-600.post@n5.nabble.com>

Wow, that was fast :)
Thanks a lot.

Do you know if there is any plan for openshift to upgrade their UPS version?



--
View this message in context: http://aerogear-users.1116366.n5.nabble.com/bug-in-the-REST-API-tp592p600.html
Sent from the aerogear-users mailing list archive at Nabble.com.

From matzew at apache.org  Fri Apr 15 10:47:06 2016
From: matzew at apache.org (Matthias Wessendorf)
Date: Fri, 15 Apr 2016 16:47:06 +0200
Subject: [Aerogear-users] bug (?) in the REST API
In-Reply-To: <1460731212286-600.post@n5.nabble.com>
References: <1460729252031-592.post@n5.nabble.com>
	<CAD_dpu2XcyFmVVHU+3XKi7Um26s+85S6FNu=Jcp+TfVExf4WpQ@mail.gmail.com>
	<1460730580879-595.post@n5.nabble.com>
	<CAAg5f2RqtKyMZ+1iAD_cGuXdzP7fphvCEv0gzzYRxaaQ4AzHmg@mail.gmail.com>
	<1460730732864-597.post@n5.nabble.com>
	<CAAg5f2Q3qLUYvO_i6XcES7kM8TcqtjGdxm0F=B2Db0ED+hL0Sw@mail.gmail.com>
	<CAAg5f2TZ2o9J1msG1sUufjksBBeUJMHAVGMBG-t3K2TQpZJANw@mail.gmail.com>
	<1460731212286-600.post@n5.nabble.com>
Message-ID: <CAAg5f2Q3T2t28ghRwP7sdfQfxjj8Z_ppdh8gzBer=3N-HOFzcA@mail.gmail.com>

I also did on 1.1.0:

curl -u
"7c1e9096-7409-4f05-97ce-79ce7d02ea48:d6c26bbb-5534-4eaf-92c3-86bb379e072e"
-v -H "Accept: application/json" -H "Content-type: application/json" -X
POST -d '{"deviceToken" :
"fe432da6199aa9b1c49f6ab99f7e20bdf9ae5df25569e7b43fc550c6c461aecd",
"deviceType" : "iPad", "operatingSystem" : "iOS", "osVersion" : "6.1.2"}'
https://someolderpush-pushee.rhcloud.com/ag-push/rest/registry/device


works too - sorry !

@update: you can manually update your own server:
https://github.com/aerogear/openshift-origin-cartridge-aerogear-push/pull/24#issuecomment-207468613

but caution :-) ATM there is no 'update' feature enabled on our AeroGear
UPS cartridge

On Fri, Apr 15, 2016 at 4:40 PM, ffraticelli <ffraticelli at unog.ch> wrote:

> Wow, that was fast :)
> Thanks a lot.
>
> Do you know if there is any plan for openshift to upgrade their UPS
> version?
>
>
>
> --
> View this message in context:
> http://aerogear-users.1116366.n5.nabble.com/bug-in-the-REST-API-tp592p600.html
> Sent from the aerogear-users mailing list archive at Nabble.com.
> _______________________________________________
> 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-users/attachments/20160415/23a78e1c/attachment.html 

From matzew at apache.org  Fri Apr 15 10:50:37 2016
From: matzew at apache.org (Matthias Wessendorf)
Date: Fri, 15 Apr 2016 16:50:37 +0200
Subject: [Aerogear-users] bug (?) in the REST API
In-Reply-To: <CAAg5f2Q3T2t28ghRwP7sdfQfxjj8Z_ppdh8gzBer=3N-HOFzcA@mail.gmail.com>
References: <1460729252031-592.post@n5.nabble.com>
	<CAD_dpu2XcyFmVVHU+3XKi7Um26s+85S6FNu=Jcp+TfVExf4WpQ@mail.gmail.com>
	<1460730580879-595.post@n5.nabble.com>
	<CAAg5f2RqtKyMZ+1iAD_cGuXdzP7fphvCEv0gzzYRxaaQ4AzHmg@mail.gmail.com>
	<1460730732864-597.post@n5.nabble.com>
	<CAAg5f2Q3qLUYvO_i6XcES7kM8TcqtjGdxm0F=B2Db0ED+hL0Sw@mail.gmail.com>
	<CAAg5f2TZ2o9J1msG1sUufjksBBeUJMHAVGMBG-t3K2TQpZJANw@mail.gmail.com>
	<1460731212286-600.post@n5.nabble.com>
	<CAAg5f2Q3T2t28ghRwP7sdfQfxjj8Z_ppdh8gzBer=3N-HOFzcA@mail.gmail.com>
Message-ID: <CAAg5f2SCqF1kbY6tjjHK0NkZTQN8uzu9RkkqrZCOkSWErkWfvA@mail.gmail.com>

btw... can you share details about the variant ?

and, is the cartridge installed on a 'medium' sized machine? the (free)
default (small) is not working

On Fri, Apr 15, 2016 at 4:47 PM, Matthias Wessendorf <matzew at apache.org>
wrote:

> I also did on 1.1.0:
>
> curl -u
> "7c1e9096-7409-4f05-97ce-79ce7d02ea48:d6c26bbb-5534-4eaf-92c3-86bb379e072e"
> -v -H "Accept: application/json" -H "Content-type: application/json" -X
> POST -d '{"deviceToken" :
> "fe432da6199aa9b1c49f6ab99f7e20bdf9ae5df25569e7b43fc550c6c461aecd",
> "deviceType" : "iPad", "operatingSystem" : "iOS", "osVersion" : "6.1.2"}'
> https://someolderpush-pushee.rhcloud.com/ag-push/rest/registry/device
>
>
> works too - sorry !
>
> @update: you can manually update your own server:
> https://github.com/aerogear/openshift-origin-cartridge-aerogear-push/pull/24#issuecomment-207468613
>
> but caution :-) ATM there is no 'update' feature enabled on our AeroGear
> UPS cartridge
>
> On Fri, Apr 15, 2016 at 4:40 PM, ffraticelli <ffraticelli at unog.ch> wrote:
>
>> Wow, that was fast :)
>> Thanks a lot.
>>
>> Do you know if there is any plan for openshift to upgrade their UPS
>> version?
>>
>>
>>
>> --
>> View this message in context:
>> http://aerogear-users.1116366.n5.nabble.com/bug-in-the-REST-API-tp592p600.html
>> Sent from the aerogear-users mailing list archive at Nabble.com.
>> _______________________________________________
>> 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
>



-- 
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-users/attachments/20160415/9f9bd384/attachment.html 

From FFRATICELLI at unog.ch  Fri Apr 15 11:03:28 2016
From: FFRATICELLI at unog.ch (Fausto FRATICELLI)
Date: Fri, 15 Apr 2016 17:03:28 +0200
Subject: [Aerogear-users] bug (?) in the REST API
In-Reply-To: <CAAg5f2SCqF1kbY6tjjHK0NkZTQN8uzu9RkkqrZCOkSWErkWfvA@mail.gmail.com>
References: <CAAg5f2SCqF1kbY6tjjHK0NkZTQN8uzu9RkkqrZCOkSWErkWfvA@mail.gmail.com>,
	<1460729252031-592.post@n5.nabble.com>	<CAD_dpu2XcyFmVVHU+3XKi7Um26s+85S6FNu=Jcp+TfVExf4WpQ@mail.gmail.com>
	<1460730580879-595.post@n5.nabble.com>	<CAAg5f2RqtKyMZ+1iAD_cGuXdzP7fphvCEv0gzzYRxaaQ4AzHmg@mail.gmail.com>
	<1460730732864-597.post@n5.nabble.com>	<CAAg5f2Q3qLUYvO_i6XcES7kM8TcqtjGdxm0F=B2Db0ED+hL0Sw@mail.gmail.com>
	<CAAg5f2TZ2o9J1msG1sUufjksBBeUJMHAVGMBG-t3K2TQpZJANw@mail.gmail.com>	<1460731212286-600.post@n5.nabble.com>
	<CAAg5f2Q3T2t28ghRwP7sdfQfxjj8Z_ppdh8gzBer=3N-HOFzcA@mail.gmail.com>
Message-ID: <OF57963273.DB81A9CC-ONC1257F96.0052B74E-C1257F96.0052B750@unog.un.org>

An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20160415/44ebe0a7/attachment-0001.html 

From matzew at apache.org  Fri Apr 15 11:30:22 2016
From: matzew at apache.org (Matthias Wessendorf)
Date: Fri, 15 Apr 2016 17:30:22 +0200
Subject: [Aerogear-users] bug (?) in the REST API
In-Reply-To: <OF57963273.DB81A9CC-ONC1257F96.0052B74E-C1257F96.0052B750@unog.un.org>
References: <1460729252031-592.post@n5.nabble.com>
	<CAD_dpu2XcyFmVVHU+3XKi7Um26s+85S6FNu=Jcp+TfVExf4WpQ@mail.gmail.com>
	<1460730580879-595.post@n5.nabble.com>
	<CAAg5f2RqtKyMZ+1iAD_cGuXdzP7fphvCEv0gzzYRxaaQ4AzHmg@mail.gmail.com>
	<1460730732864-597.post@n5.nabble.com>
	<CAAg5f2Q3qLUYvO_i6XcES7kM8TcqtjGdxm0F=B2Db0ED+hL0Sw@mail.gmail.com>
	<CAAg5f2TZ2o9J1msG1sUufjksBBeUJMHAVGMBG-t3K2TQpZJANw@mail.gmail.com>
	<1460731212286-600.post@n5.nabble.com>
	<CAAg5f2Q3T2t28ghRwP7sdfQfxjj8Z_ppdh8gzBer=3N-HOFzcA@mail.gmail.com>
	<CAAg5f2SCqF1kbY6tjjHK0NkZTQN8uzu9RkkqrZCOkSWErkWfvA@mail.gmail.com>
	<OF57963273.DB81A9CC-ONC1257F96.0052B74E-C1257F96.0052B750@unog.un.org>
Message-ID: <CAAg5f2QVpxjLE+16Ugnr2AVY02BU+C7yqR9s4P3Ro4D_SVzPYg@mail.gmail.com>

Hello Fausto!

ok, be my guest and use my 'tokentest' version :-)
Please don't use the someolderpush version - thanks!

Oh, are you OK I delete my variant/app ?

You are currently evaluating the UPS for usage at the UN? In case your mgmt
team approves it will be used inside the UN's Docker farm?
Mind keeping me up-to-date, if UPS usage was approved?

PS: we also have Docker images for UPS ;-)

Thanks,
Matthias



On Fri, Apr 15, 2016 at 5:03 PM, Fausto FRATICELLI <FFRATICELLI at unog.ch>
wrote:

> it's the free default (small) gear. 1 GB
>
> it works for registering and sending notifications, but it's not 100%
> stable and has this unfortunate bug (version 1.0)
>
> Fausto
>
> -----aerogear-users-bounces at lists.jboss.org wrote: -----
> To: "aerogear-users at lists.jboss.org" <aerogear-users at lists.jboss.org>
> From: Matthias Wessendorf
> Sent by: aerogear-users-bounces at lists.jboss.org
> Date: 04/15/2016 04:51PM
> Subject: Re: [Aerogear-users] bug (?) in the REST API
>
>
> btw... can you share details about the variant ?
>
> and, is the cartridge installed on a 'medium' sized machine? the (free)
> default (small) is not working
>
> On Fri, Apr 15, 2016 at 4:47 PM, Matthias Wessendorf <matzew at apache.org>
> wrote:
>
>> I also did on 1.1.0:
>>
>> curl -u
>> "7c1e9096-7409-4f05-97ce-79ce7d02ea48:d6c26bbb-5534-4eaf-92c3-86bb379e072e"
>> -v -H "Accept: application/json" -H "Content-type: application/json" -X
>> POST -d '{"deviceToken" :
>> "fe432da6199aa9b1c49f6ab99f7e20bdf9ae5df25569e7b43fc550c6c461aecd",
>> "deviceType" : "iPad", "operatingSystem" : "iOS", "osVersion" : "6.1.2"}'
>> https://someolderpush-pushee.rhcloud.com/ag-push/rest/registry/device
>>
>>
>> works too - sorry !
>>
>> @update: you can manually update your own server:
>> https://github.com/aerogear/openshift-origin-cartridge-aerogear-push/pull/24#issuecomment-207468613
>>
>> but caution :-) ATM there is no 'update' feature enabled on our AeroGear
>> UPS cartridge
>>
>> On Fri, Apr 15, 2016 at 4:40 PM, ffraticelli <ffraticelli at unog.ch> wrote:
>>
>>> Wow, that was fast :)
>>> Thanks a lot.
>>>
>>> Do you know if there is any plan for openshift to upgrade their UPS
>>> version?
>>>
>>>
>>>
>>> --
>>> View this message in context:
>>> http://aerogear-users.1116366.n5.nabble.com/bug-in-the-REST-API-tp592p600.html
>>> Sent from the aerogear-users mailing list archive at Nabble.com.
>>> _______________________________________________
>>> 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
>>
>
>
>
> --
> 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
>
> _______________________________________________
> 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-users/attachments/20160415/f9f2336e/attachment.html 

From yves.nicolas at dynamease.com  Fri Apr 15 12:09:03 2016
From: yves.nicolas at dynamease.com (Yves Nicolas)
Date: Fri, 15 Apr 2016 18:09:03 +0200
Subject: [Aerogear-users] what is the good way to delete an alias entry in
 aerogear unified push servers
Message-ID: <5711121F.8090605@dynamease.com>

The user interface enable to uncheck the alias so that it doesn't 
receive notification anymore but what is the good way to delete the 
alias/device token from the aerogear database?

Thanks
Yves


From matzew at apache.org  Fri Apr 15 13:18:47 2016
From: matzew at apache.org (Matthias Wessendorf)
Date: Fri, 15 Apr 2016 19:18:47 +0200
Subject: [Aerogear-users] what is the good way to delete an alias entry
 in aerogear unified push servers
In-Reply-To: <5711121F.8090605@dynamease.com>
References: <5711121F.8090605@dynamease.com>
Message-ID: <CAAg5f2QR0MZ9nk1GjxMpHwNd6Zu_o7DrhAURO9yKJP+9O66R8w@mail.gmail.com>

remove the entire installation entry:
https://aerogear.org/docs/specs/aerogear-unifiedpush-rest/index.html#417932897

what's the use-case - perhaps we can improve our story?



On Fri, Apr 15, 2016 at 6:09 PM, Yves Nicolas <yves.nicolas at dynamease.com>
wrote:

> The user interface enable to uncheck the alias so that it doesn't
> receive notification anymore but what is the good way to delete the
> alias/device token from the aerogear database?
>
> Thanks
> Yves
>
> _______________________________________________
> 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-users/attachments/20160415/62e63ca1/attachment.html 

From sharathmk99 at gmail.com  Sat Apr 16 15:42:50 2016
From: sharathmk99 at gmail.com (sharathmk99)
Date: Sat, 16 Apr 2016 12:42:50 -0700 (MST)
Subject: [Aerogear-users] How to add new Sender(eg. MQTT custom sender)
Message-ID: <1460835770679-607.post@n5.nabble.com>

Hi,

I'm trying to add MQTT based push notification.
How to add new sender module to source code or
any custom sender implementation to add new sender.

Any one interested in MQTT based push notification?
please help.

Thanks
Sharath



--
View this message in context: http://aerogear-users.1116366.n5.nabble.com/How-to-add-new-Sender-eg-MQTT-custom-sender-tp607.html
Sent from the aerogear-users mailing list archive at Nabble.com.

From matzew at apache.org  Sun Apr 17 03:47:45 2016
From: matzew at apache.org (Matthias Wessendorf)
Date: Sun, 17 Apr 2016 09:47:45 +0200
Subject: [Aerogear-users] How to add new Sender(eg. MQTT custom sender)
In-Reply-To: <1460835770679-607.post@n5.nabble.com>
References: <1460835770679-607.post@n5.nabble.com>
Message-ID: <CAAg5f2R1gOz=BhQjP=OJopuXwxw-PDotjx3TtcRzenP+p44DXA@mail.gmail.com>

Hi,

did you see Sebi's reply to your other mail?
http://lists.jboss.org/pipermail/aerogear-dev/2016-April/012353.html

-Matthias

On Sat, Apr 16, 2016 at 9:42 PM, sharathmk99 <sharathmk99 at gmail.com> wrote:

> Hi,
>
> I'm trying to add MQTT based push notification.
> How to add new sender module to source code or
> any custom sender implementation to add new sender.
>
> Any one interested in MQTT based push notification?
> please help.
>
> Thanks
> Sharath
>
>
>
> --
> View this message in context:
> http://aerogear-users.1116366.n5.nabble.com/How-to-add-new-Sender-eg-MQTT-custom-sender-tp607.html
> Sent from the aerogear-users mailing list archive at Nabble.com.
> _______________________________________________
> 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-users/attachments/20160417/d9151778/attachment-0001.html 

From sharathmk99 at gmail.com  Sun Apr 17 07:17:04 2016
From: sharathmk99 at gmail.com (Sharath MK)
Date: Sun, 17 Apr 2016 16:47:04 +0530
Subject: [Aerogear-users] How to add new Sender(eg. MQTT custom sender)
In-Reply-To: <CAAg5f2R1gOz=BhQjP=OJopuXwxw-PDotjx3TtcRzenP+p44DXA@mail.gmail.com>
References: <1460835770679-607.post@n5.nabble.com>
	<CAAg5f2R1gOz=BhQjP=OJopuXwxw-PDotjx3TtcRzenP+p44DXA@mail.gmail.com>
Message-ID: <CACHcdXjt2qr0+Wn7LH3ySW=FExn4vT16Zm2f7A_WpLJvOfS__A@mail.gmail.com>

Hi,

Yes I have seen, but I have understood the backbend. But front end UI is
change. Can you help in front end.

Thanks
On 17 Apr 2016 1:17 pm, "Matthias Wessendorf" <matzew at apache.org> wrote:

> Hi,
>
> did you see Sebi's reply to your other mail?
> http://lists.jboss.org/pipermail/aerogear-dev/2016-April/012353.html
>
> -Matthias
>
> On Sat, Apr 16, 2016 at 9:42 PM, sharathmk99 <sharathmk99 at gmail.com>
> wrote:
>
>> Hi,
>>
>> I'm trying to add MQTT based push notification.
>> How to add new sender module to source code or
>> any custom sender implementation to add new sender.
>>
>> Any one interested in MQTT based push notification?
>> please help.
>>
>> Thanks
>> Sharath
>>
>>
>>
>> --
>> View this message in context:
>> http://aerogear-users.1116366.n5.nabble.com/How-to-add-new-Sender-eg-MQTT-custom-sender-tp607.html
>> Sent from the aerogear-users mailing list archive at Nabble.com.
>> _______________________________________________
>> 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
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20160417/e1b6e6b3/attachment.html 

From yves.nicolas at dynamease.com  Mon Apr 18 03:15:41 2016
From: yves.nicolas at dynamease.com (Yves Nicolas)
Date: Mon, 18 Apr 2016 09:15:41 +0200
Subject: [Aerogear-users] what is the good way to delete an alias,
 entry in aerogear unified push servers
Message-ID: <5714899D.5020805@dynamease.com>

API deletion is ok. Use case for deletion by Alias : Java written 
backoffice doesnt know about device tokens, we want to be able to 
deregister users from the backoffice. API management, or from the java 
library. our other use case for unregistration are from the devices 
themselves, they know about the token. We can manage with the Rest api, 
is there a plan to include the unregistration inside the android and IOS 
library? Thxs Message: 3 Date: Fri, 15 Apr 2016 19:18:47 +0200 From: 
Matthias Wessendorf <matzew at apache.org> Subject: Re: [Aerogear-users] 
what is the good way to delete an alias entry in aerogear unified push 
servers To: "aerogear-users at lists.jboss.org" 
<aerogear-users at lists.jboss.org> Message-ID: 
<CAAg5f2QR0MZ9nk1GjxMpHwNd6Zu_o7DrhAURO9yKJP+9O66R8w at mail.gmail.com> 
Content-Type: text/plain; charset="utf-8" remove the entire installation 
entry: 
https://aerogear.org/docs/specs/aerogear-unifiedpush-rest/index.html#417932897 
what's the use-case - perhaps we can improve our story? On Fri, Apr 15, 
2016 at 6:09 PM, Yves Nicolas <yves.nicolas at dynamease.com> wrote:

> The user interface enable to uncheck the alias so that it doesn't
> receive notification anymore but what is the good way to delete the
> alias/device token from the aerogear database?
>
> Thanks
> Yves
>
> _______________________________________________
> Aerogear-users mailing list
> Aerogear-users at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-users
>

From matzew at apache.org  Mon Apr 18 03:27:03 2016
From: matzew at apache.org (Matthias Wessendorf)
Date: Mon, 18 Apr 2016 09:27:03 +0200
Subject: [Aerogear-users] what is the good way to delete an alias,
 entry in aerogear unified push servers
In-Reply-To: <5714899D.5020805@dynamease.com>
References: <5714899D.5020805@dynamease.com>
Message-ID: <CAAg5f2TfLZt=nH8R84GuUPQU-3YLbf5jrnqm=qTfwtVe-PXrdg@mail.gmail.com>

Hi Yves,

On Mon, Apr 18, 2016 at 9:15 AM, Yves Nicolas <yves.nicolas at dynamease.com>
wrote:

> API deletion is ok. Use case for deletion by Alias : Java written
> backoffice doesnt know about device tokens, we want to be able to
> deregister users from the backoffice. API management, or from the java
> library. our other use case for unregistration are from the devices
> themselves, they know about the token. We can manage with the Rest api,
>

Or, you can use this nice library that a different AeroGear user created!
https://github.com/mfischelmayer/aerogear-push-helper/blob/master/src/main/java/at/ftec/aerogear/api/impl/DefaultAerogearAdminService.java#L152-L159




> is there a plan to include the unregistration inside the android and IOS
> library?


Android:
there is this method:
https://github.com/aerogear/aerogear-android-push/blob/master/aerogear-android-push/src/main/java/org/jboss/aerogear/android/unifiedpush/PushRegistrar.java#L40

which does both:
* 'unregister' from the GCM service, as well as from the UPS.

Perhaps that's something you can leverage ?


On iOS, we don't have this, because Apple does not recommend to have users
manually unregister from push on the app. Their preferred way is disabling
push on the global setting.

However, I think it's arguable that unregistering from UPS, for an app, is
not equals to completely unregister from APNs, for the same app. Worth to
explore this on a different thread  :-)



> Thxs Message: 3 Date: Fri, 15 Apr 2016 19:18:47 +0200 From:
> Matthias Wessendorf <matzew at apache.org> Subject: Re: [Aerogear-users]
> what is the good way to delete an alias entry in aerogear unified push
> servers To: "aerogear-users at lists.jboss.org"
> <aerogear-users at lists.jboss.org> Message-ID:
> <CAAg5f2QR0MZ9nk1GjxMpHwNd6Zu_o7DrhAURO9yKJP+9O66R8w at mail.gmail.com>
> Content-Type: text/plain; charset="utf-8" remove the entire installation
> entry:
>
> https://aerogear.org/docs/specs/aerogear-unifiedpush-rest/index.html#417932897
> what's the use-case - perhaps we can improve our story? On Fri, Apr 15,
> 2016 at 6:09 PM, Yves Nicolas <yves.nicolas at dynamease.com> wrote:
>
> > The user interface enable to uncheck the alias so that it doesn't
> > receive notification anymore but what is the good way to delete the
> > alias/device token from the aerogear database?
> >
> > Thanks
> > Yves
> >
> > _______________________________________________
> > Aerogear-users mailing list
> > Aerogear-users at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/aerogear-users
> >
> _______________________________________________
> 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-users/attachments/20160418/99337fa1/attachment.html 

From yves.nicolas at dynamease.com  Mon Apr 18 03:34:08 2016
From: yves.nicolas at dynamease.com (Yves Nicolas)
Date: Mon, 18 Apr 2016 09:34:08 +0200
Subject: [Aerogear-users] what is the good way to delete an alias,
 entry in aerogear unified push servers
In-Reply-To: <CAAg5f2TfLZt=nH8R84GuUPQU-3YLbf5jrnqm=qTfwtVe-PXrdg@mail.gmail.com>
References: <5714899D.5020805@dynamease.com>
	<CAAg5f2TfLZt=nH8R84GuUPQU-3YLbf5jrnqm=qTfwtVe-PXrdg@mail.gmail.com>
Message-ID: <57148DF0.4020805@dynamease.com>

looks good, will try the aerogear push helper from mfischelmayer.
Was actually aware for the Android one, looking for the equivalent in Apple.
Definitely agree with you regarding the difference, it makes sense for 
the App to keep being registered at the APN level (user doesnt need to 
authorize the remote notifications again) but we want the user to be 
unregistered from the server, although this is not a high priority use case.


Le 18/04/2016 09:27, Matthias Wessendorf a ?crit :
> Hi Yves,
>
> On Mon, Apr 18, 2016 at 9:15 AM, Yves Nicolas 
> <yves.nicolas at dynamease.com <mailto:yves.nicolas at dynamease.com>> wrote:
>
>     API deletion is ok. Use case for deletion by Alias : Java written
>     backoffice doesnt know about device tokens, we want to be able to
>     deregister users from the backoffice. API management, or from the java
>     library. our other use case for unregistration are from the devices
>     themselves, they know about the token. We can manage with the Rest
>     api,
>
>
> Or, you can use this nice library that a different AeroGear user created!
> https://github.com/mfischelmayer/aerogear-push-helper/blob/master/src/main/java/at/ftec/aerogear/api/impl/DefaultAerogearAdminService.java#L152-L159
>
>
>     is there a plan to include the unregistration inside the android
>     and IOS
>     library? 
>
>
> Android:
> there is this method:
> https://github.com/aerogear/aerogear-android-push/blob/master/aerogear-android-push/src/main/java/org/jboss/aerogear/android/unifiedpush/PushRegistrar.java#L40
>
> which does both:
> * 'unregister' from the GCM service, as well as from the UPS.
>
> Perhaps that's something you can leverage ?
>
>
> On iOS, we don't have this, because Apple does not recommend to have 
> users manually unregister from push on the app. Their preferred way is 
> disabling push on the global setting.
>
> However, I think it's arguable that unregistering from UPS, for an 
> app, is not equals to completely unregister from APNs, for the same 
> app. Worth to explore this on a different thread  :-)
>
>     Thxs Message: 3 Date: Fri, 15 Apr 2016 19:18:47 +0200 From:
>     Matthias Wessendorf <matzew at apache.org <mailto:matzew at apache.org>>
>     Subject: Re: [Aerogear-users]
>     what is the good way to delete an alias entry in aerogear unified push
>     servers To: "aerogear-users at lists.jboss.org
>     <mailto:aerogear-users at lists.jboss.org>"
>     <aerogear-users at lists.jboss.org
>     <mailto:aerogear-users at lists.jboss.org>> Message-ID:
>     <CAAg5f2QR0MZ9nk1GjxMpHwNd6Zu_o7DrhAURO9yKJP+9O66R8w at mail.gmail.com <mailto:CAAg5f2QR0MZ9nk1GjxMpHwNd6Zu_o7DrhAURO9yKJP%2B9O66R8w at mail.gmail.com>>
>     Content-Type: text/plain; charset="utf-8" remove the entire
>     installation
>     entry:
>     https://aerogear.org/docs/specs/aerogear-unifiedpush-rest/index.html#417932897
>     what's the use-case - perhaps we can improve our story? On Fri,
>     Apr 15,
>     2016 at 6:09 PM, Yves Nicolas <yves.nicolas at dynamease.com
>     <mailto:yves.nicolas at dynamease.com>> wrote:
>
>     > The user interface enable to uncheck the alias so that it doesn't
>     > receive notification anymore but what is the good way to delete the
>     > alias/device token from the aerogear database?
>     >
>     > Thanks
>     > Yves
>     >
>     > _______________________________________________
>     > Aerogear-users mailing list
>     > Aerogear-users at lists.jboss.org
>     <mailto:Aerogear-users at lists.jboss.org>
>     > https://lists.jboss.org/mailman/listinfo/aerogear-users
>     >
>     _______________________________________________
>     Aerogear-users mailing list
>     Aerogear-users at lists.jboss.org <mailto: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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20160418/aedd345e/attachment-0001.html 

From matzew at apache.org  Mon Apr 18 03:53:55 2016
From: matzew at apache.org (Matthias Wessendorf)
Date: Mon, 18 Apr 2016 09:53:55 +0200
Subject: [Aerogear-users] what is the good way to delete an alias,
 entry in aerogear unified push servers
In-Reply-To: <57148DF0.4020805@dynamease.com>
References: <5714899D.5020805@dynamease.com>
	<CAAg5f2TfLZt=nH8R84GuUPQU-3YLbf5jrnqm=qTfwtVe-PXrdg@mail.gmail.com>
	<57148DF0.4020805@dynamease.com>
Message-ID: <CAAg5f2RPA6Y_+9gwPgdyD3On+NDo-JA_i4Jv2=JJ0PBLQKyoiw@mail.gmail.com>

On Mon, Apr 18, 2016 at 9:34 AM, Yves Nicolas <yves.nicolas at dynamease.com>
wrote:

> looks good, will try the aerogear push helper from mfischelmayer.
> Was actually aware for the Android one, looking for the equivalent in
> Apple.
> Definitely agree with you regarding the difference, it makes sense for the
> App to keep being registered at the APN level (user doesnt need to
> authorize the remote notifications again) but we want the user to be
> unregistered from the server, although this is not a high priority use case.
>

There are a few things we need to be aware of:
* when app issues such an unregister call, the UPS won't be sending push
notifications
* each launch of the application will hit
'application:didRegisterForRemoteNotificationsWithDeviceToken', meaning the
previously removed token will be readded. Local state on the app needs to
be around, to deviced if the registration w/ UPS should be called or not.

-Matthias



>
>
> Le 18/04/2016 09:27, Matthias Wessendorf a ?crit :
>
> Hi Yves,
>
> On Mon, Apr 18, 2016 at 9:15 AM, Yves Nicolas <yves.nicolas at dynamease.com>
> wrote:
>
>> API deletion is ok. Use case for deletion by Alias : Java written
>> backoffice doesnt know about device tokens, we want to be able to
>> deregister users from the backoffice. API management, or from the java
>> library. our other use case for unregistration are from the devices
>> themselves, they know about the token. We can manage with the Rest api,
>>
>
> Or, you can use this nice library that a different AeroGear user created!
>
> https://github.com/mfischelmayer/aerogear-push-helper/blob/master/src/main/java/at/ftec/aerogear/api/impl/DefaultAerogearAdminService.java#L152-L159
>
>
>
>
>> is there a plan to include the unregistration inside the android and IOS
>> library?
>
>
> Android:
> there is this method:
>
> https://github.com/aerogear/aerogear-android-push/blob/master/aerogear-android-push/src/main/java/org/jboss/aerogear/android/unifiedpush/PushRegistrar.java#L40
>
> which does both:
> * 'unregister' from the GCM service, as well as from the UPS.
>
> Perhaps that's something you can leverage ?
>
>
> On iOS, we don't have this, because Apple does not recommend to have users
> manually unregister from push on the app. Their preferred way is disabling
> push on the global setting.
>
> However, I think it's arguable that unregistering from UPS, for an app, is
> not equals to completely unregister from APNs, for the same app. Worth to
> explore this on a different thread  :-)
>
>
>
>> Thxs Message: 3 Date: Fri, 15 Apr 2016 19:18:47 +0200 From:
>> Matthias Wessendorf <matzew at apache.org> Subject: Re: [Aerogear-users]
>> what is the good way to delete an alias entry in aerogear unified push
>> servers To: "aerogear-users at lists.jboss.org"
>> <aerogear-users at lists.jboss.org> Message-ID:
>> <CAAg5f2QR0MZ9nk1GjxMpHwNd6Zu_o7DrhAURO9yKJP+9O66R8w at mail.gmail.com>
>> Content-Type: text/plain; charset="utf-8" remove the entire installation
>> entry:
>>
>> https://aerogear.org/docs/specs/aerogear-unifiedpush-rest/index.html#417932897
>> what's the use-case - perhaps we can improve our story? On Fri, Apr 15,
>> 2016 at 6:09 PM, Yves Nicolas < <yves.nicolas at dynamease.com>
>> yves.nicolas at dynamease.com> wrote:
>>
>> > The user interface enable to uncheck the alias so that it doesn't
>> > receive notification anymore but what is the good way to delete the
>> > alias/device token from the aerogear database?
>> >
>> > Thanks
>> > Yves
>> >
>> > _______________________________________________
>> > Aerogear-users mailing list
>> > Aerogear-users at lists.jboss.org
>> > https://lists.jboss.org/mailman/listinfo/aerogear-users
>> >
>> _______________________________________________
>> 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 listAerogear-users at lists.jboss.orghttps://lists.jboss.org/mailman/listinfo/aerogear-users
>
>
>
> _______________________________________________
> 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-users/attachments/20160418/bd8373b4/attachment.html 

From matzew at apache.org  Mon Apr 18 06:51:01 2016
From: matzew at apache.org (Matthias Wessendorf)
Date: Mon, 18 Apr 2016 12:51:01 +0200
Subject: [Aerogear-users] what is the good way to delete an alias,
 entry in aerogear unified push servers
In-Reply-To: <CAAg5f2RPA6Y_+9gwPgdyD3On+NDo-JA_i4Jv2=JJ0PBLQKyoiw@mail.gmail.com>
References: <5714899D.5020805@dynamease.com>
	<CAAg5f2TfLZt=nH8R84GuUPQU-3YLbf5jrnqm=qTfwtVe-PXrdg@mail.gmail.com>
	<57148DF0.4020805@dynamease.com>
	<CAAg5f2RPA6Y_+9gwPgdyD3On+NDo-JA_i4Jv2=JJ0PBLQKyoiw@mail.gmail.com>
Message-ID: <CAAg5f2SA3kCCD4bbU71H5BvgWfqh5qwQ8oj9=WpBKkogzbQtmA@mail.gmail.com>

There is one more thing:

Since the users might decide to unregister at any point of lifetime in the
app, the app also has to know the token, in order to actually perform that
HTTP_DELETE


On Mon, Apr 18, 2016 at 9:53 AM, Matthias Wessendorf <matzew at apache.org>
wrote:

>
>
> On Mon, Apr 18, 2016 at 9:34 AM, Yves Nicolas <yves.nicolas at dynamease.com>
> wrote:
>
>> looks good, will try the aerogear push helper from mfischelmayer.
>> Was actually aware for the Android one, looking for the equivalent in
>> Apple.
>> Definitely agree with you regarding the difference, it makes sense for
>> the App to keep being registered at the APN level (user doesnt need to
>> authorize the remote notifications again) but we want the user to be
>> unregistered from the server, although this is not a high priority use case.
>>
>
> There are a few things we need to be aware of:
> * when app issues such an unregister call, the UPS won't be sending push
> notifications
> * each launch of the application will hit
> 'application:didRegisterForRemoteNotificationsWithDeviceToken', meaning the
> previously removed token will be readded. Local state on the app needs to
> be around, to deviced if the registration w/ UPS should be called or not.
>
> -Matthias
>
>
>
>>
>>
>> Le 18/04/2016 09:27, Matthias Wessendorf a ?crit :
>>
>> Hi Yves,
>>
>> On Mon, Apr 18, 2016 at 9:15 AM, Yves Nicolas <yves.nicolas at dynamease.com
>> > wrote:
>>
>>> API deletion is ok. Use case for deletion by Alias : Java written
>>> backoffice doesnt know about device tokens, we want to be able to
>>> deregister users from the backoffice. API management, or from the java
>>> library. our other use case for unregistration are from the devices
>>> themselves, they know about the token. We can manage with the Rest api,
>>>
>>
>> Or, you can use this nice library that a different AeroGear user created!
>>
>> https://github.com/mfischelmayer/aerogear-push-helper/blob/master/src/main/java/at/ftec/aerogear/api/impl/DefaultAerogearAdminService.java#L152-L159
>>
>>
>>
>>
>>> is there a plan to include the unregistration inside the android and IOS
>>> library?
>>
>>
>> Android:
>> there is this method:
>>
>> https://github.com/aerogear/aerogear-android-push/blob/master/aerogear-android-push/src/main/java/org/jboss/aerogear/android/unifiedpush/PushRegistrar.java#L40
>>
>> which does both:
>> * 'unregister' from the GCM service, as well as from the UPS.
>>
>> Perhaps that's something you can leverage ?
>>
>>
>> On iOS, we don't have this, because Apple does not recommend to have
>> users manually unregister from push on the app. Their preferred way is
>> disabling push on the global setting.
>>
>> However, I think it's arguable that unregistering from UPS, for an app,
>> is not equals to completely unregister from APNs, for the same app. Worth
>> to explore this on a different thread  :-)
>>
>>
>>
>>> Thxs Message: 3 Date: Fri, 15 Apr 2016 19:18:47 +0200 From:
>>> Matthias Wessendorf <matzew at apache.org> Subject: Re: [Aerogear-users]
>>> what is the good way to delete an alias entry in aerogear unified push
>>> servers To: "aerogear-users at lists.jboss.org"
>>> <aerogear-users at lists.jboss.org> Message-ID:
>>> <CAAg5f2QR0MZ9nk1GjxMpHwNd6Zu_o7DrhAURO9yKJP+9O66R8w at mail.gmail.com>
>>> Content-Type: text/plain; charset="utf-8" remove the entire installation
>>> entry:
>>>
>>> https://aerogear.org/docs/specs/aerogear-unifiedpush-rest/index.html#417932897
>>> what's the use-case - perhaps we can improve our story? On Fri, Apr 15,
>>> 2016 at 6:09 PM, Yves Nicolas < <yves.nicolas at dynamease.com>
>>> yves.nicolas at dynamease.com> wrote:
>>>
>>> > The user interface enable to uncheck the alias so that it doesn't
>>> > receive notification anymore but what is the good way to delete the
>>> > alias/device token from the aerogear database?
>>> >
>>> > Thanks
>>> > Yves
>>> >
>>> > _______________________________________________
>>> > Aerogear-users mailing list
>>> > Aerogear-users at lists.jboss.org
>>> > https://lists.jboss.org/mailman/listinfo/aerogear-users
>>> >
>>> _______________________________________________
>>> 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 listAerogear-users at lists.jboss.orghttps://lists.jboss.org/mailman/listinfo/aerogear-users
>>
>>
>>
>> _______________________________________________
>> 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
>



-- 
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-users/attachments/20160418/9e9b3db3/attachment-0001.html 

From matzew at apache.org  Mon Apr 18 06:53:46 2016
From: matzew at apache.org (Matthias Wessendorf)
Date: Mon, 18 Apr 2016 12:53:46 +0200
Subject: [Aerogear-users] what is the good way to delete an alias,
 entry in aerogear unified push servers
In-Reply-To: <CAAg5f2SA3kCCD4bbU71H5BvgWfqh5qwQ8oj9=WpBKkogzbQtmA@mail.gmail.com>
References: <5714899D.5020805@dynamease.com>
	<CAAg5f2TfLZt=nH8R84GuUPQU-3YLbf5jrnqm=qTfwtVe-PXrdg@mail.gmail.com>
	<57148DF0.4020805@dynamease.com>
	<CAAg5f2RPA6Y_+9gwPgdyD3On+NDo-JA_i4Jv2=JJ0PBLQKyoiw@mail.gmail.com>
	<CAAg5f2SA3kCCD4bbU71H5BvgWfqh5qwQ8oj9=WpBKkogzbQtmA@mail.gmail.com>
Message-ID: <CAAg5f2T=MghwSznznEr=Yb_XkCK+Y_JSExJ4JBUpfPCMeiGqEg@mail.gmail.com>

In the mean time, I've create a JIRA to track this:
https://issues.jboss.org/browse/AGIOS-487

-Matthias

On Mon, Apr 18, 2016 at 12:51 PM, Matthias Wessendorf <matzew at apache.org>
wrote:

> There is one more thing:
>
> Since the users might decide to unregister at any point of lifetime in the
> app, the app also has to know the token, in order to actually perform that
> HTTP_DELETE
>
>
> On Mon, Apr 18, 2016 at 9:53 AM, Matthias Wessendorf <matzew at apache.org>
> wrote:
>
>>
>>
>> On Mon, Apr 18, 2016 at 9:34 AM, Yves Nicolas <yves.nicolas at dynamease.com
>> > wrote:
>>
>>> looks good, will try the aerogear push helper from mfischelmayer.
>>> Was actually aware for the Android one, looking for the equivalent in
>>> Apple.
>>> Definitely agree with you regarding the difference, it makes sense for
>>> the App to keep being registered at the APN level (user doesnt need to
>>> authorize the remote notifications again) but we want the user to be
>>> unregistered from the server, although this is not a high priority use case.
>>>
>>
>> There are a few things we need to be aware of:
>> * when app issues such an unregister call, the UPS won't be sending push
>> notifications
>> * each launch of the application will hit
>> 'application:didRegisterForRemoteNotificationsWithDeviceToken', meaning the
>> previously removed token will be readded. Local state on the app needs to
>> be around, to deviced if the registration w/ UPS should be called or not.
>>
>> -Matthias
>>
>>
>>
>>>
>>>
>>> Le 18/04/2016 09:27, Matthias Wessendorf a ?crit :
>>>
>>> Hi Yves,
>>>
>>> On Mon, Apr 18, 2016 at 9:15 AM, Yves Nicolas <
>>> yves.nicolas at dynamease.com> wrote:
>>>
>>>> API deletion is ok. Use case for deletion by Alias : Java written
>>>> backoffice doesnt know about device tokens, we want to be able to
>>>> deregister users from the backoffice. API management, or from the java
>>>> library. our other use case for unregistration are from the devices
>>>> themselves, they know about the token. We can manage with the Rest api,
>>>>
>>>
>>> Or, you can use this nice library that a different AeroGear user created!
>>>
>>> https://github.com/mfischelmayer/aerogear-push-helper/blob/master/src/main/java/at/ftec/aerogear/api/impl/DefaultAerogearAdminService.java#L152-L159
>>>
>>>
>>>
>>>
>>>> is there a plan to include the unregistration inside the android and IOS
>>>> library?
>>>
>>>
>>> Android:
>>> there is this method:
>>>
>>> https://github.com/aerogear/aerogear-android-push/blob/master/aerogear-android-push/src/main/java/org/jboss/aerogear/android/unifiedpush/PushRegistrar.java#L40
>>>
>>> which does both:
>>> * 'unregister' from the GCM service, as well as from the UPS.
>>>
>>> Perhaps that's something you can leverage ?
>>>
>>>
>>> On iOS, we don't have this, because Apple does not recommend to have
>>> users manually unregister from push on the app. Their preferred way is
>>> disabling push on the global setting.
>>>
>>> However, I think it's arguable that unregistering from UPS, for an app,
>>> is not equals to completely unregister from APNs, for the same app. Worth
>>> to explore this on a different thread  :-)
>>>
>>>
>>>
>>>> Thxs Message: 3 Date: Fri, 15 Apr 2016 19:18:47 +0200 From:
>>>> Matthias Wessendorf <matzew at apache.org> Subject: Re: [Aerogear-users]
>>>> what is the good way to delete an alias entry in aerogear unified push
>>>> servers To: "aerogear-users at lists.jboss.org"
>>>> <aerogear-users at lists.jboss.org> Message-ID:
>>>> <CAAg5f2QR0MZ9nk1GjxMpHwNd6Zu_o7DrhAURO9yKJP+9O66R8w at mail.gmail.com>
>>>> Content-Type: text/plain; charset="utf-8" remove the entire installation
>>>> entry:
>>>>
>>>> https://aerogear.org/docs/specs/aerogear-unifiedpush-rest/index.html#417932897
>>>> what's the use-case - perhaps we can improve our story? On Fri, Apr 15,
>>>> 2016 at 6:09 PM, Yves Nicolas < <yves.nicolas at dynamease.com>
>>>> yves.nicolas at dynamease.com> wrote:
>>>>
>>>> > The user interface enable to uncheck the alias so that it doesn't
>>>> > receive notification anymore but what is the good way to delete the
>>>> > alias/device token from the aerogear database?
>>>> >
>>>> > Thanks
>>>> > Yves
>>>> >
>>>> > _______________________________________________
>>>> > Aerogear-users mailing list
>>>> > Aerogear-users at lists.jboss.org
>>>> > https://lists.jboss.org/mailman/listinfo/aerogear-users
>>>> >
>>>> _______________________________________________
>>>> 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 listAerogear-users at lists.jboss.orghttps://lists.jboss.org/mailman/listinfo/aerogear-users
>>>
>>>
>>>
>>> _______________________________________________
>>> 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
>>
>
>
>
> --
> 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-users/attachments/20160418/33b6ba6c/attachment.html 

From matzew at apache.org  Mon Apr 18 10:30:11 2016
From: matzew at apache.org (Matthias Wessendorf)
Date: Mon, 18 Apr 2016 16:30:11 +0200
Subject: [Aerogear-users] categories have been hijacked
In-Reply-To: <CAEQz2CtP05sMHyyLJPJEptuvD0uZc_=jw+0FUnYNMY4bxWg4Nw@mail.gmail.com>
References: <2024c7a2507b42e9b175e8dc81ca11fa@stantz.qantel.com>
	<CAEQz2CsB+=s0ch3Ky3fpsVMJE2St+sCwNzxbdccdXNofUFLs9g@mail.gmail.com>
	<352f01dee6a845b3ba73d29be8968e11@stantz.qantel.com>
	<CAEQz2CtP05sMHyyLJPJEptuvD0uZc_=jw+0FUnYNMY4bxWg4Nw@mail.gmail.com>
Message-ID: <CAAg5f2RZC+42XDERVvgy+5M2rHBroOj15xt49fvncceeQAy2gA@mail.gmail.com>

Coming back to this, after a loooooooooooooong, looooooong time...


---------- Forwarded message ----------
From: Summers Pittman <supittma at redhat.com>
Date: Tue, Aug 11, 2015 at 2:31 PM
Subject: Re: [Aerogear-users] categories have been hijacked
To: aerogear-users at lists.jboss.org




On Tue, Aug 11, 2015 at 12:43 AM, Kelvin Lunsford <kelvin at qantel.com> wrote:

> Hi Summers,
>
> GCM topic messages go to all devices registered for the topic. Topic
> notifications cannot be restricted to an alias or list of aliases.
>
> The way it worked before, and still works on ios, you can send a command
> to UPS with an "alias" name AND a "categories" name and it will only go to
> devices that have registered using that "alias" name AND that "categories"
> name.  UPS finds which devices meet the selection criteria and push
> notification requests are sent for those devices.
>
> Requests with aliases and categories can target specific users in a group.
>
> With real "categories" you can segment users into groups, so every device
> can be assigned a category, and sub-groups can be defined by using more
> than one category per device.  This is useful for geographic or
> organizational targeting.
>
> I have no problem with GCM topics. Just make it a new feature.  Give me
> back my categories.
>

So the goal isn't to replace or hijack categories with topics. The goal is
to leverage Google's API fully and transparently to the UPS user so that we
make fewer calls and provide a better experience.  You have some great use
cases that haven't been brought up.  Keep in mind that the PRs open right
now are a "first draft" of the technology.



NOTE: Between Google IO 2015 and now, April 2016, there was a change on
topics: No more limitations of subscribed devices! Before it was limited to
1 million.

Now, this also means options :-) We could just auto register each android
device to one topic (e.g. /topics/VARIANT_ID), *IF* there is no category
provided!

Regarding the concerns, to 'alias' or any other criteria, my understanding
is that, for now, we just use GCM topic only if nothing else, than the
category is provided to the RESTful Sender API.

However, we could extend our Device Group feature, and kinda group all
devices to a users group, and have the category play in there too. E.g.
have some groups like:
* matthias_football
* matthias_music
but the sending here, would be a message to a device group, not a category

-Matthias




  Feel free to join in on the discussion about topics on aerogear-dev.  It
is really important we do this right and I think you can help with that.

Summers


> - Kelvin
>
>
>
> ---------------------------------------------------------------------------------------
> From: aerogear-users-bounces at lists.jboss.org [mailto:
> aerogear-users-bounces at lists.jboss.org] On Behalf Of Summers Pittman
> Sent: Monday, August 10, 2015 6:12 PM
> To: aerogear-users at lists.jboss.org
> Subject: Re: [Aerogear-users] categories have been hijacked
>
>
> >
> >On Mon, Aug 10, 2015 at 8:36 PM, Kelvin Lunsford <kelvin at qantel.com>
> wrote:
> >Setting "categories" in the push payload was working for android and ios
> in cordova push plugin 1.1.1.
> >
> >For version 2.0.2 "categories" only works for ios.
> >
> >It looks like "categories" is being hijacked in android for a GCM feature
> called "topics".
> >
> >I liked "categories".  I was using it.  Now it's gone.  GCM topics is not
> a drop-in replacement.  It's not the same thing.
>
> What do categories do that topics do not do?
>
> >New features should get new names and new commands.
> >
> >- Kelvin
>
>
> _______________________________________________
> Aerogear-users mailing list
> Aerogear-users at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-users
>


_______________________________________________
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-users/attachments/20160418/66a08b7e/attachment-0001.html 

From supittma at redhat.com  Mon Apr 18 11:17:07 2016
From: supittma at redhat.com (Summers Pittman)
Date: Mon, 18 Apr 2016 11:17:07 -0400
Subject: [Aerogear-users] categories have been hijacked
In-Reply-To: <CAAg5f2RZC+42XDERVvgy+5M2rHBroOj15xt49fvncceeQAy2gA@mail.gmail.com>
References: <2024c7a2507b42e9b175e8dc81ca11fa@stantz.qantel.com>
	<CAEQz2CsB+=s0ch3Ky3fpsVMJE2St+sCwNzxbdccdXNofUFLs9g@mail.gmail.com>
	<352f01dee6a845b3ba73d29be8968e11@stantz.qantel.com>
	<CAEQz2CtP05sMHyyLJPJEptuvD0uZc_=jw+0FUnYNMY4bxWg4Nw@mail.gmail.com>
	<CAAg5f2RZC+42XDERVvgy+5M2rHBroOj15xt49fvncceeQAy2gA@mail.gmail.com>
Message-ID: <CAEQz2Cs4Lf9F-trPqm4oh7c01sejfhhEqiK23ptnWxp1n22haw@mail.gmail.com>

On Mon, Apr 18, 2016 at 10:30 AM, Matthias Wessendorf <matzew at apache.org>
wrote:

> Coming back to this, after a loooooooooooooong, looooooong time...
>
>
> ---------- Forwarded message ----------
> From: Summers Pittman <supittma at redhat.com>
> Date: Tue, Aug 11, 2015 at 2:31 PM
> Subject: Re: [Aerogear-users] categories have been hijacked
> To: aerogear-users at lists.jboss.org
>
>
>
>
> On Tue, Aug 11, 2015 at 12:43 AM, Kelvin Lunsford <kelvin at qantel.com>
> wrote:
>
>> Hi Summers,
>>
>> GCM topic messages go to all devices registered for the topic. Topic
>> notifications cannot be restricted to an alias or list of aliases.
>>
>> The way it worked before, and still works on ios, you can send a command
>> to UPS with an "alias" name AND a "categories" name and it will only go to
>> devices that have registered using that "alias" name AND that "categories"
>> name.  UPS finds which devices meet the selection criteria and push
>> notification requests are sent for those devices.
>>
>> Requests with aliases and categories can target specific users in a group.
>>
>> With real "categories" you can segment users into groups, so every device
>> can be assigned a category, and sub-groups can be defined by using more
>> than one category per device.  This is useful for geographic or
>> organizational targeting.
>>
>> I have no problem with GCM topics. Just make it a new feature.  Give me
>> back my categories.
>>
>
> So the goal isn't to replace or hijack categories with topics. The goal is
> to leverage Google's API fully and transparently to the UPS user so that we
> make fewer calls and provide a better experience.  You have some great use
> cases that haven't been brought up.  Keep in mind that the PRs open right
> now are a "first draft" of the technology.
>
>
>
> NOTE: Between Google IO 2015 and now, April 2016, there was a change on
> topics: No more limitations of subscribed devices! Before it was limited to
> 1 million.
>
> Now, this also means options :-) We could just auto register each android
> device to one topic (e.g. /topics/VARIANT_ID), *IF* there is no category
> provided!
>

I think you mean always register a device to a variant specific topic.
That way we can send all Android GCM users a message with one push message
from the push server.


>
> Regarding the concerns, to 'alias' or any other criteria, my understanding
> is that, for now, we just use GCM topic only if nothing else, than the
> category is provided to the RESTful Sender API.
>
> However, we could extend our Device Group feature, and kinda group all
> devices to a users group, and have the category play in there too. E.g.
> have some groups like:
> * matthias_football
> * matthias_music
> but the sending here, would be a message to a device group, not a category
>
> -Matthias
>
>
>
>
>   Feel free to join in on the discussion about topics on aerogear-dev.  It
> is really important we do this right and I think you can help with that.
>
> Summers
>
>
>> - Kelvin
>>
>>
>>
>> ---------------------------------------------------------------------------------------
>> From: aerogear-users-bounces at lists.jboss.org [mailto:
>> aerogear-users-bounces at lists.jboss.org] On Behalf Of Summers Pittman
>> Sent: Monday, August 10, 2015 6:12 PM
>> To: aerogear-users at lists.jboss.org
>> Subject: Re: [Aerogear-users] categories have been hijacked
>>
>>
>> >
>> >On Mon, Aug 10, 2015 at 8:36 PM, Kelvin Lunsford <kelvin at qantel.com>
>> wrote:
>> >Setting "categories" in the push payload was working for android and ios
>> in cordova push plugin 1.1.1.
>> >
>> >For version 2.0.2 "categories" only works for ios.
>> >
>> >It looks like "categories" is being hijacked in android for a GCM
>> feature called "topics".
>> >
>> >I liked "categories".  I was using it.  Now it's gone.  GCM topics is
>> not a drop-in replacement.  It's not the same thing.
>>
>> What do categories do that topics do not do?
>>
>> >New features should get new names and new commands.
>> >
>> >- Kelvin
>>
>>
>> _______________________________________________
>> Aerogear-users mailing list
>> Aerogear-users at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-users
>>
>
>
> _______________________________________________
> 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
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20160418/50588f92/attachment.html 

From matzew at apache.org  Mon Apr 18 11:23:06 2016
From: matzew at apache.org (Matthias Wessendorf)
Date: Mon, 18 Apr 2016 17:23:06 +0200
Subject: [Aerogear-users] categories have been hijacked
In-Reply-To: <CAEQz2Cs4Lf9F-trPqm4oh7c01sejfhhEqiK23ptnWxp1n22haw@mail.gmail.com>
References: <2024c7a2507b42e9b175e8dc81ca11fa@stantz.qantel.com>
	<CAEQz2CsB+=s0ch3Ky3fpsVMJE2St+sCwNzxbdccdXNofUFLs9g@mail.gmail.com>
	<352f01dee6a845b3ba73d29be8968e11@stantz.qantel.com>
	<CAEQz2CtP05sMHyyLJPJEptuvD0uZc_=jw+0FUnYNMY4bxWg4Nw@mail.gmail.com>
	<CAAg5f2RZC+42XDERVvgy+5M2rHBroOj15xt49fvncceeQAy2gA@mail.gmail.com>
	<CAEQz2Cs4Lf9F-trPqm4oh7c01sejfhhEqiK23ptnWxp1n22haw@mail.gmail.com>
Message-ID: <CAAg5f2Qf-q1ufZxScx=FeRXLeoP9s37Smzj02XgcZg0RhMB68A@mail.gmail.com>

On Mon, Apr 18, 2016 at 5:17 PM, Summers Pittman <supittma at redhat.com>
wrote:

>
>
> On Mon, Apr 18, 2016 at 10:30 AM, Matthias Wessendorf <matzew at apache.org>
> wrote:
>
>> Coming back to this, after a loooooooooooooong, looooooong time...
>>
>>
>> ---------- Forwarded message ----------
>> From: Summers Pittman <supittma at redhat.com>
>> Date: Tue, Aug 11, 2015 at 2:31 PM
>> Subject: Re: [Aerogear-users] categories have been hijacked
>> To: aerogear-users at lists.jboss.org
>>
>>
>>
>>
>> On Tue, Aug 11, 2015 at 12:43 AM, Kelvin Lunsford <kelvin at qantel.com>
>> wrote:
>>
>>> Hi Summers,
>>>
>>> GCM topic messages go to all devices registered for the topic. Topic
>>> notifications cannot be restricted to an alias or list of aliases.
>>>
>>> The way it worked before, and still works on ios, you can send a command
>>> to UPS with an "alias" name AND a "categories" name and it will only go to
>>> devices that have registered using that "alias" name AND that "categories"
>>> name.  UPS finds which devices meet the selection criteria and push
>>> notification requests are sent for those devices.
>>>
>>> Requests with aliases and categories can target specific users in a
>>> group.
>>>
>>> With real "categories" you can segment users into groups, so every
>>> device can be assigned a category, and sub-groups can be defined by using
>>> more than one category per device.  This is useful for geographic or
>>> organizational targeting.
>>>
>>> I have no problem with GCM topics. Just make it a new feature.  Give me
>>> back my categories.
>>>
>>
>> So the goal isn't to replace or hijack categories with topics. The goal
>> is to leverage Google's API fully and transparently to the UPS user so that
>> we make fewer calls and provide a better experience.  You have some great
>> use cases that haven't been brought up.  Keep in mind that the PRs open
>> right now are a "first draft" of the technology.
>>
>>
>>
>> NOTE: Between Google IO 2015 and now, April 2016, there was a change on
>> topics: No more limitations of subscribed devices! Before it was limited to
>> 1 million.
>>
>> Now, this also means options :-) We could just auto register each android
>> device to one topic (e.g. /topics/VARIANT_ID), *IF* there is no category
>> provided!
>>
>
> I think you mean always register a device to a variant specific topic.
>


yes, that's what I mean



> That way we can send all Android GCM users a message with one push message
> from the push server.
>

right


>
>
>>
>> Regarding the concerns, to 'alias' or any other criteria, my
>> understanding is that, for now, we just use GCM topic only if nothing else,
>> than the category is provided to the RESTful Sender API.
>>
>> However, we could extend our Device Group feature, and kinda group all
>> devices to a users group, and have the category play in there too. E.g.
>> have some groups like:
>> * matthias_football
>> * matthias_music
>> but the sending here, would be a message to a device group, not a category
>>
>> -Matthias
>>
>>
>>
>>
>>   Feel free to join in on the discussion about topics on aerogear-dev.
>> It is really important we do this right and I think you can help with that.
>>
>> Summers
>>
>>
>>> - Kelvin
>>>
>>>
>>>
>>> ---------------------------------------------------------------------------------------
>>> From: aerogear-users-bounces at lists.jboss.org [mailto:
>>> aerogear-users-bounces at lists.jboss.org] On Behalf Of Summers Pittman
>>> Sent: Monday, August 10, 2015 6:12 PM
>>> To: aerogear-users at lists.jboss.org
>>> Subject: Re: [Aerogear-users] categories have been hijacked
>>>
>>>
>>> >
>>> >On Mon, Aug 10, 2015 at 8:36 PM, Kelvin Lunsford <kelvin at qantel.com>
>>> wrote:
>>> >Setting "categories" in the push payload was working for android and
>>> ios in cordova push plugin 1.1.1.
>>> >
>>> >For version 2.0.2 "categories" only works for ios.
>>> >
>>> >It looks like "categories" is being hijacked in android for a GCM
>>> feature called "topics".
>>> >
>>> >I liked "categories".  I was using it.  Now it's gone.  GCM topics is
>>> not a drop-in replacement.  It's not the same thing.
>>>
>>> What do categories do that topics do not do?
>>>
>>> >New features should get new names and new commands.
>>> >
>>> >- Kelvin
>>>
>>>
>>> _______________________________________________
>>> Aerogear-users mailing list
>>> Aerogear-users at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-users
>>>
>>
>>
>> _______________________________________________
>> 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
>>
>>
>
> _______________________________________________
> 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-users/attachments/20160418/d12d9b38/attachment-0001.html 

From henry.hertoghe at gmail.com  Mon Apr 18 18:05:21 2016
From: henry.hertoghe at gmail.com (hh)
Date: Mon, 18 Apr 2016 15:05:21 -0700 (MST)
Subject: [Aerogear-users] Get the deviceToken - Android
Message-ID: <1461017121084-619.post@n5.nabble.com>

Hey All,

how can we retrieve the deviceToken in Android?

It seems impossible to be done, and I need it to unregister the device (API
call needs the deviceToken).

Thanks for your help,

Kr,

Henry



--
View this message in context: http://aerogear-users.1116366.n5.nabble.com/Get-the-deviceToken-Android-tp619.html
Sent from the aerogear-users mailing list archive at Nabble.com.

From dpassos at redhat.com  Tue Apr 19 08:30:07 2016
From: dpassos at redhat.com (Daniel Passos)
Date: Tue, 19 Apr 2016 09:30:07 -0300
Subject: [Aerogear-users] Get the deviceToken - Android
In-Reply-To: <1461017121084-619.post@n5.nabble.com>
References: <1461017121084-619.post@n5.nabble.com>
Message-ID: <CADF=h2ss2DFoOQzB041hh3FwoGpzRAWx8mi6PKrwCpy4i9o5zQ@mail.gmail.com>

Hi,

deviceToken is not exposed in AeroGear Android lib, anyway you can
unregister a device using the unregister[1][2] method.

[1]
https://github.com/aerogear/aerogear-android-push/blob/master/aerogear-android-push/src/main/java/org/jboss/aerogear/android/unifiedpush/PushRegistrar.java#L40
[2]
https://github.com/aerogear/aerogear-android-push/blob/master/aerogear-android-push/src/main/java/org/jboss/aerogear/android/unifiedpush/gcm/AeroGearGCMPushRegistrar.java#L209-L265


On Mon, Apr 18, 2016 at 7:05 PM, hh <henry.hertoghe at gmail.com> wrote:

> Hey All,
>
> how can we retrieve the deviceToken in Android?
>
> It seems impossible to be done, and I need it to unregister the device (API
> call needs the deviceToken).
>
> Thanks for your help,
>
> Kr,
>
> Henry
>
>
>
> --
> View this message in context:
> http://aerogear-users.1116366.n5.nabble.com/Get-the-deviceToken-Android-tp619.html
> Sent from the aerogear-users mailing list archive at Nabble.com.
> _______________________________________________
> Aerogear-users mailing list
> Aerogear-users at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-users
>



-- 
-- Passos
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20160419/82fcd115/attachment.html 

From henry.hertoghe at gmail.com  Tue Apr 19 09:48:10 2016
From: henry.hertoghe at gmail.com (hh)
Date: Tue, 19 Apr 2016 06:48:10 -0700 (MST)
Subject: [Aerogear-users] Get the deviceToken - Android
In-Reply-To: <CADF=h2ss2DFoOQzB041hh3FwoGpzRAWx8mi6PKrwCpy4i9o5zQ@mail.gmail.com>
References: <1461017121084-619.post@n5.nabble.com>
	<CADF=h2ss2DFoOQzB041hh3FwoGpzRAWx8mi6PKrwCpy4i9o5zQ@mail.gmail.com>
Message-ID: <1461073690573-621.post@n5.nabble.com>

Hi Daniel,

Thanks for your reply.

I knew about the "unregister" method but it didn't do his job perfectly, as
sometimes it wasn't unregistered and I had the following block & error which
where throwed.

 if ((deviceToken == null) || (deviceToken.trim().equals(""))) {
                        throw new
IllegalStateException(DEVICE_ALREADY_UNREGISTERED);
 }

But my device was still registered, so I don't really understand why this
error was throwed.

Probably, the deviceToken is null, as for the register method, we have the
following:

 if (instanceId == null) {
                        instanceId = instanceIdProvider.get(context);
                    }
                    String token = instanceId.getToken(senderId,
                                                   
GoogleCloudMessaging.INSTANCE_ID_SCOPE);
                    
                    deviceToken = token;



while for the unregister method there is nothing, so I don't see how the
deviceToken could not be null?

Thanks,

Henry



--
View this message in context: http://aerogear-users.1116366.n5.nabble.com/Get-the-deviceToken-Android-tp619p621.html
Sent from the aerogear-users mailing list archive at Nabble.com.

From supittma at redhat.com  Tue Apr 19 12:31:31 2016
From: supittma at redhat.com (Summers Pittman)
Date: Tue, 19 Apr 2016 12:31:31 -0400
Subject: [Aerogear-users] Get the deviceToken - Android
In-Reply-To: <1461073690573-621.post@n5.nabble.com>
References: <1461017121084-619.post@n5.nabble.com>
	<CADF=h2ss2DFoOQzB041hh3FwoGpzRAWx8mi6PKrwCpy4i9o5zQ@mail.gmail.com>
	<1461073690573-621.post@n5.nabble.com>
Message-ID: <CAEQz2Csm=o9bP8-_rPu-fj_v3NrEAy63w8qFptgOM3NgEuUP_g@mail.gmail.com>

Are you using the same instance of the registrar to register and unregister?

On Tue, Apr 19, 2016 at 9:48 AM, hh <henry.hertoghe at gmail.com> wrote:

> Hi Daniel,
>
> Thanks for your reply.
>
> I knew about the "unregister" method but it didn't do his job perfectly, as
> sometimes it wasn't unregistered and I had the following block & error
> which
> where throwed.
>
>  if ((deviceToken == null) || (deviceToken.trim().equals(""))) {
>                         throw new
> IllegalStateException(DEVICE_ALREADY_UNREGISTERED);
>  }
>
> But my device was still registered, so I don't really understand why this
> error was throwed.
>
> Probably, the deviceToken is null, as for the register method, we have the
> following:
>
>  if (instanceId == null) {
>                         instanceId = instanceIdProvider.get(context);
>                     }
>                     String token = instanceId.getToken(senderId,
>
> GoogleCloudMessaging.INSTANCE_ID_SCOPE);
>
>                     deviceToken = token;
>
>
>
> while for the unregister method there is nothing, so I don't see how the
> deviceToken could not be null?
>
> Thanks,
>
> Henry
>
>
>
> --
> View this message in context:
> http://aerogear-users.1116366.n5.nabble.com/Get-the-deviceToken-Android-tp619p621.html
> Sent from the aerogear-users mailing list archive at Nabble.com.
> _______________________________________________
> 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-users/attachments/20160419/de004dc1/attachment.html 

From ibmoreno.cba at gmail.com  Sun Apr 24 14:35:07 2016
From: ibmoreno.cba at gmail.com (ibmoreno)
Date: Sun, 24 Apr 2016 11:35:07 -0700 (MST)
Subject: [Aerogear-users] NullPointerException in Server (error 500) for
	sendMetrics
Message-ID: <1461522907854-623.post@n5.nabble.com>

Hi
I have problem when sending response to the server,
"pushRegistar.sendMetrics" 500 error on the server. NullPointerException
error in
classorg.jboss.aerogear.unifiedpush.service.metrics.PushMessageMetricsService.updateAnalytics(PushMessageMetricsService.java:159).
What I might be missing?

Error im server:

2016-04-24 12:33:50,358 ERROR [io.undertow.request] (default task-44)
UT005023: Exception handling request to
/ag-push/rest/registry/device/pushMessage/e2bd21d9-1d44-40e1-8761-4f078bb2f61a:
org.jboss.resteasy.spi.UnhandledException: javax.ejb.EJBException:
java.lang.NullPointerException
	at
org.jboss.resteasy.core.ExceptionHandler.handleApplicationException(ExceptionHandler.java:76)
	at
org.jboss.resteasy.core.ExceptionHandler.handleException(ExceptionHandler.java:212)
	at
org.jboss.resteasy.core.SynchronousDispatcher.writeException(SynchronousDispatcher.java:168)
	at
org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:411)
	at
org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:202)
	at
org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.service(ServletContainerDispatcher.java:221)
	at
org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:56)
	at
org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:51)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
	at
io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:85)
	at
io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:129)
	at
org.jboss.aerogear.unifiedpush.service.filter.HttpContextFilter.doFilter(HttpContextFilter.java:55)
	at io.undertow.servlet.core.ManagedFilter.doFilter(ManagedFilter.java:60)
	at
io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:131)
	at
org.jboss.aerogear.unifiedpush.rest.util.VersionFilter.doFilter(VersionFilter.java:65)
	at io.undertow.servlet.core.ManagedFilter.doFilter(ManagedFilter.java:60)
	at
io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:131)
	at
io.undertow.servlet.handlers.FilterHandler.handleRequest(FilterHandler.java:84)
	at
io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:62)
	at
io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36)
	at
org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:78)
	at
io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
	at
org.keycloak.adapters.undertow.UndertowAuthenticatedActionsHandler.handleRequest(UndertowAuthenticatedActionsHandler.java:66)
	at
org.keycloak.adapters.undertow.UndertowAuthenticatedActionsHandler.handleRequest(UndertowAuthenticatedActionsHandler.java:66)
	at
io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:131)
	at
io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:57)
	at
io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
	at
io.undertow.security.handlers.AuthenticationConstraintHandler.handleRequest(AuthenticationConstraintHandler.java:51)
	at
io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:46)
	at
io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:64)
	at
io.undertow.servlet.handlers.security.ServletSecurityConstraintHandler.handleRequest(ServletSecurityConstraintHandler.java:56)
	at
io.undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:60)
	at
io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:77)
	at
io.undertow.security.handlers.NotificationReceiverHandler.handleRequest(NotificationReceiverHandler.java:50)
	at
io.undertow.security.handlers.AbstractSecurityContextAssociationHandler.handleRequest(AbstractSecurityContextAssociationHandler.java:43)
	at
io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
	at
org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61)
	at
io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
	at
org.keycloak.adapters.undertow.ServletPreAuthActionsHandler.handleRequest(ServletPreAuthActionsHandler.java:69)
	at
org.keycloak.adapters.undertow.ServletPreAuthActionsHandler.handleRequest(ServletPreAuthActionsHandler.java:69)
	at
io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
	at
io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:284)
	at
io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:263)
	at
io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:81)
	at
io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:174)
	at io.undertow.server.Connectors.executeRootHandler(Connectors.java:202)
	at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:793)
	at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	at java.lang.Thread.run(Thread.java:745)
Caused by: javax.ejb.EJBException: java.lang.NullPointerException
	at
org.jboss.as.ejb3.tx.CMTTxInterceptor.handleExceptionInOurTx(CMTTxInterceptor.java:187)
	at
org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:277)
	at
org.jboss.as.ejb3.tx.CMTTxInterceptor.required(CMTTxInterceptor.java:327)
	at
org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:239)
	at
org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
	at
org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41)
	at
org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
	at
org.jboss.as.ejb3.component.invocationmetrics.WaitTimeInterceptor.processInvocation(WaitTimeInterceptor.java:43)
	at
org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
	at
org.jboss.as.ejb3.security.SecurityContextInterceptor.processInvocation(SecurityContextInterceptor.java:100)
	at
org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
	at
org.jboss.as.ejb3.component.interceptors.ShutDownInterceptorFactory$1.processInvocation(ShutDownInterceptorFactory.java:64)
	at
org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
	at
org.jboss.as.ejb3.component.interceptors.LoggingInterceptor.processInvocation(LoggingInterceptor.java:66)
	at
org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
	at
org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50)
	at
org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
	at
org.jboss.as.ejb3.component.interceptors.AdditionalSetupInterceptor.processInvocation(AdditionalSetupInterceptor.java:54)
	at
org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
	at
org.jboss.invocation.ContextClassLoaderInterceptor.processInvocation(ContextClassLoaderInterceptor.java:64)
	at
org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
	at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:356)
	at
org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:636)
	at
org.jboss.invocation.AccessCheckingInterceptor.processInvocation(AccessCheckingInterceptor.java:61)
	at
org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
	at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:356)
	at
org.jboss.invocation.PrivilegedWithCombinerInterceptor.processInvocation(PrivilegedWithCombinerInterceptor.java:80)
	at
org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
	at
org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61)
	at org.jboss.as.ee.component.ViewService$View.invoke(ViewService.java:195)
	at
org.jboss.as.ee.component.ViewDescription$1.processInvocation(ViewDescription.java:185)
	at
org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
	at
org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61)
	at
org.jboss.as.ee.component.ProxyInvocationHandler.invoke(ProxyInvocationHandler.java:73)
	at
org.jboss.aerogear.unifiedpush.service.metrics.PushMessageMetricsService$$$view10.updateAnalytics(Unknown
Source)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at
org.jboss.weld.util.reflection.Reflections.invokeAndUnwrap(Reflections.java:436)
	at
org.jboss.weld.bean.proxy.EnterpriseBeanProxyMethodHandler.invoke(EnterpriseBeanProxyMethodHandler.java:127)
	at
org.jboss.weld.bean.proxy.EnterpriseTargetBeanInstance.invoke(EnterpriseTargetBeanInstance.java:56)
	at
org.jboss.weld.bean.proxy.InjectionPointPropagatingEnterpriseTargetBeanInstance.invoke(InjectionPointPropagatingEnterpriseTargetBeanInstance.java:67)
	at
org.jboss.weld.bean.proxy.ProxyMethodHandler.invoke(ProxyMethodHandler.java:100)
	at
org.jboss.aerogear.unifiedpush.service.metrics.PushMessageMetricsService$Proxy$_$$_Weld$EnterpriseProxy$.updateAnalytics(Unknown
Source)
	at
org.jboss.aerogear.unifiedpush.rest.registry.installations.InstallationRegistrationEndpoint.increasePushMessageReadCounter(InstallationRegistrationEndpoint.java:214)
	at
org.jboss.aerogear.unifiedpush.rest.registry.installations.InstallationRegistrationEndpoint$Proxy$_$$_WeldClientProxy.increasePushMessageReadCounter(Unknown
Source)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at
org.jboss.resteasy.core.MethodInjectorImpl.invoke(MethodInjectorImpl.java:139)
	at
org.jboss.resteasy.core.ResourceMethodInvoker.invokeOnTarget(ResourceMethodInvoker.java:295)
	at
org.jboss.resteasy.core.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:249)
	at
org.jboss.resteasy.core.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:236)
	at
org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:395)
	... 46 more
Caused by: java.lang.NullPointerException
	at
org.jboss.aerogear.unifiedpush.service.metrics.PushMessageMetricsService.updateAnalytics(PushMessageMetricsService.java:159)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at
org.jboss.as.ee.component.ManagedReferenceMethodInterceptor.processInvocation(ManagedReferenceMethodInterceptor.java:52)
	at
org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
	at
org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:437)
	at
org.jboss.as.weld.ejb.Jsr299BindingsInterceptor.doMethodInterception(Jsr299BindingsInterceptor.java:82)
	at
org.jboss.as.weld.ejb.Jsr299BindingsInterceptor.processInvocation(Jsr299BindingsInterceptor.java:93)
	at
org.jboss.as.ee.component.interceptors.UserInterceptorFactory$1.processInvocation(UserInterceptorFactory.java:63)
	at
org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
	at
org.jboss.as.ejb3.component.invocationmetrics.ExecutionTimeInterceptor.processInvocation(ExecutionTimeInterceptor.java:43)
	at
org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
	at
org.jboss.as.jpa.interceptor.SBInvocationInterceptor.processInvocation(SBInvocationInterceptor.java:47)
	at
org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
	at
org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:437)
	at
org.jboss.weld.ejb.AbstractEJBRequestScopeActivationInterceptor.aroundInvoke(AbstractEJBRequestScopeActivationInterceptor.java:64)
	at
org.jboss.as.weld.ejb.EjbRequestScopeActivationInterceptor.processInvocation(EjbRequestScopeActivationInterceptor.java:83)
	at
org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
	at
org.jboss.as.ee.concurrent.ConcurrentContextInterceptor.processInvocation(ConcurrentContextInterceptor.java:45)
	at
org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
	at
org.jboss.invocation.InitialInterceptor.processInvocation(InitialInterceptor.java:21)
	at
org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
	at
org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61)
	at
org.jboss.as.ee.component.interceptors.ComponentDispatcherInterceptor.processInvocation(ComponentDispatcherInterceptor.java:52)
	at
org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
	at
org.jboss.as.ejb3.component.pool.PooledInstanceInterceptor.processInvocation(PooledInstanceInterceptor.java:51)
	at
org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
	at
org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:275)
	... 100 more


android implementation:


 PushApplication application = (PushApplication) getApplication();
        AeroGearGCMPushRegistrar pushRegistar = (AeroGearGCMPushRegistrar)
application.getPushRegistar();

        String pushMessageId =
bundle.getString(UnifiedPushMessage.PUSH_MESSAGE_ID);
        UnifiedPushMetricsMessage pushMetricsMessage = new
UnifiedPushMetricsMessage(pushMessageId);

        pushRegistar.sendMetrics(pushMetricsMessage, new
Callback<UnifiedPushMetricsMessage>() {
            @Override
            public void onSuccess(UnifiedPushMetricsMessage
unifiedPushMetricsMessage) {
                Log.d(TAG, "Metrics for : " +
unifiedPushMetricsMessage.getMessageId() + " successfully sent");
            }

            @Override
            public void onFailure(Exception e) {
                Log.d(TAG, e.getMessage(), e);
            }
        });






--
View this message in context: http://aerogear-users.1116366.n5.nabble.com/NullPointerException-in-Server-error-500-for-sendMetrics-tp623.html
Sent from the aerogear-users mailing list archive at Nabble.com.

From Ashish.Pandita at indegene.com  Thu Apr 28 07:44:05 2016
From: Ashish.Pandita at indegene.com (Ashish Pandita)
Date: Thu, 28 Apr 2016 11:44:05 +0000
Subject: [Aerogear-users] AeroGear SDK integration with Keycloak
Message-ID: <4C1D8037-6EBE-4B33-9EC4-391C68259BD5@indegene.com>

Hi All,

I am having some trouble using aerogear to connect keycloak locally. I am using shoot example I did the following things
1) installed pods on shoot&share https://github.com/aerogear/aerogear-ios-cookbook/tree/0.3.0/Shoot
2) installed the key cloak ver keycloak-1.9.2.Final (https://github.com/aerogear/aerogear-backend-cookbook/tree/master/Shoot) I can access the admin console in browser imported the realm configuration https://github.com/aerogear/aerogear-backend-cookbook/blob/master/Shoot/configuration/shoot-realm.json
3) I run the server attached is the log and here is the terminal rec https://asciinema.org/a/7xhosmb63kn9tnvn99gnh5mbm
4) I am not able to login to keycloak. I am getting errors in console when keycloak launches the web view can you please help what need to be done to resolve it or guide to proper resource.

here is the Aerogear API which I am using

 @IBAction func shareWithKeycloak() {



        let keycloakHost = "http://localhost:8080"
        let keycloakConfig = KeycloakConfig(
            clientId: "shoot-third-party",
            host: keycloakHost,
            realm: "shoot-realm")
        // If you want to use embedded web view uncomment
          keycloakConfig.isWebView = true



        // Workaround issue on Keychain https://forums.developer.apple.com/message/23323
        let gdModule = KeycloakOAuth2Module(config: keycloakConfig, session: UntrustedMemoryOAuth2Session(accountId: "ACCOUNT_FOR_CLIENTID_\(keycloakConfig.clientId)"))



        // let gdModule = AccountManager.addKeycloakAccount(keycloakConfig)
        self.http.authzModule = gdModule
       /* gdModule.login { (response, token, error) in



            print(response)
            print(token)
            print(error)
        } */





         print("Perform photo upload with Keycloak")





       self.performUpload("\(keycloakHost)/shoot/rest/photos", parameters: self.extractImageAsMultipartParams())

    }

    func performUpload(url: String, parameters: [String: AnyObject]?) {





        self.http.request(HttpMethod.POST, path: url, parameters: parameters, credential: nil, responseSerializer: nil) { (response, error) in
            if (error != nil) {
                self.presentAlert("Error", message: error!.localizedDescription)
            } else {
                self.presentAlert("Success", message: "Successfully uploaded!")
            }
        }



        /*



        self.http.POST(url, parameters: parameters, completionHandler: {(response, error) in
            if (error != nil) {
                self.presentAlert("Error", message: error!.localizedDescription)
            } else {
                self.presentAlert("Success", message: "Successfully uploaded!")
            }
        })



            */
    }



Disclaimer : This message and any attachments are solely for the intended recipient and may contain confidential or privileged information. If you are not the intended recipient, any disclosure, copying, use, or distribution of the information included in this message and any attachments is prohibited. If you have received this communication in error, please notify us by reply e-mail to IT at Indegene.com and immediately and permanently delete this message and any attachments. Any views expressed in this mail are not necessarily the views of INDEGENE. Thank you.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20160428/5734a74a/attachment-0001.html 
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: Terminal Saved Output.txt
Url: http://lists.jboss.org/pipermail/aerogear-users/attachments/20160428/5734a74a/attachment-0001.txt 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20160428/5734a74a/attachment-0001.htm 

From dpassos at redhat.com  Thu Apr 28 12:01:02 2016
From: dpassos at redhat.com (Daniel Passos)
Date: Thu, 28 Apr 2016 13:01:02 -0300
Subject: [Aerogear-users] AeroGear SDK integration with Keycloak
In-Reply-To: <4C1D8037-6EBE-4B33-9EC4-391C68259BD5@indegene.com>
References: <4C1D8037-6EBE-4B33-9EC4-391C68259BD5@indegene.com>
Message-ID: <CADF=h2soKNyRo-qfTRfWcwXnkKeB43A08-MspD9H5CaGUPeKEA@mail.gmail.com>

Hi

Are you getting this error when you are firing a request to KC server from
your app?

```

17:01:31,549 ERROR [org.jboss.resteasy.resteasy_jaxrs.i18n] (default
task-1) RESTEASY002010: Failed to execute:
javax.ws.rs.NotFoundException: HTTP 404 Not Found

```

I'm not 100% sure (didn't have time to test) but I think the problem is, KC
1.9.1 are using different endpoints and the iOS app was not updated yet.

Our cookbook backend[1] was updated to 1.9.1 by the community[2] weeks ago

Unfortunately he updated only the Android app[3] to the new endpoints

Can you check the Android PR[3] and see if you change that in the iOS app
it works?

[1] https://github.com/aerogear/aerogear-backend-cookbook/tree/master/Shoot
[2] https://github.com/aerogear/aerogear-backend-cookbook/pull/29
[3] https://github.com/aerogear/aerogear-android-cookbook/pull/56







On Thu, Apr 28, 2016 at 8:44 AM, Ashish Pandita <Ashish.Pandita at indegene.com
> wrote:

> Hi All,
>
> I am having some trouble using aerogear to connect keycloak locally. I am
> using shoot example I did the following things
> 1) installed pods on shoot&share
> https://github.com/aerogear/aerogear-ios-cookbook/tree/0.3.0/Shoot
> 2) installed the key cloak ver keycloak-1.9.2.Final (
> https://github.com/aerogear/aerogear-backend-cookbook/tree/master/Shoot)
> I can access the admin console in browser imported the realm configuration
> https://github.com/aerogear/aerogear-backend-cookbook/blob/master/Shoot/configuration/shoot-realm.json
> 3) I run the server attached is the log and here is the terminal rec
> https://asciinema.org/a/7xhosmb63kn9tnvn99gnh5mbm
> 4) I am not able to login to keycloak. I am getting errors in console when
> keycloak launches the web view can you please help what need to be done to
> resolve it or guide to proper resource.
>
> here is the Aerogear API which I am using
>
>  @IBAction func shareWithKeycloak() {
>
>
>         let keycloakHost = "http://localhost:8080"
>         let keycloakConfig = KeycloakConfig(
>             clientId: "shoot-third-party",
>             host: keycloakHost,
>             realm: "shoot-realm")
>         // If you want to use embedded web view uncomment
>           keycloakConfig.isWebView = true
>
>
>         // Workaround issue on Keychain
> https://forums.developer.apple.com/message/23323
>         let gdModule = KeycloakOAuth2Module(config: keycloakConfig,
> session: UntrustedMemoryOAuth2Session(accountId: "ACCOUNT_FOR_CLIENTID_\(
> keycloakConfig.clientId)"))
>
>
>         // let gdModule =
> AccountManager.addKeycloakAccount(keycloakConfig)
>         self.http.authzModule = gdModule
>        /* gdModule.login { (response, token, error) in
>
>
>             print(response)
>             print(token)
>             print(error)
>         } */
>
>
>
>
>          print("Perform photo upload with Keycloak")
>
>
>
>
>        self.performUpload("\(keycloakHost)/shoot/rest/photos",
> parameters: self.extractImageAsMultipartParams())
>
>     }
>
>     func performUpload(url: String, parameters: [String: AnyObject]?) {
>
>
>
>
>         self.http.request(HttpMethod.POST, path: url, parameters:
> parameters, credential: nil, responseSerializer: nil) { (response, error)
> in
>             if (error != nil) {
>                 self.presentAlert("Error", message: error!.
> localizedDescription)
>             } else {
>                 self.presentAlert("Success", message: "Successfully
> uploaded!")
>             }
>         }
>
>
>         /*
>
>
>         self.http.POST(url, parameters: parameters, completionHandler:
> {(response, error) in
>             if (error != nil) {
>                 self.presentAlert("Error", message:
> error!.localizedDescription)
>             } else {
>                 self.presentAlert("Success", message: "Successfully
> uploaded!")
>             }
>         })
>
>
>             */
>     }
>
>
>
> Disclaimer : This message and any attachments are solely for the intended
> recipient and may contain confidential or privileged information. If you
> are not the intended recipient, any disclosure, copying, use, or
> distribution of the information included in this message and any
> attachments is prohibited. If you have received this communication in
> error, please notify us by reply e-mail to IT at Indegene.com and
> immediately and permanently delete this message and any attachments. Any
> views expressed in this mail are not necessarily the views of INDEGENE.
> Thank you.
>
> _______________________________________________
> Aerogear-users mailing list
> Aerogear-users at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-users
>
>


-- 
-- Passos
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20160428/87a35cdc/attachment.html 

From corinnekrych at gmail.com  Fri Apr 29 07:57:36 2016
From: corinnekrych at gmail.com (Corinne Krych)
Date: Fri, 29 Apr 2016 13:57:36 +0200
Subject: [Aerogear-users] AeroGear SDK integration with Keycloak
In-Reply-To: <CADF=h2soKNyRo-qfTRfWcwXnkKeB43A08-MspD9H5CaGUPeKEA@mail.gmail.com>
References: <4C1D8037-6EBE-4B33-9EC4-391C68259BD5@indegene.com>
	<CADF=h2soKNyRo-qfTRfWcwXnkKeB43A08-MspD9H5CaGUPeKEA@mail.gmail.com>
Message-ID: <CAL8vO=c9TnF7ia2OMTnwqPJmVv2vPNJDx7VkrNEQKokV_m7Wsg@mail.gmail.com>

Hello Ashish,

Could you test this PR [1]?
As Passos mentioned the 404 error must be due to the endpoint changes.

++
Corinne
[1] https://github.com/aerogear/aerogear-ios-oauth2/pull/43

On 28 April 2016 at 18:01, Daniel Passos <dpassos at redhat.com> wrote:

> Hi
>
> Are you getting this error when you are firing a request to KC server from
> your app?
>
> ```
>
> 17:01:31,549 ERROR [org.jboss.resteasy.resteasy_jaxrs.i18n] (default task-1) RESTEASY002010: Failed to execute: javax.ws.rs.NotFoundException: HTTP 404 Not Found
>
> ```
>
> I'm not 100% sure (didn't have time to test) but I think the problem is,
> KC 1.9.1 are using different endpoints and the iOS app was not updated yet.
>
> Our cookbook backend[1] was updated to 1.9.1 by the community[2] weeks ago
>
> Unfortunately he updated only the Android app[3] to the new endpoints
>
> Can you check the Android PR[3] and see if you change that in the iOS app
> it works?
>
> [1]
> https://github.com/aerogear/aerogear-backend-cookbook/tree/master/Shoot
> [2] https://github.com/aerogear/aerogear-backend-cookbook/pull/29
> [3] https://github.com/aerogear/aerogear-android-cookbook/pull/56
>
>
>
>
>
>
>
> On Thu, Apr 28, 2016 at 8:44 AM, Ashish Pandita <
> Ashish.Pandita at indegene.com> wrote:
>
>> Hi All,
>>
>> I am having some trouble using aerogear to connect keycloak locally. I am
>> using shoot example I did the following things
>> 1) installed pods on shoot&share
>> https://github.com/aerogear/aerogear-ios-cookbook/tree/0.3.0/Shoot
>> 2) installed the key cloak ver keycloak-1.9.2.Final (
>> https://github.com/aerogear/aerogear-backend-cookbook/tree/master/Shoot)
>> I can access the admin console in browser imported the realm configuration
>> https://github.com/aerogear/aerogear-backend-cookbook/blob/master/Shoot/configuration/shoot-realm.json
>> 3) I run the server attached is the log and here is the terminal rec
>> https://asciinema.org/a/7xhosmb63kn9tnvn99gnh5mbm
>> 4) I am not able to login to keycloak. I am getting errors in console
>> when keycloak launches the web view can you please help what need to be
>> done to resolve it or guide to proper resource.
>>
>> here is the Aerogear API which I am using
>>
>>  @IBAction func shareWithKeycloak() {
>>
>>
>>         let keycloakHost = "http://localhost:8080"
>>         let keycloakConfig = KeycloakConfig(
>>             clientId: "shoot-third-party",
>>             host: keycloakHost,
>>             realm: "shoot-realm")
>>         // If you want to use embedded web view uncomment
>>           keycloakConfig.isWebView = true
>>
>>
>>         // Workaround issue on Keychain
>> https://forums.developer.apple.com/message/23323
>>         let gdModule = KeycloakOAuth2Module(config: keycloakConfig,
>> session: UntrustedMemoryOAuth2Session(accountId: "ACCOUNT_FOR_CLIENTID_\(
>> keycloakConfig.clientId)"))
>>
>>
>>         // let gdModule =
>> AccountManager.addKeycloakAccount(keycloakConfig)
>>         self.http.authzModule = gdModule
>>        /* gdModule.login { (response, token, error) in
>>
>>
>>             print(response)
>>             print(token)
>>             print(error)
>>         } */
>>
>>
>>
>>
>>          print("Perform photo upload with Keycloak")
>>
>>
>>
>>
>>        self.performUpload("\(keycloakHost)/shoot/rest/photos",
>> parameters: self.extractImageAsMultipartParams())
>>
>>     }
>>
>>     func performUpload(url: String, parameters: [String: AnyObject]?) {
>>
>>
>>
>>
>>         self.http.request(HttpMethod.POST, path: url, parameters:
>> parameters, credential: nil, responseSerializer: nil) { (response,
>> error) in
>>             if (error != nil) {
>>                 self.presentAlert("Error", message: error!.
>> localizedDescription)
>>             } else {
>>                 self.presentAlert("Success", message: "Successfully
>> uploaded!")
>>             }
>>         }
>>
>>
>>         /*
>>
>>
>>         self.http.POST(url, parameters: parameters, completionHandler:
>> {(response, error) in
>>             if (error != nil) {
>>                 self.presentAlert("Error", message:
>> error!.localizedDescription)
>>             } else {
>>                 self.presentAlert("Success", message: "Successfully
>> uploaded!")
>>             }
>>         })
>>
>>
>>             */
>>     }
>>
>>
>>
>> Disclaimer : This message and any attachments are solely for the intended
>> recipient and may contain confidential or privileged information. If you
>> are not the intended recipient, any disclosure, copying, use, or
>> distribution of the information included in this message and any
>> attachments is prohibited. If you have received this communication in
>> error, please notify us by reply e-mail to IT at Indegene.com and
>> immediately and permanently delete this message and any attachments. Any
>> views expressed in this mail are not necessarily the views of INDEGENE.
>> Thank you.
>>
>> _______________________________________________
>> Aerogear-users mailing list
>> Aerogear-users at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-users
>>
>>
>
>
> --
> -- Passos
>
> _______________________________________________
> 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-users/attachments/20160429/0d5c84ba/attachment-0001.html 

From laurent.broudoux at gmail.com  Fri Apr 29 17:09:17 2016
From: laurent.broudoux at gmail.com (Laurent Broudoux)
Date: Fri, 29 Apr 2016 14:09:17 -0700 (MST)
Subject: [Aerogear-users] Handshake issue when connecting to APNS (from
 OpenShift Online)
In-Reply-To: <1447857794947-278.post@n5.nabble.com>
References: <CAJ4FD9xMXaj4Qn6PTmPwp8u5wc-QpvFG1nqH613hFHjEfpgCEA@mail.gmail.com>
	<CAAg5f2SJqQZAa=fp4BH-RYU55OVJFigLqj06Kj+zZ+rjvy-HCw@mail.gmail.com>
	<CAAg5f2Ratmy9fOHuXnhUiDYDmPiwopuMzMWTZzqtTtbzPkCJ_g@mail.gmail.com>
	<1446827080262-266.post@n5.nabble.com>
	<CAAg5f2T+-9QwRruiDO3gtp3UYD9MCDEkLKX6tg4kYf3SdSbj7g@mail.gmail.com>
	<1447856353424-276.post@n5.nabble.com>
	<CAAg5f2QtjpY9XWw4gOQq=BWRP1HNG__iEU0pyp1GFfcK-c-EPw@mail.gmail.com>
	<1447857794947-278.post@n5.nabble.com>
Message-ID: <1461964157530-628.post@n5.nabble.com>

Hello, 

I've got the same issue here with Aerogear UPS 1.1.0.Final hosted on
Openshift Online. 

My certificate is valid until April 2017 but I encounter the same "Error
sending payload to APNs server: javax.net.ssl.SSLHandshakeException:
sun.security.validator.ValidatorException: No trusted certificate found"
exception when sending to APN after many days (variable) and many messages
(variable) sent. 

A restart of the gear make things ok again but for unknown time ... 

Any hints since last reports ? 
Let me know if I can help providing more infos. 

Regards, 
-- 
Laurent




--
View this message in context: http://aerogear-users.1116366.n5.nabble.com/Aerogear-users-Handshake-issue-when-connecting-to-APNS-from-OpenShift-Online-tp263p628.html
Sent from the aerogear-users mailing list archive at Nabble.com.