Does APNS support no longer exist according to new APIs?

Question

I went through the updated official APNS documentation and she clearly says

All developers should migrate their remote notification provider servers to the more efficient and efficient HTTP / 2-based APIs described in the APNs API.

But the new APNs API does not seem to have the old APNS feedback service. They changed the URLs of endpoints that do not have a feedback service endpoint. It also looks like error codes are being updated now, which includes the error code below,

Unregistered - The device token is inactive for the specified topic.

So, can we call the APNS feedback service again?

My main problem is that I am using javapns api version 2.2 for iOS push notifications, for which I cannot find any update that will help me deal with these new changes.

Answer 1

I think the new document is clear:

Here is the HTTP status code for the case previously reported by the feedback service:

410 - the device token is no longer active for the topic.

In addition, the response body has a JSON data key called timestamp :

time stamp

If the value in the status header is 410, the value of this key is the last when the APNs confirmed that the device token is no longer valid for the topic.

Stop turning off notifications until the device registers a token with a later timestamp with your provider.

Consequently, the HTTP response in the new API covers functionality that was previously covered by the feedback service. Since the recall service is not mentioned in the new document, we can safely assume that it is not part of the new API.

If you are using an old library like javapns that still uses the old API, I assume that it still uses the feedback service. The old API will probably still be supported by Apple for a while.