Closed GoogleCodeExporter closed 8 years ago
That is the only exception printed? Are you certain that your keystore has
been generated according to the documentation (see GetAPNSCertificate in wiki)
for the SANDBOX server, and that your "certificate" property points to your
keystore file? Are you also sure that your keystore password is correct?
If you're sure your keystore and password are valid, more details would be
required to understand what is going on during handshake. Could you enable SSL
debugging (see SSL Certificate issues in the Tips wiki page) and provide the
full printout? Thanks!
Original comment by sype...@gmail.com
on 21 Sep 2011 at 11:28
I think that I had problems with the certificate...
Maybe it got corrupted while I changed it from Mac to PC, because I am
programming on PC.
Now I think it works, because I did not get a Notification on the phone.
Will the Beta become a final soon ?
My company does not want to use any Beta versions, although I am making test
with this one.
Thank you very much for replying that fast.
Original comment by Christia...@gmail.com
on 21 Sep 2011 at 11:38
By the way, I have tried using the proper certificate with a wrong phone ID to
check how the server behaved, but I have not received any response from the
APNs server.
I think that is due to using normal notifications instead of enhanced
notifications.
Will enhanced notifications solve the problem?
Where can I find the JavaDoc of the Javapns Beta so I can activate enhanced
notifications ?
Thank you very much and have a nice day.
Original comment by Christia...@gmail.com
on 21 Sep 2011 at 1:02
As per your comment #2, I'm closing the issue as Invalid since it was a local
certificate issue and not a library bug.
Regarding your question about the beta phase, it all depends on the feedback we
receive from users. If new issues are discovered, the beta phase will continue
a bit longer. If only positive feedback is received, we can move forward
toward a final version. Since Beta 4 is very recent, not much feedback has
been received so far.
As for your other question about invalid tokens, the enhanced notification
format will help detect malformed push messages, payloads, token format, etc.
I'm not sure if the token is actually checked if it matches a known device, or
if instead an invalid token will simply show up in the Feedback Service after a
few failed attempts at pushing to that invalid token. I would think that the
second option is the one used by Apple. I can't find any clear explanation of
this in Apple's documentation, beside the simple list of error codes.
At this time though, enhanced notifications are not fully supported... see
issue #47 for more details.
Finally, the javadoc is in SVN: svn/ branches/ javapns2/
javapns_2.0_Beta_4_javadoc.jar
Original comment by sype...@gmail.com
on 21 Sep 2011 at 10:38
Original issue reported on code.google.com by
Christia...@gmail.com
on 21 Sep 2011 at 10:35