Hello!We just discovered an issue where we were using the wrong units for timestamps when communicating with APNs servers. To jump right to the point, it appears that the `timestamp` field in the response from the APNs server is actually expressed in milliseconds. We had assumed that it was in seconds because:The `apns-expiration` header (the only other timestamp used in the APNs protocol) is called out as using seconds.The equivalent field in the old feedback service was given in seconds.There is no unit called out for the `timestamp` field in the current docs.I've filed a bug report suggesting that the docs explicitly call out the unit of time for the `timestamp` field, but wanted to mention it here in case somebody else runs into the same problem.Cheers!-Jon

Units for timestamps in HTTP/2-bas… | Apple Developer Forums

Units for timestamps in HTTP/2-based protocol

Hello!

We just discovered an issue where we were using the wrong units for timestamps when communicating with APNs servers. To jump right to the point, it appears that the `timestamp` field in the response from the APNs server is actually expressed in milliseconds. We had assumed that it was in seconds because:

The `apns-expiration` header (the only other timestamp used in the APNs protocol) is called out as using seconds.
The equivalent field in the old feedback service was given in seconds.
There is no unit called out for the `timestamp` field in the current docs.

I've filed a bug report suggesting that the docs explicitly call out the unit of time for the `timestamp` field, but wanted to mention it here in case somebody else runs into the same problem.

Cheers!

-Jon