Hello,
i’m currently trying to have an in-app working on android / google play.
as far as i understand: the current version of the store api only supports the google version 2 api.
in their doc: Managed per user account is available in v2 api. but when i create a new managed product, it seems to be created by default
with the api version 3, and i’m unable to find a way to set it as v2.
also the log message shows: Unsupported (future) billing API version: 2 .
any idea ?
thanks in advance .
@tech271, I don’t think you need to worry about setting the managed product to work with v2. Just create products and work out the code for In-App Billing, and it should work. (It did for me.)
Naomi
that’s what i thought too, but when calling store.purchase ({“myproductidentifier”}) nothing happens and i only see that message in the device log: Unsupported (future) billing API version: 2
That’s odd. Mine works when calling store.purchase({“myproductidentifier”}) without any issue, and I’ve never seen “unsupported” error message.
I don’t know what could be wrong with yours. Do you have your in-app item in “active” status? Other than that, I have no more idea to suggest. (And yes, yesterday, I purchased in-app items while playing my latest app yet-to-be-released to GooglePlay, so I know it’s working.)
BTW, I’m still using daily build 1054. I don’t know if anything changed with the Corona since then, but what build are you using?
Naomi
yes the items are active, and i’m using the latest build 1076.
connections seems to work (for exemple the licensing call works and returns ok)
maybe your items were created weeks ago, mine just 4 days ago and they changed something on google side, new apps and in-app are all configured v3 ?.
I created mine about a month ago. I actually thought I needed to sort out v3:
http://forums.coronalabs.com/topic/32764-resolved-google-play-in-app-billing/
But it turned out I didn’t need to. I use new interface at GooglePlay Developer Console. I don’t think things changed since.
Naomi
thanks for all Naomi, indeed it works as it should…
the problem was coming from a misconfigured email in the allowed test accounts, and the error message about api version which was quite confusing . now when hitting a buy button, the store opens correctly.
Glad to hear it’s working for you now, @tech271. I had an issue with test user account too. It’s so easy to make a typo or use non-test user account to try testing the In-App Billing. That said, I don’t remember seeing the error message with API version (or maybe I just didn’t read the error message at all when I was having trouble with it.)
Naomi
@tech271, I don’t think you need to worry about setting the managed product to work with v2. Just create products and work out the code for In-App Billing, and it should work. (It did for me.)
Naomi
that’s what i thought too, but when calling store.purchase ({“myproductidentifier”}) nothing happens and i only see that message in the device log: Unsupported (future) billing API version: 2
That’s odd. Mine works when calling store.purchase({“myproductidentifier”}) without any issue, and I’ve never seen “unsupported” error message.
I don’t know what could be wrong with yours. Do you have your in-app item in “active” status? Other than that, I have no more idea to suggest. (And yes, yesterday, I purchased in-app items while playing my latest app yet-to-be-released to GooglePlay, so I know it’s working.)
BTW, I’m still using daily build 1054. I don’t know if anything changed with the Corona since then, but what build are you using?
Naomi
yes the items are active, and i’m using the latest build 1076.
connections seems to work (for exemple the licensing call works and returns ok)
maybe your items were created weeks ago, mine just 4 days ago and they changed something on google side, new apps and in-app are all configured v3 ?.
I created mine about a month ago. I actually thought I needed to sort out v3:
http://forums.coronalabs.com/topic/32764-resolved-google-play-in-app-billing/
But it turned out I didn’t need to. I use new interface at GooglePlay Developer Console. I don’t think things changed since.
Naomi
thanks for all Naomi, indeed it works as it should…
the problem was coming from a misconfigured email in the allowed test accounts, and the error message about api version which was quite confusing . now when hitting a buy button, the store opens correctly.
Glad to hear it’s working for you now, @tech271. I had an issue with test user account too. It’s so easy to make a typo or use non-test user account to try testing the In-App Billing. That said, I don’t remember seeing the error message with API version (or maybe I just didn’t read the error message at all when I was having trouble with it.)
Naomi