[aerogear-dev] iOS push error

Matthias Wessendorf matzew at apache.org
Thu Jan 29 01:05:15 EST 2015


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

> Hi,
>
>
>
> IOS push notification is working but still the error message is displaying
>
> *Error sending payload to APNs server:
> sun.security.validator.ValidatorException: No trusted certificate found*
>

AH!!!! yeah, that's what I tried to explain earlier: We are not yet
cleaning up the messages, when you _had_ issues in the past.
the history keeps track of it. That's why I asked to send again. The error
should be associated w/ a date.

In my screenshot from yesterday, I had an error from January 6 (almost
three weeks away). But currently works. After 30 days, we drop the history.
So, until than, all pushes (successful or not) are listed. And yes,
unfortunately the warning goes not yet away.

Here is the link to the JIRA to clean up the info
https://issues.jboss.org/browse/AGPUSH-1248

Hope that helps


>
> Thanks & Regards
>
> Harini S
>
>
>
> *From:* mwessendorf at gmail.com [mailto:mwessendorf at gmail.com] *On Behalf
> Of *Matthias Wessendorf
> *Sent:* 29 January 2015 AM 11:22
>
> *To:* Sekar, Harini
> *Cc:* AeroGear Developer Mailing List
> *Subject:* Re: iOS push error
>
>
>
> No, just a certificate, like described here:
>
> https://aerogear.org/docs/unifiedpush/aerogear-push-ios/
>
>
>
> 1. Apple App ID and SSL Certificate for APNs
>
>
>
> On Thu, Jan 29, 2015 at 5:55 AM, Sekar, Harini <harini.sekar at rntbci.com>
> wrote:
>
> Hi,
>
>
>
> Do you require any ssl trusted certificate for aerogear ?
>
>
>
> Thanks & Regards
>
> Harini S
>
>
>
> *From:* mwessendorf at gmail.com [mailto: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.
>
>
>
> 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.
>
> ***********************************************************************************************************
>
>
>
>
>
> --
>
> 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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150129/cc6d6b2d/attachment-0001.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 32978 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150129/cc6d6b2d/attachment-0003.jpg 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.jpg
Type: image/jpeg
Size: 11323 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150129/cc6d6b2d/attachment-0004.jpg 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.jpg
Type: image/jpeg
Size: 10022 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150129/cc6d6b2d/attachment-0005.jpg 


More information about the aerogear-dev mailing list