We’ve noticed that some renewal transactions returned by the validate-transaction endpoint have a purchase_date in the future that is equal to the expiration_date.
Is there any known ongoing issue that could be causing this?
Can you DM me some sample transaction IDs? We had our team take a look bu they didn’t find anything so far
Nicole, I couldn’t find how to send DMs in the forum, so I have send you some sample transaction ids through Slack.
This issue started appearing on September 9. On the same day, we also noticed another issue:
We started receiving notifications from Roku for transaction IDs that were later not recognized by the validate-transaction endpoint. Specifically, we would receive a notification for a transaction, but when we later called https://apipub.roku.com/listen/transaction-service.svc/validate-transaction/``<...>/<...> for the same transaction id, we received errorMessage = "UNAUTHORIZED".
I’ve also sent some examples of this issue through Slack.
Would there be any legitimate reasons for a purchase date to be in the future?
@RokuNicole I’ve been seeing the same issue - purchase_date in the future and equal to the expiration_date. Has Roku identified the cause of this issue yet? I do have sample transaction ids I can send you privately.
Kindly bumping this one. Do we have any updates?
