It's possible that when connecting to (legacy) APNs, we may get an exception like:
javax.net.ssl.SSLHandshakeException: Remote host closed connection during handshake
|
at com.notnoop.apns.internal.Utilities.wrapAndThrowAsRuntimeException(Utilities.java:284)
|
at com.notnoop.apns.internal.ApnsConnectionImpl.sendMessage(ApnsConnectionImpl.java:342)
|
at com.notnoop.apns.internal.ApnsConnectionImpl.sendMessage(ApnsConnectionImpl.java:312)
|
at com.notnoop.apns.internal.ApnsServiceImpl.push(ApnsServiceImpl.java:46)
|
at com.notnoop.apns.internal.AbstractApnsService.push(AbstractApnsService.java:56)
|
at com.notnoop.apns.internal.ApnsServiceImpl.push(ApnsServiceImpl.java:36)
|
at com.notnoop.apns.internal.AbstractApnsService.push(AbstractApnsService.java:45)
|
|
We should cover this in the trobule shooting guide, to tell users to renew their .p12 files, like described here: https://github.com/notnoop/java-apns/issues/254#issuecomment-143190961
|