I am currently testing a new game.
I'm using GS 1.25.101.
Apple's iap works, but Google iap doesn't work.
Is there anything that needs to be reset as it changes to Use Google Billing Client 3.0?
Hey @Acroxia , same situation here... did you manage to get Google IAP to work?
This could be a lot of things. First I'd check is - did you add the IAP key in the GameSalad publishing portal? There's no equivalent step for Apple, so it's easy to miss.
Contact me for custom work - Expert GS developer with 12 years of GS experience - Skype: armelline.support
@Armelline Yes, I did. And also checked the box for Google IAP. On Google Play Console, I created the in-app product (matching the ID I used in my game) and activated it. And yet I get no response from the IAP button in my game
Did you use all lowercase letters for your product ID, and have you definitely signed all the relevant contracts and provided your banking details? (Been a while since I did those steps on Google so not sure if they're needed but they are on iOS.)
@Armelline Lowercase: yes. Banking details: no, I haven't added a payment method yet...maybe that’s the problem?
You mentioned "signing all relevant contracts"...on Apple, there is a paid app agreement that clearly states that you need to sign it for the IAP to work. However, I didn't find anything similar on Google that I could have missed
@Baguvix iap is still not working.
@Armelline Yes. I did. Some games have been released, so you can't set the same settings.
also. admob doesn't work in iphone. (work in android)
android : work admob / doesn't work In-app
Apple : work In-app / doesn;t work admob. (request 22 but not show ad)
@Acroxia I'm sorry to hear that... I thought maybe you've figured it out.
When I uploaded my apk I received a warning saying that my app is using an old version of Google Play Billing. I'm not sure if it is related to the issue.
Are you publishing using the "Build RC" button?
Heey @Armelline , a little update here, I did some debugging and apparently the purchase table is never being filled with the data (callback is always -1 when the behavior is run). Any insights? Thanks
Yes (leaderboards works, by the way)
Yes. callback is always -1 when the behavior is run too
On Android, callback is -1 for both iap and restore.
@Armelline That was the problem, I just tried "Generate APK" instead of "Build RC"and it worked! Thank you!
@Acroxia Give it a try and see if it works for you
@Baguvix Thanks! I will try it!
If using Generate APK fixed the issue I'd best tag @adent42 into this thread so he's aware there's a potential issue with the RC.
Try pushing a copy of your app as an Alpha or Beta. We found we had to do that to get testing to work with the new billing framework.
@adent42 I've registered a new version.
Google approved it.
Download it to my Android device through the Play Store.
I opened a cash shop and bought it.
The result is only callback -1 printed and the purchase fails.
@adent42 same thing here, I promoted my internal testing to a Closed and Open testing track. After Google approved, I tested and IAP still doesn't work
update new version in google
Show caution message 'Your app has been verified to use an earlier version of Google Play payment. All app updates must use payment library version 3 or later by November 1, 2021. Please update to version 3 of the payment library before this date.'
@Acroxia are you using Build RC? We're using Google Billing 3 in that one.
@adent42 I got the same message and I am using Build RC
@adent42 Yes. using Build RC
We may have found the issue, we're working to get a new release out ASAP.
Oh! Great News! Thanks.
Thank you very much for this update.
I still get a message when I update on Google Play after RC build.
'Your app has been verified to use an earlier version of Google Play payment. All app updates must use payment library version 3 or later by November 1, 2021. Please update to version 3 of the payment library before this date.'
i submitted a new app a few days ago and got the same warning about billing.
the other thing, when tinkering with in app purchases, I followed a tutorial on YouTube. the purchase seems to read as being bought, unless you submit/generate your build with 'unpurchased' already in column 5 of the purchase table.
Yes you'll continue to get the warning, I believe until we upgrade our build system.
We are using Billing 3.0 (so it should actually work) past that date, but we hope to have an update that Google will recognize soon.
We'll look into the 'unpurchased' thing.