APNs server does not respond to some notifications

We’ve received reports that, starting on or around September 19, 2020, APNs servers have stopped responding to some notifications. From Pushy’s perspective, this can look like a Future that never resolves (completion handlers are never called and calls to .get() time out or wait forever). Please see the mailing list thread on this topic for additional background and discussion.

From HTTP/2 frame logs, the problem appears to be that the server simply never sends a HEADERS (or DATA) frame in response to a push notification and never closes the HTTP/2 stream associated with the notification.

At this point, the goal is to identify some specific notifications affected by this problem. If you’ve encountered this issue, we’re hoping to get the UUIDs (apns-id) and approximate timestamps of some affected notifications in the interest of sharing information upstream. Because the problem is that the server isn’t responding, you’ll need to assign your own apns-id values to outbound notifications (SimpleApnsNotification has a pair of constructors that accept an apnsId argument—using UUID.randomUUID() is recommended) to be able to uniquely identify which notifications are having this problem.

This issue is intended to consolidate a number of other reports on this topic, including #807, #814, and #815.

[jchambers]

Yes, I’m still investigating the issue. Thank you for your patience.

[jchambers]

Friends, I understand this is a serious problem for many of you. I promise I’ll share updates as soon as they’re available.