I test a consumable purchase using XCode 12.2.
In my payment transaction observer, I decode the ASN.1 receipt. Field 1704 contains an ia5string which Apple say is the purchase date in RFC 3339 format.
The actual raw receipt time on a recent test was "2020-11-20T10:39:35Z". But that is ridiculous - it is in the FUTURE!
The "Z" implies UTC, but the time of purchase should have been given as "2020-11-19T23:39:35Z" because of my local time being AEST (UTC+1100).
So the generated receipt is using my LOCAL time at purchase, but wrongly stating it as UTC.
Can anyone tell me if this has always been the case for test receipts and if I can expect this bug on real receipts as well?
In my payment transaction observer, I decode the ASN.1 receipt. Field 1704 contains an ia5string which Apple say is the purchase date in RFC 3339 format.
The actual raw receipt time on a recent test was "2020-11-20T10:39:35Z". But that is ridiculous - it is in the FUTURE!
The "Z" implies UTC, but the time of purchase should have been given as "2020-11-19T23:39:35Z" because of my local time being AEST (UTC+1100).
So the generated receipt is using my LOCAL time at purchase, but wrongly stating it as UTC.
Can anyone tell me if this has always been the case for test receipts and if I can expect this bug on real receipts as well?
