"Internal Server Error" when using old token to create Android order.

[hannahtinkler]

From: https://code.a8c.com/D94727

When I submit a new order request with an invalid purchase_token, I get back a response that looks like this:

{
"code": "no_response_body",
"message": "Server could not read response.",
"data": "{"headers":{},"body":"","response":{"code":500,"message":"Internal Server Error"},"cookies":[],"filename":null,"http_response":{"data":null,"headers":null,"status":null}}",
"additional_data": [
500
]
}
So somehow it's not getting the android_receipt_invalid error...

I have tried to recreate but get:

{
    "code": "android_receipt_invalid",
    "message": "The receipt provided is invalid",
    "data": 400
}

CC @coreymckrill - I don't think this was a direct result of the receipt being invalid, it looks like something else happened along the way that caused this (though probably linked to the receipt being invalid) - what errors were logged when this happened?

[coreymckrill]

@hannahtinkler I just managed to get this error again, and I should have been more specific the first time: the no_response_body happens when I submit a request that has purchase_token parameter that is either empty or contains an arbitrary string that is not an actual purchase token. If I use the purchase token I got yesterday (which is now expired), I also get android_receipt_invalid.

Here's the error I'm getting on the server side:

[15-Dec-2022 21:52:13 UTC] Fatal error: Uncaught Google\Service\Exception: {
  "error": {
    "code": 400,
    "message": "Invalid Value",
    "errors": [
      {
        "message": "Invalid Value",
        "domain": "global",
        "reason": "invalid"
      }
    ]
  }
}

I'll send you the full stack trace in a DM so we don't have a path disclosure, since this is a public repo.

[hannahtinkler]

Thanks @coreymckrill! I've tagged you on a new changeset to resolve this 🙂