At the very least it’s a documentation bug - the description also says it’s in milliseconds since the epoch as well as RFC 3339. Seems like a copy and paste error somewhere.
Have you seen the other receipts with expires_date, or was it actually expiration_date?
These posts show a receipt with an expires_date field in this format:
"expires_date":"2016-12-31 17:05:24 Etc/GMT",
I'm lookiing for guidance on how to parse this field. Try as milliseconds and if that fails, try as this format, and if that fails try RFC 3339? I don't want to find out when I deploy the live app that the date is coming back in a format I was unable to test.
So, no advice on this?
The documentation is incorrect, and as noted on the documentation pages, is no longer being updated. Is there a newer endpoint we can use or some other way of verifying receipts?