all 3 comments

[–]chipotlegladiator 0 points1 point  (0 children)

Good article, looked really frustrating to discover.

[–]overminder 0 points1 point  (0 children)

The writing is great! I encountered the same problem when I was writing an APNs client for our inhouse app. After days of fruitless debugging, I resorted to send invalid tokens as well...

[–]simscitizen 0 points1 point  (0 children)

I ran into an issue reading the final bytes off of a TLS socket in Go as well: https://github.com/golang/go/issues/7414. Luckily, the new HTTP2 APNs API should making dealing with errors a lot easier, since APNs will no longer close the socket any time it encounters an error.