google-play-billing-validator icon indicating copy to clipboard operation
google-play-billing-validator copied to clipboard

Error while acknowledging purchase

Open sushinpv opened this issue 4 years ago • 5 comments

I'm getting this error while acknowledging the purchase, but this issue is only there for purchase not with the subscription,

Please help me to solve this issue, till last month it was working,

{
  isSuccessful: false,
  errorCode: 400,
  errorMessage: 'Invalid response, please check ' +
    "'Verifier' configuration or the " +
    'statusCode above'
}

Sample code

        let receipt = {
            packageName: packageName,
            productId: productId,
            purchaseToken: purchaseToken,
            developerPayload: 'Acknowledged Purchase Successfully'
        };
        console.log(receipt);

        verifier.verifySub(receipt).then(result => {
            console.log(result);
        }).catch(err => {
            console.log(err);
            reject('err')
        });

sushinpv avatar Jun 28 '20 06:06 sushinpv

I think you need to first validate the purchase (don't include developerPayload) and check if acknowledgementState is already set to 1, before trying to acknowledge again.

Meekohi avatar May 13 '21 19:05 Meekohi

I am seeing the same thing during testing. When validating a purchase i see acknowledgementState=0 but when i try to acknowledge i get the same error.

jaredgibb avatar Mar 23 '22 18:03 jaredgibb

did anyone solve it? { "error": { "code": 400, "message": "Invalid Value", "errors": [ { "message": "Invalid Value", "domain": "global", "reason": "invalid" } ] } }

same issue I am dealing with.

hasnainelahi avatar Jun 21 '22 07:06 hasnainelahi

@Deishelon any update here

{
  isSuccessful: false,
  errorCode: 400,
  errorMessage: "Invalid response, please check 'Verifier' configuration or the statusCode above"
}

sandesh-bhoir avatar Oct 19 '23 11:10 sandesh-bhoir

did anyone solve it? { "error": { "code": 400, "message": "Invalid Value", "errors": [ { "message": "Invalid Value", "domain": "global", "reason": "invalid" } ] } }

same issue I am dealing with.

were you able to rectify it? I'm stuck at same point.

sandesh-bhoir avatar Oct 20 '23 06:10 sandesh-bhoir