Possible values of transaction.errorType and transaction.errorString

Could Corona staff please add a full list of possible values for transaction.errorType and transaction.errorString to the purchase documentation? (For both iPhone and Android).

I’m asking because, in order to learn these values as a developer, you’d have to submit and release production versions that contain logging, since that’s the only time when purchases really work and would produce actual values.

Thanks!

First, I’m not sure know the possible values because they are frequently generated by the service and we just pass the data back to you.  Apple or Google should have documented what their possible return values are and it’s subject to change.  If we put that information in our documentation, it will likely be out of date very quickly.

I feel your pain.  IAP testing is not a fun experience.

First, I’m not sure know the possible values because they are frequently generated by the service and we just pass the data back to you.  Apple or Google should have documented what their possible return values are and it’s subject to change.  If we put that information in our documentation, it will likely be out of date very quickly.

I feel your pain.  IAP testing is not a fun experience.

@Rob: I have done some logging of purchase errors, and it’s actually not that many variations. (You could add this information to the store documentation so people know what to expect.)

Below are errors from Play Store:

[Lua]

{“state”:“cancelled”,“type”:“none”,“string”:""}

{“state”:“failed”,“type”:“none”,“string”:""}

{“state”:“failed”,“type”:“invalidClient”,“string”:""}

[/Lua]

And App Store reports the following (the string parameter is localized):

[Lua]

{“state”:“cancelled”,“type”:“cancelled”,“string”:“Cannot connect to iTunes Store”}

{“state”:“failed”,“type”:“unknown”,“string”:“Cannot connect to iTunes Store”}

[/Lua]

Questions:

  1. Under what circumstances does “invalidClient” occur?

  2. Doesn’t Play Store generate any verbal error message, or is it a fault on Corona’s part that the error message doesn’t appear in the event object?

@Rob: I have done some logging of purchase errors, and it’s actually not that many variations. (You could add this information to the store documentation so people know what to expect.)

Below are errors from Play Store:

[Lua]

{“state”:“cancelled”,“type”:“none”,“string”:""}

{“state”:“failed”,“type”:“none”,“string”:""}

{“state”:“failed”,“type”:“invalidClient”,“string”:""}

[/Lua]

And App Store reports the following (the string parameter is localized):

[Lua]

{“state”:“cancelled”,“type”:“cancelled”,“string”:“Cannot connect to iTunes Store”}

{“state”:“failed”,“type”:“unknown”,“string”:“Cannot connect to iTunes Store”}

[/Lua]

Questions:

  1. Under what circumstances does “invalidClient” occur?

  2. Doesn’t Play Store generate any verbal error message, or is it a fault on Corona’s part that the error message doesn’t appear in the event object?

I have the same issue testing at the moment, getting an “invalidClient” message - would like to know what the Google Error code was (to then look up Google doco) that Corona received and gave an invalidClient… I say that because I can’t see use of the term “invalidClient” in their error codes.  I assume it’s the V3 API that is being used?  http://developer.android.com/google/play/billing/billing_reference.html

The worst thing is that the in app billing worked from the Android popup, it’s just that when it throws back to my app I get the failed.  I note it turns up as a sale in Google Merchant Center which may be real $$.  

EDIT:  I’ve just seen some other posts with a list of things to check re “invalidClient”.  I’ll go through these first.  For one thing it has only been an hour or two since I uploaded.   

See: http://forums.coronalabs.com/topic/37442-google-play-iap-ridiculous-success-rate/

Thanks

Rob

I have the same issue testing at the moment, getting an “invalidClient” message - would like to know what the Google Error code was (to then look up Google doco) that Corona received and gave an invalidClient… I say that because I can’t see use of the term “invalidClient” in their error codes.  I assume it’s the V3 API that is being used?  http://developer.android.com/google/play/billing/billing_reference.html

The worst thing is that the in app billing worked from the Android popup, it’s just that when it throws back to my app I get the failed.  I note it turns up as a sale in Google Merchant Center which may be real $$.  

EDIT:  I’ve just seen some other posts with a list of things to check re “invalidClient”.  I’ll go through these first.  For one thing it has only been an hour or two since I uploaded.   

See: http://forums.coronalabs.com/topic/37442-google-play-iap-ridiculous-success-rate/

Thanks

Rob