From raghavendra.dabbir at gmail.com  Wed Jun  1 02:55:23 2016
From: raghavendra.dabbir at gmail.com (Raghavendra)
Date: Tue, 31 May 2016 23:55:23 -0700 (MST)
Subject: [Aerogear-users] Aerogear Push Notification in iOS
Message-ID: <1464764123888-691.post@n5.nabble.com>

Hi,

I am implementing Push Notification on Android and iOS

My code works perfectly fine in Android. However, for iOS, i get the below
error on JBOSS server.

12:15:21,457 INFO  [APNsPushNotificationSender] (Thread-37
(HornetQ-client-global-threads-949943370)) One batch to APNs has been
submitted
12:15:21,716 INFO  [APNsPushNotificationSender] (MonitoringThread-1)
Removing invalid token:
8c21b00e4f2258a0bd852fedaca8b3507a326e365465ae621dbed5418806f2ce

I am not sure what mistake i am making. 

Please help.



--
View this message in context: http://aerogear-users.1116366.n5.nabble.com/Aerogear-Push-Notification-in-iOS-tp691.html
Sent from the aerogear-users mailing list archive at Nabble.com.

From yves.nicolas at dynamease.com  Wed Jun  1 03:00:55 2016
From: yves.nicolas at dynamease.com (Yves Nicolas)
Date: Wed, 1 Jun 2016 09:00:55 +0200
Subject: [Aerogear-users] Aerogear Push Notification in iOS
In-Reply-To: <1464764123888-691.post@n5.nabble.com>
References: <1464764123888-691.post@n5.nabble.com>
Message-ID: <574E8827.2030305@dynamease.com>


I had the same issue several times, i has also been addressed on this 
list recently, this has to do with the APN certificates that you upload 
in Aerogear.
You have 2 things to pay attention to :

Make sure the Apple produced APN certificate that you upload in you 
aerogear IOS variant through the edit network option is still valid datewise

Make sure this certificate is consistent with the Provisionning profile 
you have used to produce your app : APN certificate can be produced on 
apple developper site with production or development flavour. If you use 
a production provisionning profile for your app and a development APN 
certificate on aerogear, or vice versa, you will experience this issue 
of Apple network invalidating your token.

Best,
Yves

Le 01/06/2016 08:55, Raghavendra a ?crit :
> Hi,
>
> I am implementing Push Notification on Android and iOS
>
> My code works perfectly fine in Android. However, for iOS, i get the below
> error on JBOSS server.
>
> 12:15:21,457 INFO  [APNsPushNotificationSender] (Thread-37
> (HornetQ-client-global-threads-949943370)) One batch to APNs has been
> submitted
> 12:15:21,716 INFO  [APNsPushNotificationSender] (MonitoringThread-1)
> Removing invalid token:
> 8c21b00e4f2258a0bd852fedaca8b3507a326e365465ae621dbed5418806f2ce
>
> I am not sure what mistake i am making.
>
> Please help.
>
>
>
> --
> View this message in context: http://aerogear-users.1116366.n5.nabble.com/Aerogear-Push-Notification-in-iOS-tp691.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


From matzew at apache.org  Wed Jun  1 04:29:52 2016
From: matzew at apache.org (Matthias Wessendorf)
Date: Wed, 1 Jun 2016 09:29:52 +0100
Subject: [Aerogear-users] [aerogear-dev] UPS Device Registration
	Endpoints
In-Reply-To: <CALD3Fd3hN1BLFic0vFZOtVocEM11oRkPfJ21FRnDZ9b1gb-Egg@mail.gmail.com>
References: <CALD3Fd3EomTCmo4Mte7x7ohkPkAPH+fFz3NWiXFOWbVZp3kOMA@mail.gmail.com>
	<F087E56F-5BCC-43BB-B3DD-5D1E95A06379@gmail.com>
	<CAAg5f2TteiGiE680MYGy7P7=kZfpdYAKcJLm-_JMrwQpAaFoow@mail.gmail.com>
	<CALD3Fd3hN1BLFic0vFZOtVocEM11oRkPfJ21FRnDZ9b1gb-Egg@mail.gmail.com>
Message-ID: <CAAg5f2QCxb_T3nGR7FeNEyqJrLTrRt_t4Ke+81RPjHdPKaf6Tw@mail.gmail.com>

that's cool stuff!

-Matthias

On Tue, May 31, 2016 at 8:07 PM, Luke Holmquist <lholmqui at redhat.com> wrote:

> Thanks for the info guys.
>
> Also i just released the 0.1.0 version of this
> https://www.npmjs.com/package/unifiedpush-registration-client
>
> a client for doing device registration.
>
> Currently implemented is register and unregister.  i'm working on getting
> the "importer" working for the next release.
>
>
>
> On Sat, May 28, 2016 at 12:50 AM, Matthias Wessendorf <matzew at apache.org>
> wrote:
>
>>
>>
>> On Fri, May 27, 2016 at 10:10 PM, Sebastien Blanc <scm.blanc at gmail.com>
>> wrote:
>>
>>>
>>>
>>> Envoy? de mon iPhone
>>>
>>> Le 27 mai 2016 ? 21:56, Luke Holmquist <lholmqui at redhat.com> a ?crit :
>>>
>>> thats right folks, i'm asking this question on a Friday before a Holiday
>>> weekend(US) at 3:52(est)
>>>
>>>
>>> i've started to implement the Device registration endpoints in node and
>>> was just wondering what the id is here in this header
>>>
>>>
>>> -v -H "Accept: application/json" -H "Content-type: application/json" -H "aerogear-push-id: someid"
>>>
>>>
>>> is it something specific, or just a random number/alpha-numeric thingy
>>>
>>>
>>> here is the doc link for reference:
>>> https://aerogear.org/docs/specs/aerogear-unifiedpush-rest/#246535932
>>>
>>> Let's wait for Matzew to confirm but I think you can ignore it. Looks
>>> like a left over from our first analytics implementation , we use now a
>>> separate endpoint (the PUT) and pass this ID as a path parameter.
>>> We probably need to clean up the javadoc
>>>
>>
>> correct, doc error.
>>
>> the thing is only relevant here:
>>
>> https://github.com/aerogear/aerogear-unifiedpush-server/blob/252c3a979cf05b69f061f7ffa6d3dcc8826c7b51/jaxrs/src/main/java/org/jboss/aerogear/unifiedpush/rest/registry/installations/InstallationRegistrationEndpoint.java#L203
>>
>>
>>
>>>
>>>
>>>
>>> I've also decided to create this as a separate module instead of
>>> including it in the node admin client here:
>>> https://github.com/bucharest-gold/unifiedpush-admin-client
>>> mostly becuase these registration endpoints don't needed to be KC
>>> authenticated.
>>>
>>> even if they were KC managed, they would be different (E.g. just
>> bearer-only), since there is no relationship to the actual mgmt of the
>> server.
>>
>> +1 on separating these two things
>>
>> -M
>>
>>
>>
>>>   and they could also be used on a IOT device or something that runs
>>> node that has webpush/simplePush or some new crazy protocol.
>>>
>>> Make sense , I like that
>>>
>>>
>>>
>>> -Luke
>>>
>>> _______________________________________________
>>> 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/
>> twitter: http://twitter.com/mwessendorf
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20160601/7806e6b3/attachment.html 

From Ramona.Cristea at mvise.de  Wed Jun  1 06:43:30 2016
From: Ramona.Cristea at mvise.de (Ramona.Cristea)
Date: Wed, 1 Jun 2016 03:43:30 -0700 (MST)
Subject: [Aerogear-users] Device registration - Method not allowed
In-Reply-To: <CAEQz2CsNO+s12KK67h6V8k1uuc9JopKVER71vRNR8ZLLXTb+=g@mail.gmail.com>
References: <1464348325054.94450@mvise.de>
	<CAEQz2CsNO+s12KK67h6V8k1uuc9JopKVER71vRNR8ZLLXTb+=g@mail.gmail.com>
Message-ID: <1464777810893-694.post@n5.nabble.com>

Hello,

I'm a colleague of Philipp, only that I'm working on integrating the android
part. 

We generated again variantID and variantSecret and we send them correctly.
Also we tested the request using Advance REST client chrome extension and
there the connection succeeds with 200 status code and a json response. But
inside the app we still receive error 405 Method not allowed. 

Exception received: org.jboss.aerogear.android.pipe.http.HttpException: The
server returned the error code 405.
Stacktrace:
"org.jboss.aerogear.android.pipe.http.HttpRestProvider.getHeaderAndBody(HttpRestProvider.java:287)"
"org.jboss.aerogear.android.pipe.http.HttpRestProvider.post(HttpRestProvider.java:148)"
"org.jboss.aerogear.android.pipe.http.HttpRestProvider.post(HttpRestProvider.java:134)"
"org.jboss.aerogear.android.unifiedpush.gcm.AeroGearGCMPushRegistrar$4.doInBackground(AeroGearGCMPushRegistrar.java:170)"
"org.jboss.aerogear.android.unifiedpush.gcm.AeroGearGCMPushRegistrar$4.doInBackground(AeroGearGCMPushRegistrar.java:135)"
"android.os.AsyncTask$2.call(AsyncTask.java:292)"
"java.util.concurrent.FutureTask.run(FutureTask.java:237)"
"android.os.AsyncTask$SerialExecutor$1.run(AsyncTask.java:231)"
"java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1112)"
"java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:587)"
"java.lang.Thread.run(Thread.java:818)"

After some more digging we suspect that this is the issue we are
experiencing https://issues.jboss.org/browse/AGDROID-270 , only that we
don't receive inside the app an exception similar to that described in the
jira ticket. According to the steps described there, it seems that aero gear
library fails to establish a connection to a unified Push Server using
HTTPS, which is exactly what we are trying to do. We can provide the sample
app with our server configuration set up if needed. 



--
View this message in context: http://aerogear-users.1116366.n5.nabble.com/Aerogear-users-Device-registration-Method-not-allowed-tp685p694.html
Sent from the aerogear-users mailing list archive at Nabble.com.

From supittma at redhat.com  Wed Jun  1 08:20:03 2016
From: supittma at redhat.com (Summers Pittman)
Date: Wed, 1 Jun 2016 08:20:03 -0400
Subject: [Aerogear-users] Device registration - Method not allowed
In-Reply-To: <1464777810893-694.post@n5.nabble.com>
References: <1464348325054.94450@mvise.de>
	<CAEQz2CsNO+s12KK67h6V8k1uuc9JopKVER71vRNR8ZLLXTb+=g@mail.gmail.com>
	<1464777810893-694.post@n5.nabble.com>
Message-ID: <CAEQz2CsFW4YE3OyobGt=dDfoNJBaYABAsQ9LWQYcoVvfp6VazQ@mail.gmail.com>

On Wed, Jun 1, 2016 at 6:43 AM, Ramona.Cristea <Ramona.Cristea at mvise.de>
wrote:

> Hello,
>
> I'm a colleague of Philipp, only that I'm working on integrating the
> android
> part.
>
> We generated again variantID and variantSecret and we send them correctly.
> Also we tested the request using Advance REST client chrome extension and
> there the connection succeeds with 200 status code and a json response. But
> inside the app we still receive error 405 Method not allowed.
>
> Exception received: org.jboss.aerogear.android.pipe.http.HttpException: The
> server returned the error code 405.
> Stacktrace:
>
> "org.jboss.aerogear.android.pipe.http.HttpRestProvider.getHeaderAndBody(HttpRestProvider.java:287)"
>
> "org.jboss.aerogear.android.pipe.http.HttpRestProvider.post(HttpRestProvider.java:148)"
>
> "org.jboss.aerogear.android.pipe.http.HttpRestProvider.post(HttpRestProvider.java:134)"
>
> "org.jboss.aerogear.android.unifiedpush.gcm.AeroGearGCMPushRegistrar$4.doInBackground(AeroGearGCMPushRegistrar.java:170)"
>
> "org.jboss.aerogear.android.unifiedpush.gcm.AeroGearGCMPushRegistrar$4.doInBackground(AeroGearGCMPushRegistrar.java:135)"
> "android.os.AsyncTask$2.call(AsyncTask.java:292)"
> "java.util.concurrent.FutureTask.run(FutureTask.java:237)"
> "android.os.AsyncTask$SerialExecutor$1.run(AsyncTask.java:231)"
>
> "java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1112)"
>
> "java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:587)"
> "java.lang.Thread.run(Thread.java:818)"
>
> After some more digging we suspect that this is the issue we are
> experiencing https://issues.jboss.org/browse/AGDROID-270 , only that we
> don't receive inside the app an exception similar to that described in the
> jira ticket. According to the steps described there, it seems that aero
> gear
> library fails to establish a connection to a unified Push Server using
> HTTPS, which is exactly what we are trying to do. We can provide the sample
> app with our server configuration set up if needed.
>
> The sample app would be great.  Just link us a github (or any other public
repo) and we can take a look.

>
>
> --
> View this message in context:
> http://aerogear-users.1116366.n5.nabble.com/Aerogear-users-Device-registration-Method-not-allowed-tp685p694.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/20160601/61a0384a/attachment-0001.html 

From supittma at redhat.com  Wed Jun  1 08:35:17 2016
From: supittma at redhat.com (Summers Pittman)
Date: Wed, 1 Jun 2016 08:35:17 -0400
Subject: [Aerogear-users] Device registration - Method not allowed
In-Reply-To: <CAEQz2CsFW4YE3OyobGt=dDfoNJBaYABAsQ9LWQYcoVvfp6VazQ@mail.gmail.com>
References: <1464348325054.94450@mvise.de>
	<CAEQz2CsNO+s12KK67h6V8k1uuc9JopKVER71vRNR8ZLLXTb+=g@mail.gmail.com>
	<1464777810893-694.post@n5.nabble.com>
	<CAEQz2CsFW4YE3OyobGt=dDfoNJBaYABAsQ9LWQYcoVvfp6VazQ@mail.gmail.com>
Message-ID: <CAEQz2CsRni4bN750sMcbCFNaNPmJqgLtFx8JhULxWeTqHTqUiw@mail.gmail.com>

In Android N I have documented a workaround for this particular issue :
https://blog.sagaoftherealms.net/?p=578

On Wed, Jun 1, 2016 at 8:20 AM, Summers Pittman <supittma at redhat.com> wrote:

>
>
> On Wed, Jun 1, 2016 at 6:43 AM, Ramona.Cristea <Ramona.Cristea at mvise.de>
> wrote:
>
>> Hello,
>>
>> I'm a colleague of Philipp, only that I'm working on integrating the
>> android
>> part.
>>
>> We generated again variantID and variantSecret and we send them correctly.
>> Also we tested the request using Advance REST client chrome extension and
>> there the connection succeeds with 200 status code and a json response.
>> But
>> inside the app we still receive error 405 Method not allowed.
>>
>> Exception received: org.jboss.aerogear.android.pipe.http.HttpException:
>> The
>> server returned the error code 405.
>> Stacktrace:
>>
>> "org.jboss.aerogear.android.pipe.http.HttpRestProvider.getHeaderAndBody(HttpRestProvider.java:287)"
>>
>> "org.jboss.aerogear.android.pipe.http.HttpRestProvider.post(HttpRestProvider.java:148)"
>>
>> "org.jboss.aerogear.android.pipe.http.HttpRestProvider.post(HttpRestProvider.java:134)"
>>
>> "org.jboss.aerogear.android.unifiedpush.gcm.AeroGearGCMPushRegistrar$4.doInBackground(AeroGearGCMPushRegistrar.java:170)"
>>
>> "org.jboss.aerogear.android.unifiedpush.gcm.AeroGearGCMPushRegistrar$4.doInBackground(AeroGearGCMPushRegistrar.java:135)"
>> "android.os.AsyncTask$2.call(AsyncTask.java:292)"
>> "java.util.concurrent.FutureTask.run(FutureTask.java:237)"
>> "android.os.AsyncTask$SerialExecutor$1.run(AsyncTask.java:231)"
>>
>> "java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1112)"
>>
>> "java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:587)"
>> "java.lang.Thread.run(Thread.java:818)"
>>
>> After some more digging we suspect that this is the issue we are
>> experiencing https://issues.jboss.org/browse/AGDROID-270 , only that we
>> don't receive inside the app an exception similar to that described in the
>> jira ticket. According to the steps described there, it seems that aero
>> gear
>> library fails to establish a connection to a unified Push Server using
>> HTTPS, which is exactly what we are trying to do. We can provide the
>> sample
>> app with our server configuration set up if needed.
>>
>> The sample app would be great.  Just link us a github (or any other
> public repo) and we can take a look.
>
>>
>>
>> --
>> View this message in context:
>> http://aerogear-users.1116366.n5.nabble.com/Aerogear-users-Device-registration-Method-not-allowed-tp685p694.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/20160601/71004e83/attachment.html 

From lholmqui at redhat.com  Wed Jun  1 10:35:41 2016
From: lholmqui at redhat.com (Luke Holmquist)
Date: Wed, 1 Jun 2016 10:35:41 -0400
Subject: [Aerogear-users] [aerogear-dev] UPS Device Registration
	Endpoints
In-Reply-To: <CAAg5f2QCxb_T3nGR7FeNEyqJrLTrRt_t4Ke+81RPjHdPKaf6Tw@mail.gmail.com>
References: <CALD3Fd3EomTCmo4Mte7x7ohkPkAPH+fFz3NWiXFOWbVZp3kOMA@mail.gmail.com>
	<F087E56F-5BCC-43BB-B3DD-5D1E95A06379@gmail.com>
	<CAAg5f2TteiGiE680MYGy7P7=kZfpdYAKcJLm-_JMrwQpAaFoow@mail.gmail.com>
	<CALD3Fd3hN1BLFic0vFZOtVocEM11oRkPfJ21FRnDZ9b1gb-Egg@mail.gmail.com>
	<CAAg5f2QCxb_T3nGR7FeNEyqJrLTrRt_t4Ke+81RPjHdPKaf6Tw@mail.gmail.com>
Message-ID: <CALD3Fd0SQ_5dFrDz+cAMf9YRAPQdf53RSwdcJRYwv7c7kRP3+Q@mail.gmail.com>

Latest version.
https://www.npmjs.com/package/unifiedpush-registration-client

now has the importer function!!

On Wed, Jun 1, 2016 at 4:29 AM, Matthias Wessendorf <matzew at apache.org>
wrote:

> that's cool stuff!
>
> -Matthias
>
> On Tue, May 31, 2016 at 8:07 PM, Luke Holmquist <lholmqui at redhat.com>
> wrote:
>
>> Thanks for the info guys.
>>
>> Also i just released the 0.1.0 version of this
>> https://www.npmjs.com/package/unifiedpush-registration-client
>>
>> a client for doing device registration.
>>
>> Currently implemented is register and unregister.  i'm working on getting
>> the "importer" working for the next release.
>>
>>
>>
>> On Sat, May 28, 2016 at 12:50 AM, Matthias Wessendorf <matzew at apache.org>
>> wrote:
>>
>>>
>>>
>>> On Fri, May 27, 2016 at 10:10 PM, Sebastien Blanc <scm.blanc at gmail.com>
>>> wrote:
>>>
>>>>
>>>>
>>>> Envoy? de mon iPhone
>>>>
>>>> Le 27 mai 2016 ? 21:56, Luke Holmquist <lholmqui at redhat.com> a ?crit :
>>>>
>>>> thats right folks, i'm asking this question on a Friday before a
>>>> Holiday weekend(US) at 3:52(est)
>>>>
>>>>
>>>> i've started to implement the Device registration endpoints in node and
>>>> was just wondering what the id is here in this header
>>>>
>>>>
>>>> -v -H "Accept: application/json" -H "Content-type: application/json" -H "aerogear-push-id: someid"
>>>>
>>>>
>>>> is it something specific, or just a random number/alpha-numeric thingy
>>>>
>>>>
>>>> here is the doc link for reference:
>>>> https://aerogear.org/docs/specs/aerogear-unifiedpush-rest/#246535932
>>>>
>>>> Let's wait for Matzew to confirm but I think you can ignore it. Looks
>>>> like a left over from our first analytics implementation , we use now a
>>>> separate endpoint (the PUT) and pass this ID as a path parameter.
>>>> We probably need to clean up the javadoc
>>>>
>>>
>>> correct, doc error.
>>>
>>> the thing is only relevant here:
>>>
>>> https://github.com/aerogear/aerogear-unifiedpush-server/blob/252c3a979cf05b69f061f7ffa6d3dcc8826c7b51/jaxrs/src/main/java/org/jboss/aerogear/unifiedpush/rest/registry/installations/InstallationRegistrationEndpoint.java#L203
>>>
>>>
>>>
>>>>
>>>>
>>>>
>>>> I've also decided to create this as a separate module instead of
>>>> including it in the node admin client here:
>>>> https://github.com/bucharest-gold/unifiedpush-admin-client
>>>> mostly becuase these registration endpoints don't needed to be KC
>>>> authenticated.
>>>>
>>>> even if they were KC managed, they would be different (E.g. just
>>> bearer-only), since there is no relationship to the actual mgmt of the
>>> server.
>>>
>>> +1 on separating these two things
>>>
>>> -M
>>>
>>>
>>>
>>>>   and they could also be used on a IOT device or something that runs
>>>> node that has webpush/simplePush or some new crazy protocol.
>>>>
>>>> Make sense , I like that
>>>>
>>>>
>>>>
>>>> -Luke
>>>>
>>>> _______________________________________________
>>>> 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/
>>> twitter: http://twitter.com/mwessendorf
>>>
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> 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/20160601/6d4859d8/attachment.html 

From Ramona.Cristea at mvise.de  Thu Jun  2 01:53:30 2016
From: Ramona.Cristea at mvise.de (Ramona.Cristea)
Date: Wed, 1 Jun 2016 22:53:30 -0700 (MST)
Subject: [Aerogear-users] Device registration - Method not allowed
In-Reply-To: <CAEQz2CsRni4bN750sMcbCFNaNPmJqgLtFx8JhULxWeTqHTqUiw@mail.gmail.com>
References: <1464348325054.94450@mvise.de>
	<CAEQz2CsNO+s12KK67h6V8k1uuc9JopKVER71vRNR8ZLLXTb+=g@mail.gmail.com>
	<1464777810893-694.post@n5.nabble.com>
	<CAEQz2CsFW4YE3OyobGt=dDfoNJBaYABAsQ9LWQYcoVvfp6VazQ@mail.gmail.com>
	<CAEQz2CsRni4bN750sMcbCFNaNPmJqgLtFx8JhULxWeTqHTqUiw@mail.gmail.com>
Message-ID: <1464846810628-698.post@n5.nabble.com>

Unfortunately the client wants to support API 16 and up, so we have to find a
solution also for the older android versions. I sent you yesterday evening
the sample app through email, hope you received it.



--
View this message in context: http://aerogear-users.1116366.n5.nabble.com/Aerogear-users-Device-registration-Method-not-allowed-tp685p698.html
Sent from the aerogear-users mailing list archive at Nabble.com.

From raghavendra.dabbir at gmail.com  Thu Jun  2 02:43:21 2016
From: raghavendra.dabbir at gmail.com (Raghavendra)
Date: Wed, 1 Jun 2016 23:43:21 -0700 (MST)
Subject: [Aerogear-users] Aerogear Push Notification in iOS
In-Reply-To: <574E8827.2030305@dynamease.com>
References: <1464764123888-691.post@n5.nabble.com>
	<574E8827.2030305@dynamease.com>
Message-ID: <1464849801957-699.post@n5.nabble.com>

Hi

I have tried the below and both the points were already taken care of. Still
I am getting the same issue.

Is there anyway to identify further logs to get to the root cause of the
issue?

Also, my app is a hybrid app (cordova).

Regards
Raghav



--
View this message in context: http://aerogear-users.1116366.n5.nabble.com/Aerogear-Push-Notification-in-iOS-tp691p699.html
Sent from the aerogear-users mailing list archive at Nabble.com.

From matzew at apache.org  Thu Jun  2 05:09:38 2016
From: matzew at apache.org (Matthias Wessendorf)
Date: Thu, 2 Jun 2016 10:09:38 +0100
Subject: [Aerogear-users] Aerogear Push Notification in iOS
In-Reply-To: <1464849801957-699.post@n5.nabble.com>
References: <1464764123888-691.post@n5.nabble.com>
	<574E8827.2030305@dynamease.com>
	<1464849801957-699.post@n5.nabble.com>
Message-ID: <CAAg5f2ROJhwurq2AtiZVov5D+=OrPxrAT6sh_vk-Vhw1TSt65g@mail.gmail.com>

On Thu, Jun 2, 2016 at 7:43 AM, Raghavendra <raghavendra.dabbir at gmail.com>
wrote:

> Hi
>
> I have tried the below and both the points were already taken care of.
> Still
> I am getting the same issue.
>
> Is there anyway to identify further logs to get to the root cause of the
> issue?
>

https://github.com/aerogear/aerogear-unifiedpush-server/blob/1.1.x-dev/push/sender/src/main/java/org/jboss/aerogear/unifiedpush/message/sender/APNsPushNotificationSender.java#L250

it's the issue Yves described, make sure you have a dev cert for your dev
app (or vice versa)

-M


>
> Also, my app is a hybrid app (cordova).
>
> Regards
> Raghav
>
>
>
> --
> View this message in context:
> http://aerogear-users.1116366.n5.nabble.com/Aerogear-Push-Notification-in-iOS-tp691p699.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/
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20160602/ef834d16/attachment.html 

From supittma at redhat.com  Thu Jun  2 07:13:23 2016
From: supittma at redhat.com (Summers Pittman)
Date: Thu, 2 Jun 2016 07:13:23 -0400
Subject: [Aerogear-users] Device registration - Method not allowed
In-Reply-To: <1464846810628-698.post@n5.nabble.com>
References: <1464348325054.94450@mvise.de>
	<CAEQz2CsNO+s12KK67h6V8k1uuc9JopKVER71vRNR8ZLLXTb+=g@mail.gmail.com>
	<1464777810893-694.post@n5.nabble.com>
	<CAEQz2CsFW4YE3OyobGt=dDfoNJBaYABAsQ9LWQYcoVvfp6VazQ@mail.gmail.com>
	<CAEQz2CsRni4bN750sMcbCFNaNPmJqgLtFx8JhULxWeTqHTqUiw@mail.gmail.com>
	<1464846810628-698.post@n5.nabble.com>
Message-ID: <CAEQz2CucF-w4NaEo8Mb6sE=p=042rQ63EdxkSB5pM0tNNjfmxw@mail.gmail.com>

On Thu, Jun 2, 2016 at 1:53 AM, Ramona.Cristea <Ramona.Cristea at mvise.de>
wrote:

> Unfortunately the client wants to support API 16 and up, so we have to
> find a
> solution also for the older android versions. I sent you yesterday evening
> the sample app through email, hope you received it.
>
> Could you test the workaround in an Android N emulator?  If the app works
in that situation we know you are facing
https://issues.jboss.org/browse/AGDROID-270 and we can work out a better
work around which works for Android 16 (and fixes this for everyone else).

I'm taking a look at the sample today.


>
> --
> View this message in context:
> http://aerogear-users.1116366.n5.nabble.com/Aerogear-users-Device-registration-Method-not-allowed-tp685p698.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/20160602/63a3b8d7/attachment.html 

From supittma at redhat.com  Thu Jun  2 07:58:06 2016
From: supittma at redhat.com (Summers Pittman)
Date: Thu, 2 Jun 2016 07:58:06 -0400
Subject: [Aerogear-users] Device registration - Method not allowed
In-Reply-To: <CAEQz2CucF-w4NaEo8Mb6sE=p=042rQ63EdxkSB5pM0tNNjfmxw@mail.gmail.com>
References: <1464348325054.94450@mvise.de>
	<CAEQz2CsNO+s12KK67h6V8k1uuc9JopKVER71vRNR8ZLLXTb+=g@mail.gmail.com>
	<1464777810893-694.post@n5.nabble.com>
	<CAEQz2CsFW4YE3OyobGt=dDfoNJBaYABAsQ9LWQYcoVvfp6VazQ@mail.gmail.com>
	<CAEQz2CsRni4bN750sMcbCFNaNPmJqgLtFx8JhULxWeTqHTqUiw@mail.gmail.com>
	<1464846810628-698.post@n5.nabble.com>
	<CAEQz2CucF-w4NaEo8Mb6sE=p=042rQ63EdxkSB5pM0tNNjfmxw@mail.gmail.com>
Message-ID: <CAEQz2Cv+r+1a5iqN_ve_-CEkzOB=y3rftqfbvUgQL35_yR0Xuw@mail.gmail.com>

So I don't think you are experiencing AGDROID-270.

I've used the Android N network security tooling and still get the same
error.  Additionally I have successfully registered with a different
instance of UPS using the sample code.

Which version of the UPS server are you running?

On Thu, Jun 2, 2016 at 7:13 AM, Summers Pittman <supittma at redhat.com> wrote:

>
>
> On Thu, Jun 2, 2016 at 1:53 AM, Ramona.Cristea <Ramona.Cristea at mvise.de>
> wrote:
>
>> Unfortunately the client wants to support API 16 and up, so we have to
>> find a
>> solution also for the older android versions. I sent you yesterday evening
>> the sample app through email, hope you received it.
>>
>> Could you test the workaround in an Android N emulator?  If the app works
> in that situation we know you are facing
> https://issues.jboss.org/browse/AGDROID-270 and we can work out a better
> work around which works for Android 16 (and fixes this for everyone else).
>
> I'm taking a look at the sample today.
>
>
>>
>> --
>> View this message in context:
>> http://aerogear-users.1116366.n5.nabble.com/Aerogear-users-Device-registration-Method-not-allowed-tp685p698.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/20160602/75e2bbbd/attachment.html 

From Ramona.Cristea at mvise.de  Thu Jun  2 08:53:01 2016
From: Ramona.Cristea at mvise.de (Ramona.Cristea)
Date: Thu, 2 Jun 2016 05:53:01 -0700 (MST)
Subject: [Aerogear-users] Device registration - Method not allowed
In-Reply-To: <CAEQz2Cv+r+1a5iqN_ve_-CEkzOB=y3rftqfbvUgQL35_yR0Xuw@mail.gmail.com>
References: <1464348325054.94450@mvise.de>
	<CAEQz2CsNO+s12KK67h6V8k1uuc9JopKVER71vRNR8ZLLXTb+=g@mail.gmail.com>
	<1464777810893-694.post@n5.nabble.com>
	<CAEQz2CsFW4YE3OyobGt=dDfoNJBaYABAsQ9LWQYcoVvfp6VazQ@mail.gmail.com>
	<CAEQz2CsRni4bN750sMcbCFNaNPmJqgLtFx8JhULxWeTqHTqUiw@mail.gmail.com>
	<1464846810628-698.post@n5.nabble.com>
	<CAEQz2CucF-w4NaEo8Mb6sE=p=042rQ63EdxkSB5pM0tNNjfmxw@mail.gmail.com>
	<CAEQz2Cv+r+1a5iqN_ve_-CEkzOB=y3rftqfbvUgQL35_yR0Xuw@mail.gmail.com>
Message-ID: <1464871981589-703.post@n5.nabble.com>

We've deployed UPS 1.1.3. 



--
View this message in context: http://aerogear-users.1116366.n5.nabble.com/Aerogear-users-Device-registration-Method-not-allowed-tp685p703.html
Sent from the aerogear-users mailing list archive at Nabble.com.

From supittma at redhat.com  Thu Jun  2 09:08:46 2016
From: supittma at redhat.com (Summers Pittman)
Date: Thu, 2 Jun 2016 09:08:46 -0400
Subject: [Aerogear-users] Device registration - Method not allowed
In-Reply-To: <CAEQz2Cv+r+1a5iqN_ve_-CEkzOB=y3rftqfbvUgQL35_yR0Xuw@mail.gmail.com>
References: <1464348325054.94450@mvise.de>
	<CAEQz2CsNO+s12KK67h6V8k1uuc9JopKVER71vRNR8ZLLXTb+=g@mail.gmail.com>
	<1464777810893-694.post@n5.nabble.com>
	<CAEQz2CsFW4YE3OyobGt=dDfoNJBaYABAsQ9LWQYcoVvfp6VazQ@mail.gmail.com>
	<CAEQz2CsRni4bN750sMcbCFNaNPmJqgLtFx8JhULxWeTqHTqUiw@mail.gmail.com>
	<1464846810628-698.post@n5.nabble.com>
	<CAEQz2CucF-w4NaEo8Mb6sE=p=042rQ63EdxkSB5pM0tNNjfmxw@mail.gmail.com>
	<CAEQz2Cv+r+1a5iqN_ve_-CEkzOB=y3rftqfbvUgQL35_yR0Xuw@mail.gmail.com>
Message-ID: <CAEQz2CumBqf96gM4h+vF4YqeaEcQhxYO6849L_2b=MgmJqZrfw@mail.gmail.com>

Ok I did some digging and discovered a confound which might be the issue.

When I make a request to your UPS instance using curl I get a redirect.  It
is possible that the agdroid push library does not handle this redirect
elegantly.

The redirect is from "$YOUR_URL/ag-push/rest/registry/device" to
"$YOUR_URL/ag-push/rest/registry/device/".  Notice how a "/" is added onto
the end.

I'm not convinced this is the issue, but it does seem like something to
investigate.


On Thu, Jun 2, 2016 at 7:58 AM, Summers Pittman <supittma at redhat.com> wrote:

> So I don't think you are experiencing AGDROID-270.
>
> I've used the Android N network security tooling and still get the same
> error.  Additionally I have successfully registered with a different
> instance of UPS using the sample code.
>
> Which version of the UPS server are you running?
>
> On Thu, Jun 2, 2016 at 7:13 AM, Summers Pittman <supittma at redhat.com>
> wrote:
>
>>
>>
>> On Thu, Jun 2, 2016 at 1:53 AM, Ramona.Cristea <Ramona.Cristea at mvise.de>
>> wrote:
>>
>>> Unfortunately the client wants to support API 16 and up, so we have to
>>> find a
>>> solution also for the older android versions. I sent you yesterday
>>> evening
>>> the sample app through email, hope you received it.
>>>
>>> Could you test the workaround in an Android N emulator?  If the app
>> works in that situation we know you are facing
>> https://issues.jboss.org/browse/AGDROID-270 and we can work out a better
>> work around which works for Android 16 (and fixes this for everyone else).
>>
>> I'm taking a look at the sample today.
>>
>>
>>>
>>> --
>>> View this message in context:
>>> http://aerogear-users.1116366.n5.nabble.com/Aerogear-users-Device-registration-Method-not-allowed-tp685p698.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/20160602/956c37c5/attachment-0001.html 

From supittma at redhat.com  Thu Jun  2 09:31:35 2016
From: supittma at redhat.com (Summers Pittman)
Date: Thu, 2 Jun 2016 09:31:35 -0400
Subject: [Aerogear-users] Device registration - Method not allowed
In-Reply-To: <CAEQz2CumBqf96gM4h+vF4YqeaEcQhxYO6849L_2b=MgmJqZrfw@mail.gmail.com>
References: <1464348325054.94450@mvise.de>
	<CAEQz2CsNO+s12KK67h6V8k1uuc9JopKVER71vRNR8ZLLXTb+=g@mail.gmail.com>
	<1464777810893-694.post@n5.nabble.com>
	<CAEQz2CsFW4YE3OyobGt=dDfoNJBaYABAsQ9LWQYcoVvfp6VazQ@mail.gmail.com>
	<CAEQz2CsRni4bN750sMcbCFNaNPmJqgLtFx8JhULxWeTqHTqUiw@mail.gmail.com>
	<1464846810628-698.post@n5.nabble.com>
	<CAEQz2CucF-w4NaEo8Mb6sE=p=042rQ63EdxkSB5pM0tNNjfmxw@mail.gmail.com>
	<CAEQz2Cv+r+1a5iqN_ve_-CEkzOB=y3rftqfbvUgQL35_yR0Xuw@mail.gmail.com>
	<CAEQz2CumBqf96gM4h+vF4YqeaEcQhxYO6849L_2b=MgmJqZrfw@mail.gmail.com>
Message-ID: <CAEQz2CuC3XmXueeKSTGv_rPb0PvojDuJrWsKFjtmvP6_vH6AaA@mail.gmail.com>

On Thu, Jun 2, 2016 at 9:08 AM, Summers Pittman <supittma at redhat.com> wrote:

> Ok I did some digging and discovered a confound which might be the issue.
>
> When I make a request to your UPS instance using curl I get a redirect.
> It is possible that the agdroid push library does not handle this redirect
> elegantly.
>
> The redirect is from "$YOUR_URL/ag-push/rest/registry/device" to
> "$YOUR_URL/ag-push/rest/registry/device/".  Notice how a "/" is added onto
> the end.
>
> I'm not convinced this is the issue, but it does seem like something to
> investigate.
>

The redirect is causing the issue/exposing the bug.

You may follow the progress on this JIRA :
https://issues.jboss.org/browse/AGDROID-549

>
>
> On Thu, Jun 2, 2016 at 7:58 AM, Summers Pittman <supittma at redhat.com>
> wrote:
>
>> So I don't think you are experiencing AGDROID-270.
>>
>> I've used the Android N network security tooling and still get the same
>> error.  Additionally I have successfully registered with a different
>> instance of UPS using the sample code.
>>
>> Which version of the UPS server are you running?
>>
>> On Thu, Jun 2, 2016 at 7:13 AM, Summers Pittman <supittma at redhat.com>
>> wrote:
>>
>>>
>>>
>>> On Thu, Jun 2, 2016 at 1:53 AM, Ramona.Cristea <Ramona.Cristea at mvise.de>
>>> wrote:
>>>
>>>> Unfortunately the client wants to support API 16 and up, so we have to
>>>> find a
>>>> solution also for the older android versions. I sent you yesterday
>>>> evening
>>>> the sample app through email, hope you received it.
>>>>
>>>> Could you test the workaround in an Android N emulator?  If the app
>>> works in that situation we know you are facing
>>> https://issues.jboss.org/browse/AGDROID-270 and we can work out a
>>> better work around which works for Android 16 (and fixes this for everyone
>>> else).
>>>
>>> I'm taking a look at the sample today.
>>>
>>>
>>>>
>>>> --
>>>> View this message in context:
>>>> http://aerogear-users.1116366.n5.nabble.com/Aerogear-users-Device-registration-Method-not-allowed-tp685p698.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/20160602/b351ad02/attachment.html 

From Ramona.Cristea at mvise.de  Fri Jun  3 03:49:40 2016
From: Ramona.Cristea at mvise.de (Ramona.Cristea)
Date: Fri, 3 Jun 2016 00:49:40 -0700 (MST)
Subject: [Aerogear-users] Device registration - Method not allowed
In-Reply-To: <CAEQz2CuC3XmXueeKSTGv_rPb0PvojDuJrWsKFjtmvP6_vH6AaA@mail.gmail.com>
References: <1464348325054.94450@mvise.de>
	<CAEQz2CsNO+s12KK67h6V8k1uuc9JopKVER71vRNR8ZLLXTb+=g@mail.gmail.com>
	<1464777810893-694.post@n5.nabble.com>
	<CAEQz2CsFW4YE3OyobGt=dDfoNJBaYABAsQ9LWQYcoVvfp6VazQ@mail.gmail.com>
	<CAEQz2CsRni4bN750sMcbCFNaNPmJqgLtFx8JhULxWeTqHTqUiw@mail.gmail.com>
	<1464846810628-698.post@n5.nabble.com>
	<CAEQz2CucF-w4NaEo8Mb6sE=p=042rQ63EdxkSB5pM0tNNjfmxw@mail.gmail.com>
	<CAEQz2Cv+r+1a5iqN_ve_-CEkzOB=y3rftqfbvUgQL35_yR0Xuw@mail.gmail.com>
	<CAEQz2CumBqf96gM4h+vF4YqeaEcQhxYO6849L_2b=MgmJqZrfw@mail.gmail.com>
	<CAEQz2CuC3XmXueeKSTGv_rPb0PvojDuJrWsKFjtmvP6_vH6AaA@mail.gmail.com>
Message-ID: <1464940180699-706.post@n5.nabble.com>

Hello 

Thank you for your investigation. I forwarded everything to my colleague in
charge of the server. Also he discovered some issues on the server side. It
seems that some rules were applied to the server's firewall which caused
some connections to be refused. 




--
View this message in context: http://aerogear-users.1116366.n5.nabble.com/Aerogear-users-Device-registration-Method-not-allowed-tp685p706.html
Sent from the aerogear-users mailing list archive at Nabble.com.

From Ramona.Cristea at mvise.de  Fri Jun  3 04:04:13 2016
From: Ramona.Cristea at mvise.de (Ramona.Cristea)
Date: Fri, 3 Jun 2016 01:04:13 -0700 (MST)
Subject: [Aerogear-users] Enabled TLS 1.2
Message-ID: <1464941053076-707.post@n5.nabble.com>

Hello,

We would like for our push server to support only TLS 1.2 connections for
security reasons. 
The Android documentation for SSLSocket says that TLS 1.1 and TLS 1.2 is
supported within android starting API level 16+ (Android 4.1, Jelly Bean).
But it is by default disabled but starting with API level 20+ (Android 4.4
for watch, Kitkat Watch and Android 5.0 for phone, Lollipop) they are
enabled.

We set the minimum sdk version to API 16, but we would like to know if the
Aero Gear library enables TLS 1.2 protocol when doing a connection? 
If not, then all connections on smartphones with android versions < 5.0 will
fail. 



--
View this message in context: http://aerogear-users.1116366.n5.nabble.com/Enabled-TLS-1-2-tp707.html
Sent from the aerogear-users mailing list archive at Nabble.com.

From jrogoff38 at gmail.com  Sun Jun  5 21:23:12 2016
From: jrogoff38 at gmail.com (Jonathon Rogoff)
Date: Mon, 06 Jun 2016 01:23:12 +0000
Subject: [Aerogear-users] Jackson Dependency Conflict with Aerogear 1.1.0
Message-ID: <CAHGsuRCjzFP454XCiiLAqYwGWjvBhOYPBXQBpVPqNPPNiShhLw@mail.gmail.com>

I have been successfully using Aerogear 1.0.0 in my product for a while
now.  I am making some additions (primarily using contentAvailable to
prompt apps I haven't heard from lately to check in once in a while) and
thought it would be a opportunity to upgrade to 1.1.0.  I upgraded the
Aerogear server as well as my Android and iOS apps without any problems.
However, my jboss web server, used by administrators to initiate messages,
is proving problematic.

After upgrading the unifiedpush-java-client to 1.1.0.Final on my jboss web
server, I cannot get it to play nicely with the resteasy-jackson2-provider
implementation (3.0.16.Final) I use for custom RESTful communication
between my apps and the web server.

It appears that including the unifiedpush-java-client 1.1.0 causes my
RESTful services to use the codehaus jackson implementation in the
unifiedpush-java-client. Therefore, all of my fasterxml jackson annotations
(@JsonIgnore and @JsonFormat) are ignored causing my RESTful services to
fail.

If I exclude both jackson-jaxrs and jackson-databind from the
unifiedpush-java-client in my pom.xml then everything compiles and my
RESTful services work.  However, when attempting to send a push
notification from the server I get a "java.lang.NoClassDefFoundError:
org/codehaus/jackson/map/ObjectMapper" from UnifiedPushMessage for obvious
reasons.

I tried going back to the 1.0.0 version of the unifiedpush-java-client, but
that just results in status code 400 responses from the aerogear 1.1.0
server.

Do you have any suggestions for resolving this conflict, or should I just
roll everything back to the 1.0.0 version until further notice?

I appreciate any direction you can provide.

- Jonathon Rogoff
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20160606/0365298d/attachment.html 

From Matthias.Bourillon at saint-gobain.com  Mon Jun  6 05:14:22 2016
From: Matthias.Bourillon at saint-gobain.com (Bourillon, Matthias)
Date: Mon, 6 Jun 2016 09:14:22 +0000
Subject: [Aerogear-users] iOS Push issue when having multiple Installations
Message-ID: <143D1BBAE1FDE0459ADC21668AADEFC5846164E1@EXMB2EU22.za.if.atcsg.net>

Hello,
We are facing an issue while using Aerogear Push Server with an iOS variant.
Here is the scenario :

1.       We have 89 installations registered against an iOS Production Variant

2.       We send a message

3.       No one receive the message on our iOS App

4.       We disable ALL installations but 1

5.       We send a message

6.       The 1 device receives the push notification and works as expected

We have other iOS variants with thousands of registrations working without any problem like this.

Can the number of registered device impact the sending behavior? Can a wrong token or anything else block the notification sending to Apple? Logs do not seem to complain about any particular issue.
We are using Aerogear Push Server 1.0.0.

Thanks,
Matthias
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20160606/981b853a/attachment-0001.html 

From matzew at apache.org  Mon Jun  6 05:20:21 2016
From: matzew at apache.org (Matthias Wessendorf)
Date: Mon, 6 Jun 2016 11:20:21 +0200
Subject: [Aerogear-users] iOS Push issue when having multiple
	Installations
In-Reply-To: <143D1BBAE1FDE0459ADC21668AADEFC5846164E1@EXMB2EU22.za.if.atcsg.net>
References: <143D1BBAE1FDE0459ADC21668AADEFC5846164E1@EXMB2EU22.za.if.atcsg.net>
Message-ID: <CAAg5f2RR_ekTOscsn2zjEAHkxPiy_zD+j1qOtTxxTU2PNzWN-Q@mail.gmail.com>

Hi,

I think you are hitting a a bug. in the 1.1.0 series we did add a catch for
reported invalid tokens:
https://github.com/aerogear/aerogear-unifiedpush-server/commit/a44773a8dba1d9ce57a99de2dc11463f16e8e79f

-Matthias

On Mon, Jun 6, 2016 at 11:14 AM, Bourillon, Matthias <
Matthias.Bourillon at saint-gobain.com> wrote:

> Hello,
>
> We are facing an issue while using Aerogear Push Server with an iOS
> variant.
>
> Here is the scenario :
>
> 1.       We have 89 installations registered against an iOS Production
> Variant
>
> 2.       We send a message
>
> 3.       No one receive the message on our iOS App
>
> 4.       We disable ALL installations but 1
>
> 5.       We send a message
>
> 6.       The 1 device receives the push notification and works as expected
>
>
>
> We have other iOS variants with thousands of registrations working without
> any problem like this.
>
>
>
> Can the number of registered device impact the sending behavior? Can a
> wrong token or anything else block the notification sending to Apple? Logs
> do not seem to complain about any particular issue.
>
> We are using Aerogear Push Server 1.0.0.
>
>
>
> Thanks,
>
> Matthias
>
> _______________________________________________
> 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/
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20160606/95d058e7/attachment.html 

From Matthias.Bourillon at saint-gobain.com  Mon Jun  6 05:32:43 2016
From: Matthias.Bourillon at saint-gobain.com (Bourillon, Matthias)
Date: Mon, 6 Jun 2016 09:32:43 +0000
Subject: [Aerogear-users] iOS Push issue when having
	multiple	Installations
In-Reply-To: <CAAg5f2RR_ekTOscsn2zjEAHkxPiy_zD+j1qOtTxxTU2PNzWN-Q@mail.gmail.com>
References: <143D1BBAE1FDE0459ADC21668AADEFC5846164E1@EXMB2EU22.za.if.atcsg.net>
	<CAAg5f2RR_ekTOscsn2zjEAHkxPiy_zD+j1qOtTxxTU2PNzWN-Q@mail.gmail.com>
Message-ID: <143D1BBAE1FDE0459ADC21668AADEFC584616506@EXMB2EU22.za.if.atcsg.net>

Matthias,
Does the behaviour I described makes sense?
In 1.0.0, if one of the token is invalid, can it block the whole push sending to other tokens?

Matthias

De : aerogear-users-bounces at lists.jboss.org [mailto:aerogear-users-bounces at lists.jboss.org] De la part de Matthias Wessendorf
Envoy? : lundi 6 juin 2016 11:20
? : aerogear-users at lists.jboss.org
Objet : Re: [Aerogear-users] iOS Push issue when having multiple Installations

Hi,

I think you are hitting a a bug. in the 1.1.0 series we did add a catch for reported invalid tokens:
https://github.com/aerogear/aerogear-unifiedpush-server/commit/a44773a8dba1d9ce57a99de2dc11463f16e8e79f

-Matthias

On Mon, Jun 6, 2016 at 11:14 AM, Bourillon, Matthias <Matthias.Bourillon at saint-gobain.com<mailto:Matthias.Bourillon at saint-gobain.com>> wrote:
Hello,
We are facing an issue while using Aerogear Push Server with an iOS variant.
Here is the scenario :

1.       We have 89 installations registered against an iOS Production Variant

2.       We send a message

3.       No one receive the message on our iOS App

4.       We disable ALL installations but 1

5.       We send a message

6.       The 1 device receives the push notification and works as expected

We have other iOS variants with thousands of registrations working without any problem like this.

Can the number of registered device impact the sending behavior? Can a wrong token or anything else block the notification sending to Apple? Logs do not seem to complain about any particular issue.
We are using Aerogear Push Server 1.0.0.

Thanks,
Matthias

_______________________________________________
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/
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20160606/e70363d2/attachment.html 

From matzew at apache.org  Mon Jun  6 06:39:47 2016
From: matzew at apache.org (Matthias Wessendorf)
Date: Mon, 6 Jun 2016 12:39:47 +0200
Subject: [Aerogear-users] iOS Push issue when having multiple
	Installations
In-Reply-To: <143D1BBAE1FDE0459ADC21668AADEFC584616506@EXMB2EU22.za.if.atcsg.net>
References: <143D1BBAE1FDE0459ADC21668AADEFC5846164E1@EXMB2EU22.za.if.atcsg.net>
	<CAAg5f2RR_ekTOscsn2zjEAHkxPiy_zD+j1qOtTxxTU2PNzWN-Q@mail.gmail.com>
	<143D1BBAE1FDE0459ADC21668AADEFC584616506@EXMB2EU22.za.if.atcsg.net>
Message-ID: <CAAg5f2RXbe6Yqs=A=wSznMZZLDfU=CUZWQLbqjV2DVG=cckw3w@mail.gmail.com>

I think yes, the problem was the a mix of tokens for different profiles
(e.g. dev vs. prod)

-M

On Mon, Jun 6, 2016 at 11:32 AM, Bourillon, Matthias <
Matthias.Bourillon at saint-gobain.com> wrote:

> Matthias,
>
> Does the behaviour I described makes sense?
>
> In 1.0.0, if one of the token is invalid, can it block the whole push
> sending to other tokens?
>
>
>
> Matthias
>
>
>
> *De :* aerogear-users-bounces at lists.jboss.org [mailto:
> aerogear-users-bounces at lists.jboss.org] *De la part de* Matthias
> Wessendorf
> *Envoy? :* lundi 6 juin 2016 11:20
> *? :* aerogear-users at lists.jboss.org
> *Objet :* Re: [Aerogear-users] iOS Push issue when having multiple
> Installations
>
>
>
> Hi,
>
>
>
> I think you are hitting a a bug. in the 1.1.0 series we did add a catch
> for reported invalid tokens:
>
>
> https://github.com/aerogear/aerogear-unifiedpush-server/commit/a44773a8dba1d9ce57a99de2dc11463f16e8e79f
>
>
>
> -Matthias
>
>
>
> On Mon, Jun 6, 2016 at 11:14 AM, Bourillon, Matthias <
> Matthias.Bourillon at saint-gobain.com> wrote:
>
> Hello,
>
> We are facing an issue while using Aerogear Push Server with an iOS
> variant.
>
> Here is the scenario :
>
> 1.       We have 89 installations registered against an iOS Production
> Variant
>
> 2.       We send a message
>
> 3.       No one receive the message on our iOS App
>
> 4.       We disable ALL installations but 1
>
> 5.       We send a message
>
> 6.       The 1 device receives the push notification and works as expected
>
>
>
> We have other iOS variants with thousands of registrations working without
> any problem like this.
>
>
>
> Can the number of registered device impact the sending behavior? Can a
> wrong token or anything else block the notification sending to Apple? Logs
> do not seem to complain about any particular issue.
>
> We are using Aerogear Push Server 1.0.0.
>
>
>
> Thanks,
>
> Matthias
>
>
> _______________________________________________
> 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/
> twitter: http://twitter.com/mwessendorf
>
> _______________________________________________
> 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/
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20160606/6e5b55a9/attachment-0001.html 

From Matthias.Bourillon at saint-gobain.com  Mon Jun  6 10:56:36 2016
From: Matthias.Bourillon at saint-gobain.com (Bourillon, Matthias)
Date: Mon, 6 Jun 2016 14:56:36 +0000
Subject: [Aerogear-users] iOS Push issue when having
	multiple	Installations
In-Reply-To: <CAAg5f2RXbe6Yqs=A=wSznMZZLDfU=CUZWQLbqjV2DVG=cckw3w@mail.gmail.com>
References: <143D1BBAE1FDE0459ADC21668AADEFC5846164E1@EXMB2EU22.za.if.atcsg.net>
	<CAAg5f2RR_ekTOscsn2zjEAHkxPiy_zD+j1qOtTxxTU2PNzWN-Q@mail.gmail.com>
	<143D1BBAE1FDE0459ADC21668AADEFC584616506@EXMB2EU22.za.if.atcsg.net>
	<CAAg5f2RXbe6Yqs=A=wSznMZZLDfU=CUZWQLbqjV2DVG=cckw3w@mail.gmail.com>
Message-ID: <143D1BBAE1FDE0459ADC21668AADEFC5846167CC@EXMB2EU22.za.if.atcsg.net>

Matthias,
I wanted to validate this behavior and I just created a script, manually sending a Payload to Apple Push service, 1 by 1 to our 89 installations.
I am getting the same behavior : as soon as a payload is being sent to an invalid token, remaining payloads are not sent to devices. Is this something Apple block on their side?

Thanks,
Matthias

De : aerogear-users-bounces at lists.jboss.org [mailto:aerogear-users-bounces at lists.jboss.org] De la part de Matthias Wessendorf
Envoy? : lundi 6 juin 2016 12:40
? : aerogear-users at lists.jboss.org
Objet : Re: [Aerogear-users] iOS Push issue when having multiple Installations

I think yes, the problem was the a mix of tokens for different profiles (e.g. dev vs. prod)

-M

On Mon, Jun 6, 2016 at 11:32 AM, Bourillon, Matthias <Matthias.Bourillon at saint-gobain.com<mailto:Matthias.Bourillon at saint-gobain.com>> wrote:
Matthias,
Does the behaviour I described makes sense?
In 1.0.0, if one of the token is invalid, can it block the whole push sending to other tokens?

Matthias

De : aerogear-users-bounces at lists.jboss.org<mailto:aerogear-users-bounces at lists.jboss.org> [mailto:aerogear-users-bounces at lists.jboss.org<mailto:aerogear-users-bounces at lists.jboss.org>] De la part de Matthias Wessendorf
Envoy? : lundi 6 juin 2016 11:20
? : aerogear-users at lists.jboss.org<mailto:aerogear-users at lists.jboss.org>
Objet : Re: [Aerogear-users] iOS Push issue when having multiple Installations

Hi,

I think you are hitting a a bug. in the 1.1.0 series we did add a catch for reported invalid tokens:
https://github.com/aerogear/aerogear-unifiedpush-server/commit/a44773a8dba1d9ce57a99de2dc11463f16e8e79f

-Matthias

On Mon, Jun 6, 2016 at 11:14 AM, Bourillon, Matthias <Matthias.Bourillon at saint-gobain.com<mailto:Matthias.Bourillon at saint-gobain.com>> wrote:
Hello,
We are facing an issue while using Aerogear Push Server with an iOS variant.
Here is the scenario :

1.       We have 89 installations registered against an iOS Production Variant

2.       We send a message

3.       No one receive the message on our iOS App

4.       We disable ALL installations but 1

5.       We send a message

6.       The 1 device receives the push notification and works as expected

We have other iOS variants with thousands of registrations working without any problem like this.

Can the number of registered device impact the sending behavior? Can a wrong token or anything else block the notification sending to Apple? Logs do not seem to complain about any particular issue.
We are using Aerogear Push Server 1.0.0.

Thanks,
Matthias

_______________________________________________
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/
twitter: http://twitter.com/mwessendorf

_______________________________________________
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/
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20160606/a6bec6c1/attachment.html 

From lholmqui at redhat.com  Mon Jun  6 12:24:26 2016
From: lholmqui at redhat.com (Luke Holmquist)
Date: Mon, 6 Jun 2016 12:24:26 -0400
Subject: [Aerogear-users] UnifiedPush Node sender move to Promises
In-Reply-To: <CALD3Fd1=F65fEFUoCdFWzxLGU4hmV3fosutUgzO6YpyW4H96Ow@mail.gmail.com>
References: <CALD3Fd0N2Nvq32ehMtO8UAXTBQ35uFF9Od037G9-TAgE3YpQLA@mail.gmail.com>
	<CAAg5f2SdUCCXKRf3Ktdhs0JZHSr5OjtxJC24Fngz+XY5Noe_qw@mail.gmail.com>
	<CALD3Fd0a7+gk4dV6ABvj=6-XWh0+qBg_qmAY62jTay1NnCvABw@mail.gmail.com>
	<CALD3Fd1=F65fEFUoCdFWzxLGU4hmV3fosutUgzO6YpyW4H96Ow@mail.gmail.com>
Message-ID: <CALD3Fd0KUtYzutn7K-Lbfz6AjZd85h0K8hmX_TV7gaApenOO0A@mail.gmail.com>

Hello peeps,

I've just released the 0.13.0 version for the sender,
https://www.npmjs.com/package/unifiedpush-node-sender

The api has changed a bit, so please check out the example to see the
changes.

Also note that node version 4 or greater is required here


I will probably think about doing a 1.0.0 release soon once people have had
a chance to check out the changes


On Thu, May 5, 2016 at 1:46 PM, Luke Holmquist <lholmqui at redhat.com> wrote:

> for those following along at home:
>
> https://issues.jboss.org/browse/AGPUSH-1621
>
> On Thu, May 5, 2016 at 1:42 PM, Luke Holmquist <lholmqui at redhat.com>
> wrote:
>
>>
>>
>> On Thu, May 5, 2016 at 1:37 PM, Matthias Wessendorf <matzew at apache.org>
>> wrote:
>>
>>> I think it would be good for the community to move forward and use
>>> latest technology. Node 0.12 is already very old, given the current version
>>> is 6.
>>>
>>> How about getting promisses in, and afterwards release this as a 1.0.0
>>> release ?
>>>
>>
>> i think this sounds like a plan,
>>
>> /me goes and creates a JIRA
>>
>>>
>>> On Thu, May 5, 2016 at 5:14 PM, Luke Holmquist <lholmqui at redhat.com>
>>> wrote:
>>>
>>>> Hello people,
>>>>
>>>> I think i would like to move the unifiedpush-node-sender,
>>>> https://github.com/aerogear/aerogear-unifiedpush-nodejs-client ,  to
>>>> be Promise based.
>>>>
>>>> Currently it uses callback pattern that many node.js packages use as
>>>> well as emitting events.
>>>>
>>>> When i first created this 3 years ago, that was sort of the standard
>>>> way of doing things,  but Promises have become very popular(i know i love
>>>> them :)) and have been a native feature since node 0.12.x
>>>>
>>>> considering we have not yet hit a 1.0.0, we can pretty much just make
>>>> this change and we will be ok.
>>>>
>>>> If this is to big of a change all at once, we could always do both
>>>> callbacks and Promises.  I think we did this for Datamanager in the past.
>>>>
>>>> Perhaps once we fully move to promises, then we can hit a 1.0.0
>>>>
>>>> My only concern is other projects that might be using the sender that
>>>> are not yet on node 0.12 or above, since this is when promises became
>>>> native.  I would really like to not have to include the polyfill.
>>>>
>>>> i suppose those users would need to stick to the previous versions then.
>>>>
>>>> anyway,  would like to hear some thoughts.
>>>>
>>>>
>>>> -Luke
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> 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/20160606/8186f718/attachment-0001.html 

From matzew at apache.org  Mon Jun  6 15:16:57 2016
From: matzew at apache.org (Matthias Wessendorf)
Date: Mon, 6 Jun 2016 21:16:57 +0200
Subject: [Aerogear-users] iOS Push issue when having multiple
	Installations
In-Reply-To: <143D1BBAE1FDE0459ADC21668AADEFC5846167CC@EXMB2EU22.za.if.atcsg.net>
References: <143D1BBAE1FDE0459ADC21668AADEFC5846164E1@EXMB2EU22.za.if.atcsg.net>
	<CAAg5f2RR_ekTOscsn2zjEAHkxPiy_zD+j1qOtTxxTU2PNzWN-Q@mail.gmail.com>
	<143D1BBAE1FDE0459ADC21668AADEFC584616506@EXMB2EU22.za.if.atcsg.net>
	<CAAg5f2RXbe6Yqs=A=wSznMZZLDfU=CUZWQLbqjV2DVG=cckw3w@mail.gmail.com>
	<143D1BBAE1FDE0459ADC21668AADEFC5846167CC@EXMB2EU22.za.if.atcsg.net>
Message-ID: <CAAg5f2RTc0N7-epCxc9iUd+8_e6UgOVchS=bW7ZaZi+5g6D1fQ@mail.gmail.com>

are you using the 1.1.0 ?

I think it should not stop.

Question: how did invalid tokens end up at the server?

On Mon, Jun 6, 2016 at 4:56 PM, Bourillon, Matthias <
Matthias.Bourillon at saint-gobain.com> wrote:

> Matthias,
>
> I wanted to validate this behavior and I just created a script, manually
> sending a Payload to Apple Push service, 1 by 1 to our 89 installations.
> I am getting the same behavior : as soon as a payload is being sent to an
> invalid token, remaining payloads are not sent to devices. Is this
> something Apple block on their side?
>
>
>
> Thanks,
>
> Matthias
>
>
>
> *De :* aerogear-users-bounces at lists.jboss.org [mailto:
> aerogear-users-bounces at lists.jboss.org] *De la part de* Matthias
> Wessendorf
> *Envoy? :* lundi 6 juin 2016 12:40
>
> *? :* aerogear-users at lists.jboss.org
> *Objet :* Re: [Aerogear-users] iOS Push issue when having multiple
> Installations
>
>
>
> I think yes, the problem was the a mix of tokens for different profiles
> (e.g. dev vs. prod)
>
>
>
> -M
>
>
>
> On Mon, Jun 6, 2016 at 11:32 AM, Bourillon, Matthias <
> Matthias.Bourillon at saint-gobain.com> wrote:
>
> Matthias,
>
> Does the behaviour I described makes sense?
>
> In 1.0.0, if one of the token is invalid, can it block the whole push
> sending to other tokens?
>
>
>
> Matthias
>
>
>
> *De :* aerogear-users-bounces at lists.jboss.org [mailto:
> aerogear-users-bounces at lists.jboss.org] *De la part de* Matthias
> Wessendorf
> *Envoy? :* lundi 6 juin 2016 11:20
> *? :* aerogear-users at lists.jboss.org
> *Objet :* Re: [Aerogear-users] iOS Push issue when having multiple
> Installations
>
>
>
> Hi,
>
>
>
> I think you are hitting a a bug. in the 1.1.0 series we did add a catch
> for reported invalid tokens:
>
>
> https://github.com/aerogear/aerogear-unifiedpush-server/commit/a44773a8dba1d9ce57a99de2dc11463f16e8e79f
>
>
>
> -Matthias
>
>
>
> On Mon, Jun 6, 2016 at 11:14 AM, Bourillon, Matthias <
> Matthias.Bourillon at saint-gobain.com> wrote:
>
> Hello,
>
> We are facing an issue while using Aerogear Push Server with an iOS
> variant.
>
> Here is the scenario :
>
> 1.       We have 89 installations registered against an iOS Production
> Variant
>
> 2.       We send a message
>
> 3.       No one receive the message on our iOS App
>
> 4.       We disable ALL installations but 1
>
> 5.       We send a message
>
> 6.       The 1 device receives the push notification and works as expected
>
>
>
> We have other iOS variants with thousands of registrations working without
> any problem like this.
>
>
>
> Can the number of registered device impact the sending behavior? Can a
> wrong token or anything else block the notification sending to Apple? Logs
> do not seem to complain about any particular issue.
>
> We are using Aerogear Push Server 1.0.0.
>
>
>
> Thanks,
>
> Matthias
>
>
> _______________________________________________
> 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/
> twitter: http://twitter.com/mwessendorf
>
>
> _______________________________________________
> 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/
> twitter: http://twitter.com/mwessendorf
>
> _______________________________________________
> 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/
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20160606/ee0925db/attachment.html 

From Matthias.Bourillon at saint-gobain.com  Tue Jun  7 04:06:43 2016
From: Matthias.Bourillon at saint-gobain.com (Bourillon, Matthias)
Date: Tue, 7 Jun 2016 08:06:43 +0000
Subject: [Aerogear-users] iOS Push issue when having
	multiple	Installations
In-Reply-To: <CAAg5f2RTc0N7-epCxc9iUd+8_e6UgOVchS=bW7ZaZi+5g6D1fQ@mail.gmail.com>
References: <143D1BBAE1FDE0459ADC21668AADEFC5846164E1@EXMB2EU22.za.if.atcsg.net>
	<CAAg5f2RR_ekTOscsn2zjEAHkxPiy_zD+j1qOtTxxTU2PNzWN-Q@mail.gmail.com>
	<143D1BBAE1FDE0459ADC21668AADEFC584616506@EXMB2EU22.za.if.atcsg.net>
	<CAAg5f2RXbe6Yqs=A=wSznMZZLDfU=CUZWQLbqjV2DVG=cckw3w@mail.gmail.com>
	<143D1BBAE1FDE0459ADC21668AADEFC5846167CC@EXMB2EU22.za.if.atcsg.net>
	<CAAg5f2RTc0N7-epCxc9iUd+8_e6UgOVchS=bW7ZaZi+5g6D1fQ@mail.gmail.com>
Message-ID: <143D1BBAE1FDE0459ADC21668AADEFC584616E55@EXMB2EU22.za.if.atcsg.net>

Hello Matthias,
We are still in 1.0.0 as 1.1.0 migration process fails with our instance.
To me, invalid tokens have been added on the server due to App development process during which App with development provisioning profile have registered against the server.

If I understand correctly, in 1.1.0, if we have Dev token registered against the server they?ll be discovered invalid by Aerogear server and message sending will not be impacted. Is this right?

Thanks,
Matthias

De : aerogear-users-bounces at lists.jboss.org [mailto:aerogear-users-bounces at lists.jboss.org] De la part de Matthias Wessendorf
Envoy? : lundi 6 juin 2016 21:17
? : aerogear-users at lists.jboss.org
Objet : Re: [Aerogear-users] iOS Push issue when having multiple Installations

are you using the 1.1.0 ?

I think it should not stop.

Question: how did invalid tokens end up at the server?

On Mon, Jun 6, 2016 at 4:56 PM, Bourillon, Matthias <Matthias.Bourillon at saint-gobain.com<mailto:Matthias.Bourillon at saint-gobain.com>> wrote:
Matthias,
I wanted to validate this behavior and I just created a script, manually sending a Payload to Apple Push service, 1 by 1 to our 89 installations.
I am getting the same behavior : as soon as a payload is being sent to an invalid token, remaining payloads are not sent to devices. Is this something Apple block on their side?

Thanks,
Matthias

De : aerogear-users-bounces at lists.jboss.org<mailto:aerogear-users-bounces at lists.jboss.org> [mailto:aerogear-users-bounces at lists.jboss.org<mailto:aerogear-users-bounces at lists.jboss.org>] De la part de Matthias Wessendorf
Envoy? : lundi 6 juin 2016 12:40

? : aerogear-users at lists.jboss.org<mailto:aerogear-users at lists.jboss.org>
Objet : Re: [Aerogear-users] iOS Push issue when having multiple Installations

I think yes, the problem was the a mix of tokens for different profiles (e.g. dev vs. prod)

-M

On Mon, Jun 6, 2016 at 11:32 AM, Bourillon, Matthias <Matthias.Bourillon at saint-gobain.com<mailto:Matthias.Bourillon at saint-gobain.com>> wrote:
Matthias,
Does the behaviour I described makes sense?
In 1.0.0, if one of the token is invalid, can it block the whole push sending to other tokens?

Matthias

De : aerogear-users-bounces at lists.jboss.org<mailto:aerogear-users-bounces at lists.jboss.org> [mailto:aerogear-users-bounces at lists.jboss.org<mailto:aerogear-users-bounces at lists.jboss.org>] De la part de Matthias Wessendorf
Envoy? : lundi 6 juin 2016 11:20
? : aerogear-users at lists.jboss.org<mailto:aerogear-users at lists.jboss.org>
Objet : Re: [Aerogear-users] iOS Push issue when having multiple Installations

Hi,

I think you are hitting a a bug. in the 1.1.0 series we did add a catch for reported invalid tokens:
https://github.com/aerogear/aerogear-unifiedpush-server/commit/a44773a8dba1d9ce57a99de2dc11463f16e8e79f

-Matthias

On Mon, Jun 6, 2016 at 11:14 AM, Bourillon, Matthias <Matthias.Bourillon at saint-gobain.com<mailto:Matthias.Bourillon at saint-gobain.com>> wrote:
Hello,
We are facing an issue while using Aerogear Push Server with an iOS variant.
Here is the scenario :

1.       We have 89 installations registered against an iOS Production Variant

2.       We send a message

3.       No one receive the message on our iOS App

4.       We disable ALL installations but 1

5.       We send a message

6.       The 1 device receives the push notification and works as expected

We have other iOS variants with thousands of registrations working without any problem like this.

Can the number of registered device impact the sending behavior? Can a wrong token or anything else block the notification sending to Apple? Logs do not seem to complain about any particular issue.
We are using Aerogear Push Server 1.0.0.

Thanks,
Matthias

_______________________________________________
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/
twitter: http://twitter.com/mwessendorf

_______________________________________________
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/
twitter: http://twitter.com/mwessendorf

_______________________________________________
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/
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20160607/aee0580f/attachment-0001.html 

From matzew at apache.org  Tue Jun  7 04:13:03 2016
From: matzew at apache.org (Matthias Wessendorf)
Date: Tue, 7 Jun 2016 10:13:03 +0200
Subject: [Aerogear-users] iOS Push issue when having multiple
	Installations
In-Reply-To: <143D1BBAE1FDE0459ADC21668AADEFC584616E55@EXMB2EU22.za.if.atcsg.net>
References: <143D1BBAE1FDE0459ADC21668AADEFC5846164E1@EXMB2EU22.za.if.atcsg.net>
	<CAAg5f2RR_ekTOscsn2zjEAHkxPiy_zD+j1qOtTxxTU2PNzWN-Q@mail.gmail.com>
	<143D1BBAE1FDE0459ADC21668AADEFC584616506@EXMB2EU22.za.if.atcsg.net>
	<CAAg5f2RXbe6Yqs=A=wSznMZZLDfU=CUZWQLbqjV2DVG=cckw3w@mail.gmail.com>
	<143D1BBAE1FDE0459ADC21668AADEFC5846167CC@EXMB2EU22.za.if.atcsg.net>
	<CAAg5f2RTc0N7-epCxc9iUd+8_e6UgOVchS=bW7ZaZi+5g6D1fQ@mail.gmail.com>
	<143D1BBAE1FDE0459ADC21668AADEFC584616E55@EXMB2EU22.za.if.atcsg.net>
Message-ID: <CAAg5f2QUt01e+qTrQgzyyEKy2N2AAADBVdfU+Kr1SpLDbxEjpA@mail.gmail.com>

On Tuesday, 7 June 2016, Bourillon, Matthias <
Matthias.Bourillon at saint-gobain.com> wrote:

> Hello Matthias,
>
> We are still in 1.0.0 as 1.1.0 migration process fails with our instance.
>
>
hrm, any pointers?


> To me, invalid tokens have been added on the server due to App development
> process during which App with development provisioning profile have
> registered against the server.
>
> yes!
Please note, dev/prod variant settings should not be mixed, for different
reasons



>
>
> If I understand correctly, in 1.1.0, if we have Dev token registered
> against the server they?ll be discovered invalid by Aerogear server and
> message sending will not be impacted. Is this right?
>
>
>
> Thanks,
>
> Matthias
>
>
>
> *De :* aerogear-users-bounces at lists.jboss.org
> <javascript:_e(%7B%7D,'cvml','aerogear-users-bounces at lists.jboss.org');>
> [mailto:aerogear-users-bounces at lists.jboss.org
> <javascript:_e(%7B%7D,'cvml','aerogear-users-bounces at lists.jboss.org');>] *De
> la part de* Matthias Wessendorf
> *Envoy? :* lundi 6 juin 2016 21:17
> *? :* aerogear-users at lists.jboss.org
> <javascript:_e(%7B%7D,'cvml','aerogear-users at lists.jboss.org');>
> *Objet :* Re: [Aerogear-users] iOS Push issue when having multiple
> Installations
>
>
>
> are you using the 1.1.0 ?
>
>
>
> I think it should not stop.
>
>
>
> Question: how did invalid tokens end up at the server?
>
>
>
> On Mon, Jun 6, 2016 at 4:56 PM, Bourillon, Matthias <
> Matthias.Bourillon at saint-gobain.com
> <javascript:_e(%7B%7D,'cvml','Matthias.Bourillon at saint-gobain.com');>>
> wrote:
>
> Matthias,
>
> I wanted to validate this behavior and I just created a script, manually
> sending a Payload to Apple Push service, 1 by 1 to our 89 installations.
> I am getting the same behavior : as soon as a payload is being sent to an
> invalid token, remaining payloads are not sent to devices. Is this
> something Apple block on their side?
>
>
>
> Thanks,
>
> Matthias
>
>
>
> *De :* aerogear-users-bounces at lists.jboss.org
> <javascript:_e(%7B%7D,'cvml','aerogear-users-bounces at lists.jboss.org');>
> [mailto:aerogear-users-bounces at lists.jboss.org
> <javascript:_e(%7B%7D,'cvml','aerogear-users-bounces at lists.jboss.org');>] *De
> la part de* Matthias Wessendorf
> *Envoy? :* lundi 6 juin 2016 12:40
>
>
> *? :* aerogear-users at lists.jboss.org
> <javascript:_e(%7B%7D,'cvml','aerogear-users at lists.jboss.org');>
> *Objet :* Re: [Aerogear-users] iOS Push issue when having multiple
> Installations
>
>
>
> I think yes, the problem was the a mix of tokens for different profiles
> (e.g. dev vs. prod)
>
>
>
> -M
>
>
>
> On Mon, Jun 6, 2016 at 11:32 AM, Bourillon, Matthias <
> Matthias.Bourillon at saint-gobain.com
> <javascript:_e(%7B%7D,'cvml','Matthias.Bourillon at saint-gobain.com');>>
> wrote:
>
> Matthias,
>
> Does the behaviour I described makes sense?
>
> In 1.0.0, if one of the token is invalid, can it block the whole push
> sending to other tokens?
>
>
>
> Matthias
>
>
>
> *De :* aerogear-users-bounces at lists.jboss.org
> <javascript:_e(%7B%7D,'cvml','aerogear-users-bounces at lists.jboss.org');>
> [mailto:aerogear-users-bounces at lists.jboss.org
> <javascript:_e(%7B%7D,'cvml','aerogear-users-bounces at lists.jboss.org');>] *De
> la part de* Matthias Wessendorf
> *Envoy? :* lundi 6 juin 2016 11:20
> *? :* aerogear-users at lists.jboss.org
> <javascript:_e(%7B%7D,'cvml','aerogear-users at lists.jboss.org');>
> *Objet :* Re: [Aerogear-users] iOS Push issue when having multiple
> Installations
>
>
>
> Hi,
>
>
>
> I think you are hitting a a bug. in the 1.1.0 series we did add a catch
> for reported invalid tokens:
>
>
> https://github.com/aerogear/aerogear-unifiedpush-server/commit/a44773a8dba1d9ce57a99de2dc11463f16e8e79f
>
>
>
> -Matthias
>
>
>
> On Mon, Jun 6, 2016 at 11:14 AM, Bourillon, Matthias <
> Matthias.Bourillon at saint-gobain.com
> <javascript:_e(%7B%7D,'cvml','Matthias.Bourillon at saint-gobain.com');>>
> wrote:
>
> Hello,
>
> We are facing an issue while using Aerogear Push Server with an iOS
> variant.
>
> Here is the scenario :
>
> 1.       We have 89 installations registered against an iOS Production
> Variant
>
> 2.       We send a message
>
> 3.       No one receive the message on our iOS App
>
> 4.       We disable ALL installations but 1
>
> 5.       We send a message
>
> 6.       The 1 device receives the push notification and works as expected
>
>
>
> We have other iOS variants with thousands of registrations working without
> any problem like this.
>
>
>
> Can the number of registered device impact the sending behavior? Can a
> wrong token or anything else block the notification sending to Apple? Logs
> do not seem to complain about any particular issue.
>
> We are using Aerogear Push Server 1.0.0.
>
>
>
> Thanks,
>
> Matthias
>
>
> _______________________________________________
> Aerogear-users mailing list
> Aerogear-users at lists.jboss.org
> <javascript:_e(%7B%7D,'cvml','Aerogear-users at lists.jboss.org');>
> https://lists.jboss.org/mailman/listinfo/aerogear-users
>
>
>
>
>
> --
>
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> twitter: http://twitter.com/mwessendorf
>
>
> _______________________________________________
> Aerogear-users mailing list
> Aerogear-users at lists.jboss.org
> <javascript:_e(%7B%7D,'cvml','Aerogear-users at lists.jboss.org');>
> https://lists.jboss.org/mailman/listinfo/aerogear-users
>
>
>
>
>
> --
>
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> twitter: http://twitter.com/mwessendorf
>
>
> _______________________________________________
> Aerogear-users mailing list
> Aerogear-users at lists.jboss.org
> <javascript:_e(%7B%7D,'cvml','Aerogear-users at lists.jboss.org');>
> https://lists.jboss.org/mailman/listinfo/aerogear-users
>
>
>
>
>
> --
>
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> twitter: http://twitter.com/mwessendorf
>


-- 
Sent from Gmail Mobile
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20160607/82872de2/attachment.html 

From mridul.choudhury at skymetweather.com  Fri Jun 10 09:52:42 2016
From: mridul.choudhury at skymetweather.com (mridul)
Date: Fri, 10 Jun 2016 06:52:42 -0700 (MST)
Subject: [Aerogear-users] SSL issue at Amazon EC2 With
 aerogear-unifiedpush-server-1.2.0-alpha.1 on Wildfly 10 , Java 8
Message-ID: <1465566762008-718.post@n5.nabble.com>

Hi,
    I am successfully running a test for
aerogear-unifiedpush-server-1.2.0-alpha.1 on Wildfly 10 , Java 8  in my
office network with perfect access , registration of devices and messaging
by using https://my_pub_ip:8443/ag-push. So far so good, now last Monday I
set up the same environment (for production purposes) at Amazone EC2
instance and tested it with Self signed keys. I am able to access
https://amazone_pub_ip:8443 , it displays me the wildfly index page. The
moment I access /ag-push in amazone ec2 instance I get a run time exception
as below :

18:16:20,702 ERROR [io.undertow.request] (default task-22) UT005023:
Exception handling request to /ag-push/: java.lang.RuntimeException: Unable
to resolve realm public key remotely
	at
org.keycloak.adapters.AdapterDeploymentContext.resolveRealmKey(AdapterDeploymentContext.java:136)
	at
org.keycloak.adapters.AdapterDeploymentContext.resolveDeployment(AdapterDeploymentContext.java:85)
	at
org.keycloak.adapters.PreAuthActionsHandler.preflightCors(PreAuthActionsHandler.java:74)
	at
org.keycloak.adapters.PreAuthActionsHandler.handleRequest(PreAuthActionsHandler.java:50)
	at
org.keycloak.adapters.undertow.ServletPreAuthActionsHandler.handleRequest(ServletPreAuthActionsHandler.java:68)
	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: java.net.ConnectException: Connection timed out
	at java.net.PlainSocketImpl.socketConnect(Native Method)
	at
java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
	at
java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
	at
java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
	at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
	at java.net.Socket.connect(Socket.java:589)
	at sun.security.ssl.SSLSocketImpl.connect(SSLSocketImpl.java:668)
	at
org.apache.http.conn.ssl.SSLSocketFactory.connectSocket(SSLSocketFactory.java:524)
	at
org.apache.http.conn.ssl.SSLSocketFactory.connectSocket(SSLSocketFactory.java:403)
	at
org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:177)
	at
org.apache.http.impl.conn.AbstractPoolEntry.open(AbstractPoolEntry.java:144)
	at
org.apache.http.impl.conn.AbstractPooledConnAdapter.open(AbstractPooledConnAdapter.java:131)
	at
org.apache.http.impl.client.DefaultRequestDirector.tryConnect(DefaultRequestDirector.java:611)
	at
org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:446)
	at
org.apache.http.impl.client.AbstractHttpClient.doExecute(AbstractHttpClient.java:863)
	at
org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82)
	at
org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:106)
	at
org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:57)
	at
org.keycloak.adapters.AdapterDeploymentContext.resolveRealmKey(AdapterDeploymentContext.java:107)

 
Please share some insight to this issue 

Thanks.
Mridul.




--
View this message in context: http://aerogear-users.1116366.n5.nabble.com/SSL-issue-at-Amazon-EC2-With-aerogear-unifiedpush-server-1-2-0-alpha-1-on-Wildfly-10-Java-8-tp718.html
Sent from the aerogear-users mailing list archive at Nabble.com.

From matzew at apache.org  Sun Jun 12 03:54:00 2016
From: matzew at apache.org (Matthias Wessendorf)
Date: Sun, 12 Jun 2016 09:54:00 +0200
Subject: [Aerogear-users] SSL issue at Amazon EC2 With
 aerogear-unifiedpush-server-1.2.0-alpha.1 on Wildfly 10 , Java 8
In-Reply-To: <1465566762008-718.post@n5.nabble.com>
References: <1465566762008-718.post@n5.nabble.com>
Message-ID: <CAAg5f2Sx31oTHHYg_Qm3toQZFZmQ8jDr6-hrsFKzFEpLw9sH0Q@mail.gmail.com>

not sure, perhaps you might ask on the Keycloak list for this adapter issue?

On Fri, Jun 10, 2016 at 3:52 PM, mridul <mridul.choudhury at skymetweather.com>
wrote:

> Hi,
>     I am successfully running a test for
> aerogear-unifiedpush-server-1.2.0-alpha.1 on Wildfly 10 , Java 8  in my
> office network with perfect access , registration of devices and messaging
> by using https://my_pub_ip:8443/ag-push. So far so good, now last Monday I
> set up the same environment (for production purposes) at Amazone EC2
> instance and tested it with Self signed keys. I am able to access
> https://amazone_pub_ip:8443 , it displays me the wildfly index page. The
> moment I access /ag-push in amazone ec2 instance I get a run time exception
> as below :
>
> 18:16:20,702 ERROR [io.undertow.request] (default task-22) UT005023:
> Exception handling request to /ag-push/: java.lang.RuntimeException: Unable
> to resolve realm public key remotely
>         at
>
> org.keycloak.adapters.AdapterDeploymentContext.resolveRealmKey(AdapterDeploymentContext.java:136)
>         at
>
> org.keycloak.adapters.AdapterDeploymentContext.resolveDeployment(AdapterDeploymentContext.java:85)
>         at
>
> org.keycloak.adapters.PreAuthActionsHandler.preflightCors(PreAuthActionsHandler.java:74)
>         at
>
> org.keycloak.adapters.PreAuthActionsHandler.handleRequest(PreAuthActionsHandler.java:50)
>         at
>
> org.keycloak.adapters.undertow.ServletPreAuthActionsHandler.handleRequest(ServletPreAuthActionsHandler.java:68)
>         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: java.net.ConnectException: Connection timed out
>         at java.net.PlainSocketImpl.socketConnect(Native Method)
>         at
>
> java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
>         at
>
> java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
>         at
> java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
>         at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
>         at java.net.Socket.connect(Socket.java:589)
>         at sun.security.ssl.SSLSocketImpl.connect(SSLSocketImpl.java:668)
>         at
>
> org.apache.http.conn.ssl.SSLSocketFactory.connectSocket(SSLSocketFactory.java:524)
>         at
>
> org.apache.http.conn.ssl.SSLSocketFactory.connectSocket(SSLSocketFactory.java:403)
>         at
>
> org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:177)
>         at
>
> org.apache.http.impl.conn.AbstractPoolEntry.open(AbstractPoolEntry.java:144)
>         at
>
> org.apache.http.impl.conn.AbstractPooledConnAdapter.open(AbstractPooledConnAdapter.java:131)
>         at
>
> org.apache.http.impl.client.DefaultRequestDirector.tryConnect(DefaultRequestDirector.java:611)
>         at
>
> org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:446)
>         at
>
> org.apache.http.impl.client.AbstractHttpClient.doExecute(AbstractHttpClient.java:863)
>         at
>
> org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82)
>         at
>
> org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:106)
>         at
>
> org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:57)
>         at
>
> org.keycloak.adapters.AdapterDeploymentContext.resolveRealmKey(AdapterDeploymentContext.java:107)
>
>
> Please share some insight to this issue
>
> Thanks.
> Mridul.
>
>
>
>
> --
> View this message in context:
> http://aerogear-users.1116366.n5.nabble.com/SSL-issue-at-Amazon-EC2-With-aerogear-unifiedpush-server-1-2-0-alpha-1-on-Wildfly-10-Java-8-tp718.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/
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20160612/e5e656b3/attachment.html 

From raghavendra.dabbir at gmail.com  Mon Jun 13 02:38:48 2016
From: raghavendra.dabbir at gmail.com (Raghavendra)
Date: Sun, 12 Jun 2016 23:38:48 -0700 (MST)
Subject: [Aerogear-users] Aerogear Push Notification in iOS
In-Reply-To: <574E8827.2030305@dynamease.com>
References: <1464764123888-691.post@n5.nabble.com>
	<574E8827.2030305@dynamease.com>
Message-ID: <1465799928736-720.post@n5.nabble.com>

Hi,

I still have this issue. The below is my further analysis

Pls help.

- The issue found so far has no challenges with the below:
a.	Mac
b.	Provisioning profile
c.	Certificate
d.	Developer profile
e.	Native vs Hybrid

- The issue occurs only when the iPA is generated from ?Archive?. This issue
does not occur if the iPA is automatically set into device using XCODE Run.




--
View this message in context: http://aerogear-users.1116366.n5.nabble.com/Aerogear-Push-Notification-in-iOS-tp691p720.html
Sent from the aerogear-users mailing list archive at Nabble.com.


From matzew at apache.org  Mon Jun 13 04:11:23 2016
From: matzew at apache.org (Matthias Wessendorf)
Date: Mon, 13 Jun 2016 10:11:23 +0200
Subject: [Aerogear-users] Aerogear Push Notification in iOS
In-Reply-To: <1465799928736-720.post@n5.nabble.com>
References: <1464764123888-691.post@n5.nabble.com>
	<574E8827.2030305@dynamease.com>
	<1465799928736-720.post@n5.nabble.com>
Message-ID: <CAAg5f2QGeTbX4tjktqHcp=5hP8S5Km4Paw4niD3Aj27TnK4AFA@mail.gmail.com>

Is archive a release build ? If so, you need a production cert.

Here is doc, how to get to the .p12 files:
https://aerogear.org/docs/unifiedpush/aerogear-push-ios/guides/#app-id-ssl-certificate-apns

On Mon, Jun 13, 2016 at 8:38 AM, Raghavendra <raghavendra.dabbir at gmail.com>
wrote:

> Hi,
>
> I still have this issue. The below is my further analysis
>
> Pls help.
>
> - The issue found so far has no challenges with the below:
> a.      Mac
> b.      Provisioning profile
> c.      Certificate
> d.      Developer profile
> e.      Native vs Hybrid
>
> - The issue occurs only when the iPA is generated from ?Archive?. This
> issue
> does not occur if the iPA is automatically set into device using XCODE Run.
>
>
>
>
> --
> View this message in context:
> http://aerogear-users.1116366.n5.nabble.com/Aerogear-Push-Notification-in-iOS-tp691p720.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/
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20160613/948fa6e7/attachment.html 

From edewit at redhat.com  Fri Jun 17 08:18:28 2016
From: edewit at redhat.com (Erik Jan de Wit)
Date: Fri, 17 Jun 2016 14:18:28 +0200
Subject: [Aerogear-users] [aerogear-dev] AeroGear Cordova release
In-Reply-To: <CAAg5f2Qxe2HUV4rE5aeJZZM69Hu7UiWfOsmpuozhLtR=ffXxbQ@mail.gmail.com>
References: <CAAg5f2S+jJrnJOPGk5oM-F3mS8ttxQBBuvD3ic7RQ3kzCp=iRg@mail.gmail.com>
	<CAO2B-fZYRnri-sGvgDeKJdm6Gia+sSXegR0cBXUM827P0dqyUQ@mail.gmail.com>
	<CAAg5f2Qxe2HUV4rE5aeJZZM69Hu7UiWfOsmpuozhLtR=ffXxbQ@mail.gmail.com>
Message-ID: <CAO2B-fY1uyeQZ4PLOJJqf2CbTm393-XV3RviTJ3YAH9=43Q3xA@mail.gmail.com>

Hi,

We are going to release another version of the aerogear push plugin, as
always I've created a branch for you to test. The biggest change it the use
of FCM for google so be sure to test it against a compatible UPS.

Add the plugin with the following command:

$> cordova plugin add
https://github.com/aerogear/aerogear-cordova-push.git\#release-3.0.0

?

Other changes are:

[image: Major] [image: Bug] AGCORDOVA-133
<https://issues.jboss.org/browse/AGCORDOVA-133> Library Dependencies
Conflict With Every Other Plugin Requiring The Same
<https://issues.jboss.org/browse/AGCORDOVA-133>

[image: Major] [image: Tracker] AGCORDOVA-134
<https://issues.jboss.org/browse/AGCORDOVA-134> geting problem in cordova
build <https://issues.jboss.org/browse/AGCORDOVA-134>

[image: Major] [image: Feature Request] AGCORDOVA-138
<https://issues.jboss.org/browse/AGCORDOVA-138> Update Cordova-Android to
use AGDROID 3.0.0 for GCM and InstanceID
<https://issues.jboss.org/browse/AGCORDOVA-138>


[image: Major] [image: Task] AGCORDOVA-140
<https://issues.jboss.org/browse/AGCORDOVA-140> AeroGear Cookbook Updates
<https://issues.jboss.org/browse/AGCORDOVA-140>


[image: Major] [image: Sub-task] AGCORDOVA-141
<https://issues.jboss.org/browse/AGCORDOVA-141> Push Hello World update
<https://issues.jboss.org/browse/AGCORDOVA-141>


[image: Major] [image: Feature Request] AGCORDOVA-145
<https://issues.jboss.org/browse/AGCORDOVA-145> Update Cordova-Android to
use FCM enabled AGDroid <https://issues.jboss.org/browse/AGCORDOVA-145>

On Fri, Jun 17, 2016 at 10:49 AM, Matthias Wessendorf <matzew at apache.org>
wrote:

> cool!
>
> On Thu, Jun 16, 2016 at 9:01 PM, Erik Jan de Wit <edewit at redhat.com>
> wrote:
>
>> yeah, let's do that
>>
>> On Thu, Jun 16, 2016 at 1:53 PM, Matthias Wessendorf <matzew at apache.org>
>> wrote:
>>
>>> Hi Erik,
>>>
>>> now that FCM got merged, can you tag and release the 3.0.0 bits ?
>>>
>>> -Matthias
>>>
>>> --
>>> Matthias Wessendorf
>>>
>>> blog: http://matthiaswessendorf.wordpress.com/
>>> twitter: http://twitter.com/mwessendorf
>>>
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>
>>
>>
>> --
>> Cheers,
>>        Erik Jan
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> twitter: http://twitter.com/mwessendorf
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



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

From matzew at apache.org  Fri Jun 17 09:14:30 2016
From: matzew at apache.org (Matthias Wessendorf)
Date: Fri, 17 Jun 2016 15:14:30 +0200
Subject: [Aerogear-users] [aerogear-dev] AeroGear Cordova release
In-Reply-To: <CAO2B-fY1uyeQZ4PLOJJqf2CbTm393-XV3RviTJ3YAH9=43Q3xA@mail.gmail.com>
References: <CAAg5f2S+jJrnJOPGk5oM-F3mS8ttxQBBuvD3ic7RQ3kzCp=iRg@mail.gmail.com>
	<CAO2B-fZYRnri-sGvgDeKJdm6Gia+sSXegR0cBXUM827P0dqyUQ@mail.gmail.com>
	<CAAg5f2Qxe2HUV4rE5aeJZZM69Hu7UiWfOsmpuozhLtR=ffXxbQ@mail.gmail.com>
	<CAO2B-fY1uyeQZ4PLOJJqf2CbTm393-XV3RviTJ3YAH9=43Q3xA@mail.gmail.com>
Message-ID: <CAAg5f2TVXq_1-p2=JF4XQ3BFFW3jxHNco67hYN3O1z6TZEaLBw@mail.gmail.com>

+1

On Fri, Jun 17, 2016 at 2:18 PM, Erik Jan de Wit <edewit at redhat.com> wrote:

> Hi,
>
> We are going to release another version of the aerogear push plugin, as
> always I've created a branch for you to test. The biggest change it the use
> of FCM for google so be sure to test it against a compatible UPS.
>
> Add the plugin with the following command:
>
> $> cordova plugin add https://github.com/aerogear/aerogear-cordova-push.git\#release-3.0.0
>
> ?
>
> Other changes are:
>
> [image: Major] [image: Bug] AGCORDOVA-133
> <https://issues.jboss.org/browse/AGCORDOVA-133> Library Dependencies
> Conflict With Every Other Plugin Requiring The Same
> <https://issues.jboss.org/browse/AGCORDOVA-133>
>
> [image: Major] [image: Tracker] AGCORDOVA-134
> <https://issues.jboss.org/browse/AGCORDOVA-134> geting problem in cordova
> build <https://issues.jboss.org/browse/AGCORDOVA-134>
>
> [image: Major] [image: Feature Request] AGCORDOVA-138
> <https://issues.jboss.org/browse/AGCORDOVA-138> Update Cordova-Android to
> use AGDROID 3.0.0 for GCM and InstanceID
> <https://issues.jboss.org/browse/AGCORDOVA-138>
>
>
> [image: Major] [image: Task] AGCORDOVA-140
> <https://issues.jboss.org/browse/AGCORDOVA-140> AeroGear Cookbook Updates
> <https://issues.jboss.org/browse/AGCORDOVA-140>
>
>
> [image: Major] [image: Sub-task] AGCORDOVA-141
> <https://issues.jboss.org/browse/AGCORDOVA-141> Push Hello World update
> <https://issues.jboss.org/browse/AGCORDOVA-141>
>
>
> [image: Major] [image: Feature Request] AGCORDOVA-145
> <https://issues.jboss.org/browse/AGCORDOVA-145> Update Cordova-Android to
> use FCM enabled AGDroid <https://issues.jboss.org/browse/AGCORDOVA-145>
>
> On Fri, Jun 17, 2016 at 10:49 AM, Matthias Wessendorf <matzew at apache.org>
> wrote:
>
>> cool!
>>
>> On Thu, Jun 16, 2016 at 9:01 PM, Erik Jan de Wit <edewit at redhat.com>
>> wrote:
>>
>>> yeah, let's do that
>>>
>>> On Thu, Jun 16, 2016 at 1:53 PM, Matthias Wessendorf <matzew at apache.org>
>>> wrote:
>>>
>>>> Hi Erik,
>>>>
>>>> now that FCM got merged, can you tag and release the 3.0.0 bits ?
>>>>
>>>> -Matthias
>>>>
>>>> --
>>>> Matthias Wessendorf
>>>>
>>>> blog: http://matthiaswessendorf.wordpress.com/
>>>> twitter: http://twitter.com/mwessendorf
>>>>
>>>> _______________________________________________
>>>> aerogear-dev mailing list
>>>> aerogear-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>
>>>
>>>
>>>
>>> --
>>> Cheers,
>>>        Erik Jan
>>>
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>
>>
>>
>> --
>> Matthias Wessendorf
>>
>> blog: http://matthiaswessendorf.wordpress.com/
>> twitter: http://twitter.com/mwessendorf
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
>
> --
> Cheers,
>        Erik Jan
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20160617/44f36457/attachment.html 

From Romain.Javornik at saint-gobain.com  Fri Jun 17 10:11:09 2016
From: Romain.Javornik at saint-gobain.com (Javornik, Romain)
Date: Fri, 17 Jun 2016 14:11:09 +0000
Subject: [Aerogear-users] iOS Push issue when having multiple
 Installations
Message-ID: <144EA958C5BCB144849B6DF3DD05867C98608F@EXMB1EU12.za.if.atcsg.net>

Hello Matthias,

in regard of the upgrade, we were running the 1.0.2 and we migrate to the 1.1.1, here some problem you might want to be aware of.

The update was smooth from 1.0.2 to 1.0.3, but I have to add the parameter ?transformedBitIsBoolean? in our DB connection (standalone.xml).
<connection-url>jdbc:mysql://localhost:3306/unifiedpush?transformedBitIsBoolean=true</connection-url>

But it was quite hard for us to update to 1.1.0 from our 1.0.3, the problem where coming from our DB :

?         Redundancy of FK

?         Wrong data type

?         Wrong data order in the table (even if it shouldn?t matter, it does for some reasons)

?         Wrong table name

So basically our database was not in sync with the one the migrator tool expect, specially the part related to the table ?variant?.

The way we proceed to make the migration is the following :

1.       We made some modification in our current database (creation of columns, change columns order in table)

2.       We exported the data, and reimport all of it in a fresh 1.0.3 installation

3.       We run the migrator tool to 1.1.0

4.       We add in variant.VARIANT_TYPE the type of OS (ios, android) wich was missing

The modifications made in the step 1 make the data import in the step 2 possible,
they come from the differences between our schema and the schema from scratch.

Best Regards,
Romain

De : Bourillon, Matthias
Envoy? : mercredi 15 juin 2016 11:45
? : Javornik, Romain
Objet : Re: [Aerogear-users] iOS Push issue when having multiple Installations

Fait un reply l?-dessus sur la liste aerogear-users at lists.jboss.org<mailto:aerogear-users at lists.jboss.org>

De : aerogear-users-bounces at lists.jboss.org<mailto:aerogear-users-bounces at lists.jboss.org> [mailto:aerogear-users-bounces at lists.jboss.org] De la part de Matthias Wessendorf
Envoy? : mardi 7 juin 2016 10:13
? : aerogear-users at lists.jboss.org<mailto:aerogear-users at lists.jboss.org>
Objet : Re: [Aerogear-users] iOS Push issue when having multiple Installations



On Tuesday, 7 June 2016, Bourillon, Matthias <Matthias.Bourillon at saint-gobain.com<mailto:Matthias.Bourillon at saint-gobain.com>> wrote:
Hello Matthias,
We are still in 1.0.0 as 1.1.0 migration process fails with our instance.

hrm, any pointers?

To me, invalid tokens have been added on the server due to App development process during which App with development provisioning profile have registered against the server.
yes!
Please note, dev/prod variant settings should not be mixed, for different reasons



If I understand correctly, in 1.1.0, if we have Dev token registered against the server they?ll be discovered invalid by Aerogear server and message sending will not be impacted. Is this right?

Thanks,
Matthias

De : aerogear-users-bounces at lists.jboss.org<javascript:_e(%7B%7D,'cvml','aerogear-users-bounces at lists.jboss.org');> [mailto:aerogear-users-bounces at lists.jboss.org<javascript:_e(%7B%7D,'cvml','aerogear-users-bounces at lists.jboss.org');>] De la part de Matthias Wessendorf
Envoy? : lundi 6 juin 2016 21:17
? : aerogear-users at lists.jboss.org<javascript:_e(%7B%7D,'cvml','aerogear-users at lists.jboss.org');>
Objet : Re: [Aerogear-users] iOS Push issue when having multiple Installations

are you using the 1.1.0 ?

I think it should not stop.

Question: how did invalid tokens end up at the server?

On Mon, Jun 6, 2016 at 4:56 PM, Bourillon, Matthias <Matthias.Bourillon at saint-gobain.com<javascript:_e(%7B%7D,'cvml','Matthias.Bourillon at saint-gobain.com');>> wrote:
Matthias,
I wanted to validate this behavior and I just created a script, manually sending a Payload to Apple Push service, 1 by 1 to our 89 installations.
I am getting the same behavior : as soon as a payload is being sent to an invalid token, remaining payloads are not sent to devices. Is this something Apple block on their side?

Thanks,
Matthias

De : aerogear-users-bounces at lists.jboss.org<javascript:_e(%7B%7D,'cvml','aerogear-users-bounces at lists.jboss.org');> [mailto:aerogear-users-bounces at lists.jboss.org<javascript:_e(%7B%7D,'cvml','aerogear-users-bounces at lists.jboss.org');>] De la part de Matthias Wessendorf
Envoy? : lundi 6 juin 2016 12:40

? : aerogear-users at lists.jboss.org<javascript:_e(%7B%7D,'cvml','aerogear-users at lists.jboss.org');>
Objet : Re: [Aerogear-users] iOS Push issue when having multiple Installations

I think yes, the problem was the a mix of tokens for different profiles (e.g. dev vs. prod)

-M

On Mon, Jun 6, 2016 at 11:32 AM, Bourillon, Matthias <Matthias.Bourillon at saint-gobain.com<javascript:_e(%7B%7D,'cvml','Matthias.Bourillon at saint-gobain.com');>> wrote:
Matthias,
Does the behaviour I described makes sense?
In 1.0.0, if one of the token is invalid, can it block the whole push sending to other tokens?

Matthias

De : aerogear-users-bounces at lists.jboss.org<javascript:_e(%7B%7D,'cvml','aerogear-users-bounces at lists.jboss.org');> [mailto:aerogear-users-bounces at lists.jboss.org<javascript:_e(%7B%7D,'cvml','aerogear-users-bounces at lists.jboss.org');>] De la part de Matthias Wessendorf
Envoy? : lundi 6 juin 2016 11:20
? : aerogear-users at lists.jboss.org<javascript:_e(%7B%7D,'cvml','aerogear-users at lists.jboss.org');>
Objet : Re: [Aerogear-users] iOS Push issue when having multiple Installations

Hi,

I think you are hitting a a bug. in the 1.1.0 series we did add a catch for reported invalid tokens:
https://github.com/aerogear/aerogear-unifiedpush-server/commit/a44773a8dba1d9ce57a99de2dc11463f16e8e79f

-Matthias

On Mon, Jun 6, 2016 at 11:14 AM, Bourillon, Matthias <Matthias.Bourillon at saint-gobain.com<javascript:_e(%7B%7D,'cvml','Matthias.Bourillon at saint-gobain.com');>> wrote:
Hello,
We are facing an issue while using Aerogear Push Server with an iOS variant.
Here is the scenario :

1.       We have 89 installations registered against an iOS Production Variant

2.       We send a message

3.       No one receive the message on our iOS App

4.       We disable ALL installations but 1

5.       We send a message

6.       The 1 device receives the push notification and works as expected

We have other iOS variants with thousands of registrations working without any problem like this.

Can the number of registered device impact the sending behavior? Can a wrong token or anything else block the notification sending to Apple? Logs do not seem to complain about any particular issue.
We are using Aerogear Push Server 1.0.0.

Thanks,
Matthias

_______________________________________________
Aerogear-users mailing list
Aerogear-users at lists.jboss.org<javascript:_e(%7B%7D,'cvml','Aerogear-users at lists.jboss.org');>
https://lists.jboss.org/mailman/listinfo/aerogear-users



--
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
twitter: http://twitter.com/mwessendorf

_______________________________________________
Aerogear-users mailing list
Aerogear-users at lists.jboss.org<javascript:_e(%7B%7D,'cvml','Aerogear-users at lists.jboss.org');>
https://lists.jboss.org/mailman/listinfo/aerogear-users



--
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
twitter: http://twitter.com/mwessendorf

_______________________________________________
Aerogear-users mailing list
Aerogear-users at lists.jboss.org<javascript:_e(%7B%7D,'cvml','Aerogear-users at lists.jboss.org');>
https://lists.jboss.org/mailman/listinfo/aerogear-users



--
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
twitter: http://twitter.com/mwessendorf


--
Sent from Gmail Mobile
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20160617/9805fc05/attachment-0001.html 

From matzew at apache.org  Mon Jun 20 02:49:34 2016
From: matzew at apache.org (Matthias Wessendorf)
Date: Mon, 20 Jun 2016 08:49:34 +0200
Subject: [Aerogear-users] [aerogear-dev] AeroGear Cordova release
In-Reply-To: <CAAg5f2TVXq_1-p2=JF4XQ3BFFW3jxHNco67hYN3O1z6TZEaLBw@mail.gmail.com>
References: <CAAg5f2S+jJrnJOPGk5oM-F3mS8ttxQBBuvD3ic7RQ3kzCp=iRg@mail.gmail.com>
	<CAO2B-fZYRnri-sGvgDeKJdm6Gia+sSXegR0cBXUM827P0dqyUQ@mail.gmail.com>
	<CAAg5f2Qxe2HUV4rE5aeJZZM69Hu7UiWfOsmpuozhLtR=ffXxbQ@mail.gmail.com>
	<CAO2B-fY1uyeQZ4PLOJJqf2CbTm393-XV3RviTJ3YAH9=43Q3xA@mail.gmail.com>
	<CAAg5f2TVXq_1-p2=JF4XQ3BFFW3jxHNco67hYN3O1z6TZEaLBw@mail.gmail.com>
Message-ID: <CAAg5f2SxdpNUtB0pbyRzi+bo3uDGW3gx2q2Df5HKE=38L1aicQ@mail.gmail.com>

Actually, see other thread.
-1 on releasing

On Fri, Jun 17, 2016 at 3:14 PM, Matthias Wessendorf <matzew at apache.org>
wrote:

> +1
>
> On Fri, Jun 17, 2016 at 2:18 PM, Erik Jan de Wit <edewit at redhat.com>
> wrote:
>
>> Hi,
>>
>> We are going to release another version of the aerogear push plugin, as
>> always I've created a branch for you to test. The biggest change it the use
>> of FCM for google so be sure to test it against a compatible UPS.
>>
>> Add the plugin with the following command:
>>
>> $> cordova plugin add https://github.com/aerogear/aerogear-cordova-push.git\#release-3.0.0
>>
>> ?
>>
>> Other changes are:
>>
>> [image: Major] [image: Bug] AGCORDOVA-133
>> <https://issues.jboss.org/browse/AGCORDOVA-133> Library Dependencies
>> Conflict With Every Other Plugin Requiring The Same
>> <https://issues.jboss.org/browse/AGCORDOVA-133>
>>
>> [image: Major] [image: Tracker] AGCORDOVA-134
>> <https://issues.jboss.org/browse/AGCORDOVA-134> geting problem in
>> cordova build <https://issues.jboss.org/browse/AGCORDOVA-134>
>>
>> [image: Major] [image: Feature Request] AGCORDOVA-138
>> <https://issues.jboss.org/browse/AGCORDOVA-138> Update Cordova-Android
>> to use AGDROID 3.0.0 for GCM and InstanceID
>> <https://issues.jboss.org/browse/AGCORDOVA-138>
>>
>>
>> [image: Major] [image: Task] AGCORDOVA-140
>> <https://issues.jboss.org/browse/AGCORDOVA-140> AeroGear Cookbook Updates
>> <https://issues.jboss.org/browse/AGCORDOVA-140>
>>
>>
>> [image: Major] [image: Sub-task] AGCORDOVA-141
>> <https://issues.jboss.org/browse/AGCORDOVA-141> Push Hello World update
>> <https://issues.jboss.org/browse/AGCORDOVA-141>
>>
>>
>> [image: Major] [image: Feature Request] AGCORDOVA-145
>> <https://issues.jboss.org/browse/AGCORDOVA-145> Update Cordova-Android
>> to use FCM enabled AGDroid
>> <https://issues.jboss.org/browse/AGCORDOVA-145>
>>
>> On Fri, Jun 17, 2016 at 10:49 AM, Matthias Wessendorf <matzew at apache.org>
>> wrote:
>>
>>> cool!
>>>
>>> On Thu, Jun 16, 2016 at 9:01 PM, Erik Jan de Wit <edewit at redhat.com>
>>> wrote:
>>>
>>>> yeah, let's do that
>>>>
>>>> On Thu, Jun 16, 2016 at 1:53 PM, Matthias Wessendorf <matzew at apache.org
>>>> > wrote:
>>>>
>>>>> Hi Erik,
>>>>>
>>>>> now that FCM got merged, can you tag and release the 3.0.0 bits ?
>>>>>
>>>>> -Matthias
>>>>>
>>>>> --
>>>>> Matthias Wessendorf
>>>>>
>>>>> blog: http://matthiaswessendorf.wordpress.com/
>>>>> twitter: http://twitter.com/mwessendorf
>>>>>
>>>>> _______________________________________________
>>>>> aerogear-dev mailing list
>>>>> aerogear-dev at lists.jboss.org
>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Cheers,
>>>>        Erik Jan
>>>>
>>>> _______________________________________________
>>>> aerogear-dev mailing list
>>>> aerogear-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>
>>>
>>>
>>>
>>> --
>>> Matthias Wessendorf
>>>
>>> blog: http://matthiaswessendorf.wordpress.com/
>>> twitter: http://twitter.com/mwessendorf
>>>
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>
>>
>>
>> --
>> Cheers,
>>        Erik Jan
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> twitter: http://twitter.com/mwessendorf
>



-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20160620/40b44db5/attachment.html 

From Matthias.Bourillon at saint-gobain.com  Mon Jun 20 12:10:45 2016
From: Matthias.Bourillon at saint-gobain.com (Bourillon, Matthias)
Date: Mon, 20 Jun 2016 16:10:45 +0000
Subject: [Aerogear-users] iOS Push issue when having
	multiple	Installations
In-Reply-To: <CAAg5f2RXbe6Yqs=A=wSznMZZLDfU=CUZWQLbqjV2DVG=cckw3w@mail.gmail.com>
References: <143D1BBAE1FDE0459ADC21668AADEFC5846164E1@EXMB2EU22.za.if.atcsg.net>
	<CAAg5f2RR_ekTOscsn2zjEAHkxPiy_zD+j1qOtTxxTU2PNzWN-Q@mail.gmail.com>
	<143D1BBAE1FDE0459ADC21668AADEFC584616506@EXMB2EU22.za.if.atcsg.net>
	<CAAg5f2RXbe6Yqs=A=wSznMZZLDfU=CUZWQLbqjV2DVG=cckw3w@mail.gmail.com>
Message-ID: <143D1BBAE1FDE0459ADC21668AADEFC58461D390@EXMB2EU22.za.if.atcsg.net>

Hello Matthias,
Last week we migrated from 1.0.0 to 1.1.0.
Today, after a Push Notification got sent, we had following errors in logs :

16:53:11,978 WARN  [com.notnoop.apns.internal.ApnsConnectionImpl] (MonitoringThread-1) Received error for message that wasn't in the cache...
16:53:11,978 WARNING [org.jboss.aerogear.unifiedpush.message.sender.APNsPushNotificationSender] (MonitoringThread-1) Internal cache size exceeded, new size is: 150
16:53:11,978 SEVERE [org.jboss.aerogear.unifiedpush.message.sender.APNsPushNotificationSender] (MonitoringThread-1) Error sending payload to APNs server: com.notnoop.exceptions.ApnsDeliveryErrorException: Failed to deliver notification with error code 8
                at com.notnoop.apns.internal.ApnsConnectionImpl$2.run(ApnsConnectionImpl.java:199) [apns-1.0.0.Beta6.jar:]
                at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_75]

Does this means some invalid tokens were found?
In that case, do they get deleted from Installations and is the Push server able to recover by himself and send other push to other tokens?
Or do we need to re-send the message again ?

Thanks,
Matthias


De : aerogear-users-bounces at lists.jboss.org [mailto:aerogear-users-bounces at lists.jboss.org] De la part de Matthias Wessendorf
Envoy? : lundi 6 juin 2016 12:40
? : aerogear-users at lists.jboss.org
Objet : Re: [Aerogear-users] iOS Push issue when having multiple Installations

I think yes, the problem was the a mix of tokens for different profiles (e.g. dev vs. prod)

-M

On Mon, Jun 6, 2016 at 11:32 AM, Bourillon, Matthias <Matthias.Bourillon at saint-gobain.com<mailto:Matthias.Bourillon at saint-gobain.com>> wrote:
Matthias,
Does the behaviour I described makes sense?
In 1.0.0, if one of the token is invalid, can it block the whole push sending to other tokens?

Matthias

De : aerogear-users-bounces at lists.jboss.org<mailto:aerogear-users-bounces at lists.jboss.org> [mailto:aerogear-users-bounces at lists.jboss.org<mailto:aerogear-users-bounces at lists.jboss.org>] De la part de Matthias Wessendorf
Envoy? : lundi 6 juin 2016 11:20
? : aerogear-users at lists.jboss.org<mailto:aerogear-users at lists.jboss.org>
Objet : Re: [Aerogear-users] iOS Push issue when having multiple Installations

Hi,

I think you are hitting a a bug. in the 1.1.0 series we did add a catch for reported invalid tokens:
https://github.com/aerogear/aerogear-unifiedpush-server/commit/a44773a8dba1d9ce57a99de2dc11463f16e8e79f

-Matthias

On Mon, Jun 6, 2016 at 11:14 AM, Bourillon, Matthias <Matthias.Bourillon at saint-gobain.com<mailto:Matthias.Bourillon at saint-gobain.com>> wrote:
Hello,
We are facing an issue while using Aerogear Push Server with an iOS variant.
Here is the scenario :

1.       We have 89 installations registered against an iOS Production Variant

2.       We send a message

3.       No one receive the message on our iOS App

4.       We disable ALL installations but 1

5.       We send a message

6.       The 1 device receives the push notification and works as expected

We have other iOS variants with thousands of registrations working without any problem like this.

Can the number of registered device impact the sending behavior? Can a wrong token or anything else block the notification sending to Apple? Logs do not seem to complain about any particular issue.
We are using Aerogear Push Server 1.0.0.

Thanks,
Matthias

_______________________________________________
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/
twitter: http://twitter.com/mwessendorf

_______________________________________________
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/
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20160620/614eb4b6/attachment-0001.html 

From matzew at apache.org  Thu Jun 23 11:58:28 2016
From: matzew at apache.org (Matthias Wessendorf)
Date: Thu, 23 Jun 2016 17:58:28 +0200
Subject: [Aerogear-users] [aerogear-dev] AeroGear Cordova release
In-Reply-To: <CAAg5f2SxdpNUtB0pbyRzi+bo3uDGW3gx2q2Df5HKE=38L1aicQ@mail.gmail.com>
References: <CAAg5f2S+jJrnJOPGk5oM-F3mS8ttxQBBuvD3ic7RQ3kzCp=iRg@mail.gmail.com>
	<CAO2B-fZYRnri-sGvgDeKJdm6Gia+sSXegR0cBXUM827P0dqyUQ@mail.gmail.com>
	<CAAg5f2Qxe2HUV4rE5aeJZZM69Hu7UiWfOsmpuozhLtR=ffXxbQ@mail.gmail.com>
	<CAO2B-fY1uyeQZ4PLOJJqf2CbTm393-XV3RviTJ3YAH9=43Q3xA@mail.gmail.com>
	<CAAg5f2TVXq_1-p2=JF4XQ3BFFW3jxHNco67hYN3O1z6TZEaLBw@mail.gmail.com>
	<CAAg5f2SxdpNUtB0pbyRzi+bo3uDGW3gx2q2Df5HKE=38L1aicQ@mail.gmail.com>
Message-ID: <CAAg5f2RGCp6CzdhWRJ0yf6rYoKtGssNRjOYpFcgXf039KAte1w@mail.gmail.com>

since this is fixed, I am fine in tagging master to 3.0.0

On Mon, Jun 20, 2016 at 8:49 AM, Matthias Wessendorf <matzew at apache.org>
wrote:

> Actually, see other thread.
> -1 on releasing
>
> On Fri, Jun 17, 2016 at 3:14 PM, Matthias Wessendorf <matzew at apache.org>
> wrote:
>
>> +1
>>
>> On Fri, Jun 17, 2016 at 2:18 PM, Erik Jan de Wit <edewit at redhat.com>
>> wrote:
>>
>>> Hi,
>>>
>>> We are going to release another version of the aerogear push plugin, as
>>> always I've created a branch for you to test. The biggest change it the use
>>> of FCM for google so be sure to test it against a compatible UPS.
>>>
>>> Add the plugin with the following command:
>>>
>>> $> cordova plugin add https://github.com/aerogear/aerogear-cordova-push.git\#release-3.0.0
>>>
>>> ?
>>>
>>> Other changes are:
>>>
>>> [image: Major] [image: Bug] AGCORDOVA-133
>>> <https://issues.jboss.org/browse/AGCORDOVA-133> Library Dependencies
>>> Conflict With Every Other Plugin Requiring The Same
>>> <https://issues.jboss.org/browse/AGCORDOVA-133>
>>>
>>> [image: Major] [image: Tracker] AGCORDOVA-134
>>> <https://issues.jboss.org/browse/AGCORDOVA-134> geting problem in
>>> cordova build <https://issues.jboss.org/browse/AGCORDOVA-134>
>>>
>>> [image: Major] [image: Feature Request] AGCORDOVA-138
>>> <https://issues.jboss.org/browse/AGCORDOVA-138> Update Cordova-Android
>>> to use AGDROID 3.0.0 for GCM and InstanceID
>>> <https://issues.jboss.org/browse/AGCORDOVA-138>
>>>
>>>
>>> [image: Major] [image: Task] AGCORDOVA-140
>>> <https://issues.jboss.org/browse/AGCORDOVA-140> AeroGear Cookbook
>>> Updates <https://issues.jboss.org/browse/AGCORDOVA-140>
>>>
>>>
>>> [image: Major] [image: Sub-task] AGCORDOVA-141
>>> <https://issues.jboss.org/browse/AGCORDOVA-141> Push Hello World update
>>> <https://issues.jboss.org/browse/AGCORDOVA-141>
>>>
>>>
>>> [image: Major] [image: Feature Request] AGCORDOVA-145
>>> <https://issues.jboss.org/browse/AGCORDOVA-145> Update Cordova-Android
>>> to use FCM enabled AGDroid
>>> <https://issues.jboss.org/browse/AGCORDOVA-145>
>>>
>>> On Fri, Jun 17, 2016 at 10:49 AM, Matthias Wessendorf <matzew at apache.org
>>> > wrote:
>>>
>>>> cool!
>>>>
>>>> On Thu, Jun 16, 2016 at 9:01 PM, Erik Jan de Wit <edewit at redhat.com>
>>>> wrote:
>>>>
>>>>> yeah, let's do that
>>>>>
>>>>> On Thu, Jun 16, 2016 at 1:53 PM, Matthias Wessendorf <
>>>>> matzew at apache.org> wrote:
>>>>>
>>>>>> Hi Erik,
>>>>>>
>>>>>> now that FCM got merged, can you tag and release the 3.0.0 bits ?
>>>>>>
>>>>>> -Matthias
>>>>>>
>>>>>> --
>>>>>> Matthias Wessendorf
>>>>>>
>>>>>> blog: http://matthiaswessendorf.wordpress.com/
>>>>>> twitter: http://twitter.com/mwessendorf
>>>>>>
>>>>>> _______________________________________________
>>>>>> aerogear-dev mailing list
>>>>>> aerogear-dev at lists.jboss.org
>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Cheers,
>>>>>        Erik Jan
>>>>>
>>>>> _______________________________________________
>>>>> aerogear-dev mailing list
>>>>> aerogear-dev at lists.jboss.org
>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Matthias Wessendorf
>>>>
>>>> blog: http://matthiaswessendorf.wordpress.com/
>>>> twitter: http://twitter.com/mwessendorf
>>>>
>>>> _______________________________________________
>>>> aerogear-dev mailing list
>>>> aerogear-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>
>>>
>>>
>>>
>>> --
>>> Cheers,
>>>        Erik Jan
>>>
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>
>>
>>
>> --
>> Matthias Wessendorf
>>
>> blog: http://matthiaswessendorf.wordpress.com/
>> twitter: http://twitter.com/mwessendorf
>>
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> twitter: http://twitter.com/mwessendorf
>



-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20160623/f6bbb271/attachment.html 

From edewit at redhat.com  Thu Jun 23 12:23:14 2016
From: edewit at redhat.com (Erik Jan de Wit)
Date: Thu, 23 Jun 2016 18:23:14 +0200
Subject: [Aerogear-users] [aerogear-dev] AeroGear Cordova release
In-Reply-To: <CAAg5f2RGCp6CzdhWRJ0yf6rYoKtGssNRjOYpFcgXf039KAte1w@mail.gmail.com>
References: <CAAg5f2S+jJrnJOPGk5oM-F3mS8ttxQBBuvD3ic7RQ3kzCp=iRg@mail.gmail.com>
	<CAO2B-fZYRnri-sGvgDeKJdm6Gia+sSXegR0cBXUM827P0dqyUQ@mail.gmail.com>
	<CAAg5f2Qxe2HUV4rE5aeJZZM69Hu7UiWfOsmpuozhLtR=ffXxbQ@mail.gmail.com>
	<CAO2B-fY1uyeQZ4PLOJJqf2CbTm393-XV3RviTJ3YAH9=43Q3xA@mail.gmail.com>
	<CAAg5f2TVXq_1-p2=JF4XQ3BFFW3jxHNco67hYN3O1z6TZEaLBw@mail.gmail.com>
	<CAAg5f2SxdpNUtB0pbyRzi+bo3uDGW3gx2q2Df5HKE=38L1aicQ@mail.gmail.com>
	<CAAg5f2RGCp6CzdhWRJ0yf6rYoKtGssNRjOYpFcgXf039KAte1w@mail.gmail.com>
Message-ID: <CAO2B-fZnxsmu7ZLGZnJrgMZF4vMrwe+AJqS3FSsxQkTd0=MaAg@mail.gmail.com>

The release 3.0.0 has been published to npm thanks to everyone involved.

On Thu, Jun 23, 2016 at 5:58 PM, Matthias Wessendorf <matzew at apache.org>
wrote:

> since this is fixed, I am fine in tagging master to 3.0.0
>
> On Mon, Jun 20, 2016 at 8:49 AM, Matthias Wessendorf <matzew at apache.org>
> wrote:
>
>> Actually, see other thread.
>> -1 on releasing
>>
>> On Fri, Jun 17, 2016 at 3:14 PM, Matthias Wessendorf <matzew at apache.org>
>> wrote:
>>
>>> +1
>>>
>>> On Fri, Jun 17, 2016 at 2:18 PM, Erik Jan de Wit <edewit at redhat.com>
>>> wrote:
>>>
>>>> Hi,
>>>>
>>>> We are going to release another version of the aerogear push plugin, as
>>>> always I've created a branch for you to test. The biggest change it the use
>>>> of FCM for google so be sure to test it against a compatible UPS.
>>>>
>>>> Add the plugin with the following command:
>>>>
>>>> $> cordova plugin add https://github.com/aerogear/aerogear-cordova-push.git\#release-3.0.0
>>>>
>>>> ?
>>>>
>>>> Other changes are:
>>>>
>>>> [image: Major] [image: Bug] AGCORDOVA-133
>>>> <https://issues.jboss.org/browse/AGCORDOVA-133> Library Dependencies
>>>> Conflict With Every Other Plugin Requiring The Same
>>>> <https://issues.jboss.org/browse/AGCORDOVA-133>
>>>>
>>>> [image: Major] [image: Tracker] AGCORDOVA-134
>>>> <https://issues.jboss.org/browse/AGCORDOVA-134> geting problem in
>>>> cordova build <https://issues.jboss.org/browse/AGCORDOVA-134>
>>>>
>>>> [image: Major] [image: Feature Request] AGCORDOVA-138
>>>> <https://issues.jboss.org/browse/AGCORDOVA-138> Update Cordova-Android
>>>> to use AGDROID 3.0.0 for GCM and InstanceID
>>>> <https://issues.jboss.org/browse/AGCORDOVA-138>
>>>>
>>>>
>>>> [image: Major] [image: Task] AGCORDOVA-140
>>>> <https://issues.jboss.org/browse/AGCORDOVA-140> AeroGear Cookbook
>>>> Updates <https://issues.jboss.org/browse/AGCORDOVA-140>
>>>>
>>>>
>>>> [image: Major] [image: Sub-task] AGCORDOVA-141
>>>> <https://issues.jboss.org/browse/AGCORDOVA-141> Push Hello World update
>>>> <https://issues.jboss.org/browse/AGCORDOVA-141>
>>>>
>>>>
>>>> [image: Major] [image: Feature Request] AGCORDOVA-145
>>>> <https://issues.jboss.org/browse/AGCORDOVA-145> Update Cordova-Android
>>>> to use FCM enabled AGDroid
>>>> <https://issues.jboss.org/browse/AGCORDOVA-145>
>>>>
>>>> On Fri, Jun 17, 2016 at 10:49 AM, Matthias Wessendorf <
>>>> matzew at apache.org> wrote:
>>>>
>>>>> cool!
>>>>>
>>>>> On Thu, Jun 16, 2016 at 9:01 PM, Erik Jan de Wit <edewit at redhat.com>
>>>>> wrote:
>>>>>
>>>>>> yeah, let's do that
>>>>>>
>>>>>> On Thu, Jun 16, 2016 at 1:53 PM, Matthias Wessendorf <
>>>>>> matzew at apache.org> wrote:
>>>>>>
>>>>>>> Hi Erik,
>>>>>>>
>>>>>>> now that FCM got merged, can you tag and release the 3.0.0 bits ?
>>>>>>>
>>>>>>> -Matthias
>>>>>>>
>>>>>>> --
>>>>>>> Matthias Wessendorf
>>>>>>>
>>>>>>> blog: http://matthiaswessendorf.wordpress.com/
>>>>>>> twitter: http://twitter.com/mwessendorf
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> aerogear-dev mailing list
>>>>>>> aerogear-dev at lists.jboss.org
>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Cheers,
>>>>>>        Erik Jan
>>>>>>
>>>>>> _______________________________________________
>>>>>> aerogear-dev mailing list
>>>>>> aerogear-dev at lists.jboss.org
>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Matthias Wessendorf
>>>>>
>>>>> blog: http://matthiaswessendorf.wordpress.com/
>>>>> twitter: http://twitter.com/mwessendorf
>>>>>
>>>>> _______________________________________________
>>>>> aerogear-dev mailing list
>>>>> aerogear-dev at lists.jboss.org
>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Cheers,
>>>>        Erik Jan
>>>>
>>>> _______________________________________________
>>>> aerogear-dev mailing list
>>>> aerogear-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>
>>>
>>>
>>>
>>> --
>>> Matthias Wessendorf
>>>
>>> blog: http://matthiaswessendorf.wordpress.com/
>>> twitter: http://twitter.com/mwessendorf
>>>
>>
>>
>>
>> --
>> Matthias Wessendorf
>>
>> blog: http://matthiaswessendorf.wordpress.com/
>> twitter: http://twitter.com/mwessendorf
>>
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> twitter: http://twitter.com/mwessendorf
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



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

From supittma at redhat.com  Fri Jun 24 15:20:22 2016
From: supittma at redhat.com (Summers Pittman)
Date: Fri, 24 Jun 2016 15:20:22 -0400
Subject: [Aerogear-users] Enabled TLS 1.2
In-Reply-To: <1464941053076-707.post@n5.nabble.com>
References: <1464941053076-707.post@n5.nabble.com>
Message-ID: <CAEQz2Cuhp-btUmuzmFXOuo-3o0RxugJHU9VPBfVota3cmndGMQ@mail.gmail.com>

Ramona,

Sorry this slipped past our radars.  No we don't currently do anything to
enable TLS 1.2 in JellyBean or KitKat Android versions.

However, we can work together to modify this class
https://github.com/aerogear/aerogear-android-pipe/blob/master/aerogear-android-pipe/src/main/java/org/jboss/aerogear/android/pipe/http/HttpRestProvider.java
which is the class which configured HTTP for push and release an updated
library.  Alternatively, you can use reflection to inject your own
HttpProvider into the push registrar.  Push uses this field :
https://github.com/aerogear/aerogear-android-push/blob/master/aerogear-android-push/src/main/java/org/jboss/aerogear/android/unifiedpush/fcm/AeroGearFCMPushRegistrar.java#L87
to configure http.

Again, sorry it took so long to reply.  Feel free to follow up with us here
or on the #aerogear IRC channel.

Summers

On Fri, Jun 3, 2016 at 4:04 AM, Ramona.Cristea <Ramona.Cristea at mvise.de>
wrote:

> Hello,
>
> We would like for our push server to support only TLS 1.2 connections for
> security reasons.
> The Android documentation for SSLSocket says that TLS 1.1 and TLS 1.2 is
> supported within android starting API level 16+ (Android 4.1, Jelly Bean).
> But it is by default disabled but starting with API level 20+ (Android 4.4
> for watch, Kitkat Watch and Android 5.0 for phone, Lollipop) they are
> enabled.
>
> We set the minimum sdk version to API 16, but we would like to know if the
> Aero Gear library enables TLS 1.2 protocol when doing a connection?
> If not, then all connections on smartphones with android versions < 5.0
> will
> fail.
>
>
>
> --
> View this message in context:
> http://aerogear-users.1116366.n5.nabble.com/Enabled-TLS-1-2-tp707.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/20160624/44457d7a/attachment.html 

From redprogrammer at gmail.com  Fri Jun 24 22:59:56 2016
From: redprogrammer at gmail.com (redprogrammer)
Date: Fri, 24 Jun 2016 19:59:56 -0700 (MST)
Subject: [Aerogear-users] AeroGear UnifiedPush Server Java Client Send Emoji
Message-ID: <1466823596875-730.post@n5.nabble.com>

Hi,

i am using AeroGear UnifiedPush Server on openshift cartige. ? hava a
problem while using java client. I want to send emojis in push notifications
but i can't send emojis. This error throwed

Jun 24, 2016 7:57:46 PM org.jboss.aerogear.unifiedpush.DefaultPushSender
submitPayload
INFO: HTTP Response code from UnifiedPush Server: 500
Jun 24, 2016 7:57:47 PM org.jboss.aerogear.unifiedpush.DefaultPushSender
submitPayload
SEVERE: The Unified Push Server returned status code: 500
Exception in thread "main"
org.jboss.aerogear.unifiedpush.exception.PushSenderHttpException
	at
org.jboss.aerogear.unifiedpush.DefaultPushSender.submitPayload(DefaultPushSender.java:281)
	at
org.jboss.aerogear.unifiedpush.DefaultPushSender.send(DefaultPushSender.java:230)
	at com.ratemyapp.pushtest.NewClass.main(NewClass.java:44)

Can you help me??
Best Regards



--
View this message in context: http://aerogear-users.1116366.n5.nabble.com/AeroGear-UnifiedPush-Server-Java-Client-Send-Emoji-tp730.html
Sent from the aerogear-users mailing list archive at Nabble.com.


From edewit at redhat.com  Sat Jun 25 02:41:11 2016
From: edewit at redhat.com (Erik Jan de Wit)
Date: Sat, 25 Jun 2016 08:41:11 +0200
Subject: [Aerogear-users] AeroGear UnifiedPush Server Java Client Send
	Emoji
In-Reply-To: <1466823596875-730.post@n5.nabble.com>
References: <1466823596875-730.post@n5.nabble.com>
Message-ID: <CAO2B-fb-L-LObzTm3Z_Yqbn-v2Upk2pxcTd8o-mWNtqQLqcO5g@mail.gmail.com>

How do the logs on the server look like? You can ssh to the machine and see
the logs there as well

On Sat, Jun 25, 2016 at 4:59 AM, redprogrammer <redprogrammer at gmail.com>
wrote:

> Hi,
>
> i am using AeroGear UnifiedPush Server on openshift cartige. ? hava a
> problem while using java client. I want to send emojis in push
> notifications
> but i can't send emojis. This error throwed
>
> Jun 24, 2016 7:57:46 PM org.jboss.aerogear.unifiedpush.DefaultPushSender
> submitPayload
> INFO: HTTP Response code from UnifiedPush Server: 500
> Jun 24, 2016 7:57:47 PM org.jboss.aerogear.unifiedpush.DefaultPushSender
> submitPayload
> SEVERE: The Unified Push Server returned status code: 500
> Exception in thread "main"
> org.jboss.aerogear.unifiedpush.exception.PushSenderHttpException
>         at
>
> org.jboss.aerogear.unifiedpush.DefaultPushSender.submitPayload(DefaultPushSender.java:281)
>         at
>
> org.jboss.aerogear.unifiedpush.DefaultPushSender.send(DefaultPushSender.java:230)
>         at com.ratemyapp.pushtest.NewClass.main(NewClass.java:44)
>
> Can you help me??
> Best Regards
>
>
>
> --
> View this message in context:
> http://aerogear-users.1116366.n5.nabble.com/AeroGear-UnifiedPush-Server-Java-Client-Send-Emoji-tp730.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
>



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