a2: Connection errors

I’m having connection errors when trying to connect to APNS:

TRACE 2018-04-03T08:46:05Z: apns2::signer: Signer::with_signature found signature for """""" APNS valid for 2700s
TRACE 2018-04-03T08:46:05Z: apns2::alpn: AlpnConnector::call ("https://api.push.apple.com/3/device/******")
TRACE 2018-04-03T08:46:05Z: apns2::client: Client::call requesting ("https://api.push.apple.com/3/device/******")
TRACE 2018-04-03T08:46:06Z: apns2::alpn: AlpnConnector::call got TCP, trying TLS
TRACE 2018-04-03T08:46:06Z: apns2::client: Request error: an operation was canceled internally before starting
 WARN 2018-04-03T08:46:06Z: push_relay::server: Error: Push message could not be processed: Push was unsuccessful: Error connecting to APNs

Any idea what the reason for this could be?

About this issue

Original URL
State: closed
Created 6 years ago
Comments: 23 (23 by maintainers)

Commits related to this issue

Add CLI argparser (#6) — committed to eklipse2k8/rust-apns by deleted user 2 years ago

Most upvoted comments

You see the returned future not evaluated here, only after you explicitly send it to a reactor core. To not have a client at this point should not be possible at all.

It’s possible because the future does not contain a reference to the client itself, but a receiving end of a channel or stream or something like that. The sender of such a type can be dropped even if the receiving end is still alive. I think this is because futures require a static lifetime, if I’m not mistaken?

Maybe @carllerche or @seanmonstar know more about this? (Relevant comments: https://github.com/pimeys/apns2/issues/6#issuecomment-378287736 and later)

dbrgn on Apr 3, 2018