[aerogear-dev] iOS push error

Thu Jan 29 03:58:19 EST 2015

On Thu, Jan 29, 2015 at 9:49 AM, Sekar, Harini <harini.sekar at rntbci.com>
wrote:

> Sounds good.
>
> Also we tried to deploy the Aero Gear server in Virtual PC which is used
> only inside the our network.
>
> Aero Gear works only in localhost when we try to open it using the IP it
> is not working ?
>
> Do we need any signed SSL certificate to do so ? How to overcome this
> issue ?
>

yes, that is by design. You need to have a SSL cert for the HTTPS, when
deploying on external interfaces

We do have a docker based example for doing that, with a self-signed
certificate:
https://github.com/aerogear/dockerfiles/tree/master/wildfly/unifiedpush-wildfly

Inside of the configuration data, there is some more details:
https://github.com/aerogear/dockerfiles/blob/master/wildfly/configuration/certs/certificate.sh

and the standalone.xml file, to reference the self signed certificate:
https://github.com/aerogear/dockerfiles/blob/master/wildfly/configuration/xml/standalone-sample.xml

> Currently , we have deployed aero gear in OpenShit. Later we have to move
> the same to our Virtual PC ?
>
>
>
> *SSL by default*
>
> By default the option "Require SSL" on Keycloak is enabled to make sure
> that UnifiedPush will run under SSL, except for *localhost* and *Docker* images.
> If you are deploying UPS on non-SSL environment, an exception like "*request
> scheme: http ssl required*" is expected.
>
>
>
>
>
> *From:* aerogear-dev-bounces at lists.jboss.org [mailto:
> aerogear-dev-bounces at lists.jboss.org] *On Behalf Of *Matthias Wessendorf
> *Sent:* 29 January 2015 PM 02:08
>
> *To:* AeroGear Developer Mailing List
> *Subject:* Re: [aerogear-dev] iOS push error
>
>
>
>
>
>
>
> On Thu, Jan 29, 2015 at 9:32 AM, Sekar, Harini <harini.sekar at rntbci.com>
> wrote:
>
> That’s great. When will be the  new update will be released ?
>
>
>
> 1.0.3 will be out in Feb. Here is the jIRA to track fixed and open issues:
>
>
> https://issues.jboss.org/browse/AGPUSH/fixforversion/12325082?selectedTab=com.atlassian.jira.jira-projects-plugin:version-issues-panel
>
>
>
> I want to know why sending push notification dint work in that particular
> time.
>
> Whether it problem with the AeroGear server or IOS certificate ?
>
>
>
> It works now, right ? Not sure what the actual issue was, tbh
>
>
>
>
>
> Yes only 2 IOS devices are there.
>
> When I try to register android in aero gear , in some cases it gets
> registered twice with different device token but they have same alias
> names(device uuid). Is this a bug ?
>
> For your better understanding I have attached the screen shot below
>
>
>
> that happens after uninstall. if you than reintall, it gets a new token
> from Google.
>
> So you have two tokens, but that is really one device. Not a big deal.
>
>
>
> AFTER sending the payload to Google, the response from there gives us
> those tokens that we can remove from the DB. With this being merged soon,
> we also clean up those tokens in the uninstall case:
>
> https://github.com/aerogear/aerogear-unifiedpush-server/pull/474
>
>
>
> So, after the send, now, there should be only one.
>
>
>
>
>
>
>
> NOTE: for iOS we have a similar mechanism to clean up "invalid tokens",
> after a send (invalid means the user removed the iOS app or disabled push
> on the user settings_
>
>
>
> HTH,
>
> Matthias
>
>
>
>
>
>
>
>
>
> *From:* aerogear-dev-bounces at lists.jboss.org [mailto:
> aerogear-dev-bounces at lists.jboss.org] *On Behalf Of *Matthias Wessendorf
> *Sent:* 29 January 2015 PM 01:10
>
>
> *To:* AeroGear Developer Mailing List
> *Subject:* Re: [aerogear-dev] iOS push error
>
>
>
> is that from now ?
>
>
>
> how many devices do you have, for iOS? I guess two ? We had a bug with
> incorrect numbers. That is fixed in the upcoming 1.0.3 release
>
>
>
> On Thu, Jan 29, 2015 at 8:03 AM, Sekar, Harini <harini.sekar at rntbci.com>
> wrote:
>
> It works.
>
> Then why this error occurred while sending notification to IOS devices
>
>
>
> Error:
>
> *Problem occurred during sending push notification(s)*
>
> *Edit Push Network...
> <https://aerogearpush-corpnews.rhcloud.com/ag-push/#/detail/9ca512f4-5dbf-468d-b1f7-22cef66f74cb>*
> ------------------------------
>
> Variants:
>
> IOS APNS
> <https://aerogearpush-corpnews.rhcloud.com/ag-push/#/detail/9ca512f4-5dbf-468d-b1f7-22cef66f74cb>
>
> Failed
>
> *2 installations*
>
> Android
> <https://aerogearpush-corpnews.rhcloud.com/ag-push/#/detail/9ca512f4-5dbf-468d-b1f7-22cef66f74cb>
>
> Succeeded
>
> *4 installations*
>
> IOS APNS
> <https://aerogearpush-corpnews.rhcloud.com/ag-push/#/detail/9ca512f4-5dbf-468d-b1f7-22cef66f74cb>
>
> Failed
>
> *2 installations*
>
>
>
>
>
> *From:* aerogear-dev-bounces at lists.jboss.org [mailto:
> aerogear-dev-bounces at lists.jboss.org] *On Behalf Of *Sébastien Blanc
> *Sent:* 29 January 2015 PM 12:18
> *To:* AeroGear Developer Mailing List
>
> *Subject:* Re: [aerogear-dev] iOS push error
>
>
>
>
>
> Envoyé de mon iPhone
>
>
> Le 29 janv. 2015 à 07:29, Sekar, Harini <harini.sekar at rntbci.com> a
> écrit :
>
> Hi,
>
>
>
> Thank u so much J
>
> If I use Java sender client to send notification , then those activity
> will be listed in the History link in the Aero Gear Admin UI ?
>
>
>
> Yes , in the details you will even see it comes from the Java sender.
>
> Thanks & Regards
>
> Harini S
>
>
>
> *From:* mwessendorf at gmail.com [mailto:mwessendorf at gmail.com
> <mwessendorf at gmail.com>] *On Behalf Of *Matthias Wessendorf
> *Sent:* 29 January 2015 AM 11:37
> *To:* Sekar, Harini
> *Cc:* AeroGear Developer Mailing List
> *Subject:* Re: iOS push error
>
>
>
>
>
>
>
> On Thu, Jan 29, 2015 at 7:03 AM, Sekar, Harini <harini.sekar at rntbci.com>
> wrote:
>
> Yes we are having proxy issue. How to set proxy for this APNS ?
>
>
>
> That's currently not supported on the Unified Push Server, but we track
> the requirement in a ticket:
>
> https://issues.jboss.org/browse/AGPUSH-306
>
>
>
> We didn't have much users requesting this, since usually they delpoy
> the Unified Push Server where they have access to the internet. Otherwise
> the device registration would be hard :-)
>
>
>
> -Matthias
>
>
>
>
>
>
>
> *From:* mwessendorf at gmail.com [mailto:mwessendorf at gmail.com] *On Behalf
> Of *Matthias Wessendorf
> *Sent:* 29 January 2015 AM 11:32
>
>
> *To:* Sekar, Harini
> *Cc:* AeroGear Developer Mailing List
> *Subject:* Re: iOS push error
>
>
>
>
>
>
>
> On Thu, Jan 29, 2015 at 6:00 AM, Sekar, Harini <harini.sekar at rntbci.com>
> wrote:
>
> Hi ,
>
>
>
> When I try to integrate the JAVA Apns I am getting this error “Exception
> in thread "main" *com.notnoop.exceptions.NetworkIOException*:
> *java.net.UnknownHostException*: gateway.push.apple.com”
>
>
>
>
>
> weird, I just tried this code:
>
> https://gist.github.com/matzew/461fb3f6fb26cfc092e7
>
>
>
>
>
> and it works. Wondering, are you behind a firewall or so ?
>
>
>
>
>
>
>
> Thanks & Regards
>
> Harini S
>
>
>
> *From:* aerogear-dev-bounces at lists.jboss.org [mailto:
> aerogear-dev-bounces at lists.jboss.org] *On Behalf Of *Sekar, Harini
> *Sent:* 29 January 2015 AM 10:25
> *To:* Matthias Wessendorf
> *Cc:* AeroGear Developer Mailing List
> *Subject:* Re: [aerogear-dev] iOS push error
>
>
>
> Hi,
>
>
>
> Do you require any ssl trusted certificate for aerogear ?
>
>
>
> Thanks & Regards
>
> Harini S
>
>
>
> *From:* mwessendorf at gmail.com [mailto:mwessendorf at gmail.com
> <mwessendorf at gmail.com>] *On Behalf Of *Matthias Wessendorf
> *Sent:* 28 January 2015 PM 04:51
> *To:* Sekar, Harini
> *Cc:* AeroGear Developer Mailing List
> *Subject:* Re: iOS push error
>
>
>
> You are saying you are not getting push notifications delivered, even
> after a reboot? I think there is something wrong with the certificate's
> .p12 file.
>
>
>
> Do you have it locally ? If so, can you run a standalone test, using this
> Java lib:
>
> https://github.com/notnoop/java-apns
>
>
>
>
>
> 1) get the APNs Servce:
>
> ApnsService service =
>
>     APNS.newService()
>
>     .withCert("/path/to/certificate.p12", "MyCertPassword")
>
>     .withProductionDestination()   // you said you are using production -
> right ? otherwise it's Sandbox....
>
>     .build();
>
>
>
> 2) get a token from the UI, ideally your own device, and send a push:
>
> String payload = APNS.newPayload().alertBody("Test test test").build();
>
> String token = "your token goes here";
>
> service.push(token, payload);
>
>
>
>
>
> That would help to isolate the issue.
>
>
>
>
>
> BTW. what version of the UPS are you running ?
>
>
>
>
>
> On Wed, Jan 28, 2015 at 11:22 AM, Sekar, Harini <harini.sekar at rntbci.com>
> wrote:
>
> Hi Matthias ,
>
>
>
> Have attached the screenshots of the problem I am facing.
>
> It was working till last Thursday (23/01/2015) and I was able to receive
> the notification too, later it started throwing this error.
>
> Kindly help me in sorting out this issue.
>
> <image001.jpg>
>
> <image002.jpg>
>
> <image003.jpg>
>
>
>
> Thanks & Regards,
>
> Harini S
>
>
>
> *From:* mwessendorf at gmail.com [mailto:mwessendorf at gmail.com] *On Behalf
> Of *Matthias Wessendorf
> *Sent:* 28 January 2015 PM 01:21
> *To:* Sekar, Harini
> *Cc:* AeroGear Developer Mailing List
> *Subject:* Re: iOS push error
>
>
>
> Hi Harini,
>
>
>
> >  Yes , but still that warning is there.
>
>
>
> we do not (yet) clean up the warning, after the problem has been solved,
> however we plan to do so (see https://issues.jboss.org/browse/AGPUSH-1248)
>
>
>
> That said - does the push go through? Do you get a notification ? The
> warning itself is has a specific date (click on activity link to go to
> details).
>
>
>
> Here is an older error (on my test instance):
>
>
> https://www.dropbox.com/s/nlrr9kd5dkfuae1/Screen%20Shot%202015-01-28%20at%2008.49.44.png?dl=0
>
>
>
> That error occured only on Jan 6th, but as said above, we do not yet clean
> that up
>
>
>
>
>
> -Matthias
>
>
>
> On Wed, Jan 28, 2015 at 4:23 AM, Sekar, Harini <harini.sekar at rntbci.com>
> wrote:
>
> Hello,
>
>
>
> It was working fine for one day. After that it started throwing the error.
>
> I am using free  version of Openshit in this it doesn’t support custom ssl
> is this may be a problem ?
>
> ·         Did you upload the correct .p12 file for the iOS variant? -  Yes
>
> ·         Or did you replace a development cert with a production cert
> ? – No I am using oly production cert
>
> ·         Did it work a few days ago? – Yes it worked for only one day
>
> ·         Did you try to reboot the instance via the openshift UI ? – Yes
> , but still that warning is there.
>
>
>
> Thanks & Regards
>
> Harini S
>
>
>
> *From:* mwessendorf at gmail.com [mailto:mwessendorf at gmail.com] *On Behalf
> Of *Matthias Wessendorf
> *Sent:* 27 January 2015 PM 06:02
> *To:* AeroGear Developer Mailing List; Sekar, Harini
> *Subject:* iOS push error
>
>
>
> Hi Harini,
>
>
>
> I opened a new thread for this to make it easier to follow up on this
> subject.
>
>
>
> I just tested my Push Server and iOS just worked fine. Here are a few
> questions:
>
>
>
> * Did you upload the correct .p12 file for the iOS variant?
>
> * Or did you replace a development cert with a production cert ?
>
> * Did it work a few days ago?
>
> * Did you try to reboot the instance via the openshift UI ?
>
>
>
> Thanks,
>
> Matthias
>
>
>
>
>
>
>
> On Tue, Jan 27, 2015 at 1:08 PM, Sekar, Harini <harini.sekar at rntbci.com>
> wrote:
>
> Hi guys,
>
> Have deployed the aerogear in openshit and push notification for IOS is
> not working
> Error :
> reason: Error sending payload to APNs server:
> sun.security.validator.ValidatorException: No trusted certificate found
>
> please help me sort this out
>
> Thanks & Regards
> Harini S
>
>
>
> --
>
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>
>
> ***********************************************************************************************************
> CONFIDENTIALITY NOTICE
>
> This message is for the named person's use only.  It may contain
> confidential, proprietary or legally privileged information.
>
> If you receive this message in error, please immediately delete it and all
> copies of it from your system, destroy any hard copies of it and notify us
> by email to email.security at rntbci.com with a copy of this message. You
> must not, directly or indirectly, use, disclose, distribute, print or copy
> any part of this message if you are not the intended recipient. RNTBCI and
> any of its subsidiaries each reserves the right to monitor all e-mail
> communications through its networks.
>
> RNTBCI is neither liable for the proper, complete transmission of the
> information contained in this communication nor any delay in its receipt.
> This email was scanned for the presence of computer viruses. In the
> unfortunate event of infection RNTBCI does not accept any liability.
>
> Any views expressed in this message are those of the individual sender,
> except where the message states otherwise and the sender is authorised to
> state them.
>
> ***********************************************************************************************************
>
>
>
>
>
> --
>
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>
>
> ***********************************************************************************************************
> CONFIDENTIALITY NOTICE
>
> This message is for the named person's use only.  It may contain
> confidential, proprietary or legally privileged information.
>
> If you receive this message in error, please immediately delete it and all
> copies of it from your system, destroy any hard copies of it and notify us
> by email to email.security at rntbci.com with a copy of this message. You
> must not, directly or indirectly, use, disclose, distribute, print or copy
> any part of this message if you are not the intended recipient. RNTBCI and
> any of its subsidiaries each reserves the right to monitor all e-mail
> communications through its networks.
>
> RNTBCI is neither liable for the proper, complete transmission of the
> information contained in this communication nor any delay in its receipt.
> This email was scanned for the presence of computer viruses. In the
> unfortunate event of infection RNTBCI does not accept any liability.
>
> Any views expressed in this message are those of the individual sender,
> except where the message states otherwise and the sender is authorised to
> state them.
>
> ***********************************************************************************************************
>
>
>
>
>
> --
>
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>
>
> ***********************************************************************************************************
> CONFIDENTIALITY NOTICE
>
> This message is for the named person's use only.  It may contain
> confidential, proprietary or legally privileged information.
>
> If you receive this message in error, please immediately delete it and all
> copies of it from your system, destroy any hard copies of it and notify us
> by email to email.security at rntbci.com with a copy of this message. You
> must not, directly or indirectly, use, disclose, distribute, print or copy
> any part of this message if you are not the intended recipient. RNTBCI and
> any of its subsidiaries each reserves the right to monitor all e-mail
> communications through its networks.
>
> RNTBCI is neither liable for the proper, complete transmission of the
> information contained in this communication nor any delay in its receipt.
> This email was scanned for the presence of computer viruses. In the
> unfortunate event of infection RNTBCI does not accept any liability.
>
> Any views expressed in this message are those of the individual sender,
> except where the message states otherwise and the sender is authorised to
> state them.
>
> ***********************************************************************************************************
>
>
> ***********************************************************************************************************
> CONFIDENTIALITY NOTICE
>
> This message is for the named person's use only.  It may contain
> confidential, proprietary or legally privileged information.
>
> If you receive this message in error, please immediately delete it and all
> copies of it from your system, destroy any hard copies of it and notify us
> by email to email.security at rntbci.com with a copy of this message. You
> must not, directly or indirectly, use, disclose, distribute, print or copy
> any part of this message if you are not the intended recipient. RNTBCI and
> any of its subsidiaries each reserves the right to monitor all e-mail
> communications through its networks.
>
> RNTBCI is neither liable for the proper, complete transmission of the
> information contained in this communication nor any delay in its receipt.
> This email was scanned for the presence of computer viruses. In the
> unfortunate event of infection RNTBCI does not accept any liability.
>
> Any views expressed in this message are those of the individual sender,
> except where the message states otherwise and the sender is authorised to
> state them.
>
> ***********************************************************************************************************
>
>
>
>
>
> --
>
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>
>
> ***********************************************************************************************************
> CONFIDENTIALITY NOTICE
>
> This message is for the named person's use only.  It may contain
> confidential, proprietary or legally privileged information.
>
> If you receive this message in error, please immediately delete it and all
> copies of it from your system, destroy any hard copies of it and notify us
> by email to email.security at rntbci.com with a copy of this message. You
> must not, directly or indirectly, use, disclose, distribute, print or copy
> any part of this message if you are not the intended recipient. RNTBCI and
> any of its subsidiaries each reserves the right to monitor all e-mail
> communications through its networks.
>
> RNTBCI is neither liable for the proper, complete transmission of the
> information contained in this communication nor any delay in its receipt.
> This email was scanned for the presence of computer viruses. In the
> unfortunate event of infection RNTBCI does not accept any liability.
>
> Any views expressed in this message are those of the individual sender,
> except where the message states otherwise and the sender is authorised to
> state them.
>
> ***********************************************************************************************************
>
>
>
>
>
> --
>
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>
>
> ***********************************************************************************************************
> CONFIDENTIALITY NOTICE
>
> This message is for the named person's use only.  It may contain
> confidential, proprietary or legally privileged information.
>
> If you receive this message in error, please immediately delete it and all
> copies of it from your system, destroy any hard copies of it and notify us
> by email to email.security at rntbci.com with a copy of this message. You
> must not, directly or indirectly, use, disclose, distribute, print or copy
> any part of this message if you are not the intended recipient. RNTBCI and
> any of its subsidiaries each reserves the right to monitor all e-mail
> communications through its networks.
>
> RNTBCI is neither liable for the proper, complete transmission of the
> information contained in this communication nor any delay in its receipt.
> This email was scanned for the presence of computer viruses. In the
> unfortunate event of infection RNTBCI does not accept any liability.
>
> Any views expressed in this message are those of the individual sender,
> except where the message states otherwise and the sender is authorised to
> state them.
>
> ***********************************************************************************************************
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
> ***********************************************************************************************************
> CONFIDENTIALITY NOTICE
>
> This message is for the named person's use only.  It may contain
> confidential, proprietary or legally privileged information.
>
> If you receive this message in error, please immediately delete it and all
> copies of it from your system, destroy any hard copies of it and notify us
> by email to email.security at rntbci.com with a copy of this message. You
> must not, directly or indirectly, use, disclose, distribute, print or copy
> any part of this message if you are not the intended recipient. RNTBCI and
> any of its subsidiaries each reserves the right to monitor all e-mail
> communications through its networks.
>
> RNTBCI is neither liable for the proper, complete transmission of the
> information contained in this communication nor any delay in its receipt.
> This email was scanned for the presence of computer viruses. In the
> unfortunate event of infection RNTBCI does not accept any liability.
>
> Any views expressed in this message are those of the individual sender,
> except where the message states otherwise and the sender is authorised to
> state them.
>
> ***********************************************************************************************************
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
>
>
>
> --
>
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>
>
> ***********************************************************************************************************
> CONFIDENTIALITY NOTICE
>
> This message is for the named person's use only.  It may contain
> confidential, proprietary or legally privileged information.
>
> If you receive this message in error, please immediately delete it and all
> copies of it from your system, destroy any hard copies of it and notify us
> by email to email.security at rntbci.com with a copy of this message. You
> must not, directly or indirectly, use, disclose, distribute, print or copy
> any part of this message if you are not the intended recipient. RNTBCI and
> any of its subsidiaries each reserves the right to monitor all e-mail
> communications through its networks.
>
> RNTBCI is neither liable for the proper, complete transmission of the
> information contained in this communication nor any delay in its receipt.
> This email was scanned for the presence of computer viruses. In the
> unfortunate event of infection RNTBCI does not accept any liability.
>
> Any views expressed in this message are those of the individual sender,
> except where the message states otherwise and the sender is authorised to
> state them.
>
> ***********************************************************************************************************
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
>
>
>
> --
>
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>
>
> ***********************************************************************************************************
> CONFIDENTIALITY NOTICE
>
> This message is for the named person's use only.  It may contain
> confidential, proprietary or legally privileged information.
>
> If you receive this message in error, please immediately delete it and all
> copies of it from your system, destroy any hard copies of it and notify us
> by email to email.security at rntbci.com with a copy of this message. You
> must not, directly or indirectly, use, disclose, distribute, print or copy
> any part of this message if you are not the intended recipient. RNTBCI and
> any of its subsidiaries each reserves the right to monitor all e-mail
> communications through its networks.
>
> RNTBCI is neither liable for the proper, complete transmission of the
> information contained in this communication nor any delay in its receipt.
> This email was scanned for the presence of computer viruses. In the
> unfortunate event of infection RNTBCI does not accept any liability.
>
> Any views expressed in this message are those of the individual sender,
> except where the message states otherwise and the sender is authorised to
> state them.
>
> ***********************************************************************************************************
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>

-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150129/24f9f1e7/attachment-0001.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 25534 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150129/24f9f1e7/attachment-0001.png 