Recent change in APNs “Unregistered” response behaviour?

[Justin Mason]

Hey all —

Just wondering if anyone has noticed a recent change in how APNs over
HTTP/2 handles uninstalled apps? Since about the 26th of Jan, we’ve
noticed a dramatic drop in the count of 410 “Unregistered” responses,
across the board.

We are using HTTP/2 with provider certificates against the APNs
production server.
The same behaviour is visible across several certificates...

—j.

[j...@turo.com]

Huh. And here I was just thinking that people started really liking our app a lot more ;)

Yes, we've observed the same behavior. Unfortunately, we've also observed an increase in HTTP/500 ("InternalServerError") responses, and I wonder if the latter might be masking the former. I've already filed a bug report with Apple, but have received no reply. Have you seen the same?

-Jon

[Justin Mason]

I can’t find any sign of increased 500 responses — and hopefully I’m
not dropping those ;)
I’ve opened a bug report with Apple, too, but no word yet.

> --
> Pushy is an open-source Java library for sending APNs (iOS and OS X) push
> notifications. Pushy is brought to you by the engineers at RelayRides.
> ---
> You received this message because you are subscribed to the Google Groups
> "pushy" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to pushy-apns+...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

[Jon Chambers]

> hopefully I’m not dropping those ;)

Reading various bits of forum traffic and bug reports in provider libraries, it sounds like the 500 responses are mostly happening for people using token authentication. It's possible that the same problem is affecting both authentication schemes, but only being reported in one. Seems like a bit of a stretch, though.

-Jon

[Justin Mason]

Following up on this -- Apple responded to my support request _extremely_ unhelpfully, stating 'I’d just call it a statistical quirk. This is the first time I’ve ever heard of a developer tracking this as a metric.' -- so no help there. :(

I opened a follow-up Radar a couple of weeks ago, but there's been no response yet.

--j.

On Thursday, 2 February 2017 19:03:18 UTC, Jon Chambers wrote:

> hopefully I’m not dropping those ;)

[j...@turo.com]

Bummer. I've also received no reply to my radar reporting elevated rates of HTTP/500 responses.

-Jon

[j...@turo.com]

I did just receive a reply from Apple about the elevate rate of HTTP/500 responses. They write:

Are you still seeing the issue mentioned in the description? If you do, would you please provide some more details with a reproduction?

 

1. Bundle ID.
2. Time frame + time zone of the reproduction.
3. The IP address of your service will be helpful.
4. Detail information about pushes (token, message ID, timestamp) around the reproduction time frame is also helpful.

I don't think anybody affected is reading this thread, but just in case, please email me directly at j...@turo.com if you're still experiencing the issue.

Thanks!

-Jon