IAP Badger not connecting in Google Play

Hi,

I’ve tried using IAP badger for my IAP purchase. I’ve made modifications from the badger I got from github and uploaded it in google dev console. I’m not getting any errors from the one i’m running in the simulator but it still won’t connect in google play. The setup in google dev console is already done. I’ve tried almost everything. I will paste the link for the codes below:

main.lu = http://pastebin.com/k1TjRK6t

config.lua = http://pastebin.com/HQLEXkzb

build.settings = http://pastebin.com/Tt1Z00Cb

Note:

I am not the admin of the google play developer console and I uploaded the apk in beta testing.

Thank you!

Yla

I didn’t read through all of the main.lua, but did you really use “50_coins” / “100_coins” as the Google productName? You should have the unique identifier there, for example “com.yourdomainname.yourappname.50_coins”.

And, did you fill in your app license key in the config.lua or did you leave it with

key = “my key”,

?

You definitely need to enter your key correctly - you can copy and paste this from the Google Play console entry for your app.

Simon

Hi,

I’m sorry I forgot to update this. I already got this working. I have my key when I posted this concern. If you will look at the config.lua, I wrote the application table twice! It’s just a typo that I overlooked. 

I got this working by testing a modified build that is not uploaded in Google Play with the same package name, version name and the IAP works. Then when I tried updating my apk in Google Dev Console, it goes back again to contacting Google Play, the IAP does not work. Any idea why?

@klippstein1 What’s the disadvantage/difference if I use 100_coins vs com.domainname.appname.50_coins? Just curious.

Thanks for your help and thanks for this great plugin @happymongoose!

Yla

Hi Yla,

Try uploading your apk and waiting for a while - there may be something going on with the version number that needs to propagate through Google’s servers around the world before you can test it (ie. your closest Google Play server might think you’re attempting to use a higher APK number than the one it recognises, because it hasn’t picked up the change yet).

I think that made sense.

Simon

Hi Simon,

Yes! That’s about it. I tried just now the apk from Google Play and it works. Thank you!

Yla

I didn’t read through all of the main.lua, but did you really use “50_coins” / “100_coins” as the Google productName? You should have the unique identifier there, for example “com.yourdomainname.yourappname.50_coins”.

And, did you fill in your app license key in the config.lua or did you leave it with

key = “my key”,

?

You definitely need to enter your key correctly - you can copy and paste this from the Google Play console entry for your app.

Simon

Hi,

I’m sorry I forgot to update this. I already got this working. I have my key when I posted this concern. If you will look at the config.lua, I wrote the application table twice! It’s just a typo that I overlooked. 

I got this working by testing a modified build that is not uploaded in Google Play with the same package name, version name and the IAP works. Then when I tried updating my apk in Google Dev Console, it goes back again to contacting Google Play, the IAP does not work. Any idea why?

@klippstein1 What’s the disadvantage/difference if I use 100_coins vs com.domainname.appname.50_coins? Just curious.

Thanks for your help and thanks for this great plugin @happymongoose!

Yla

Hi Yla,

Try uploading your apk and waiting for a while - there may be something going on with the version number that needs to propagate through Google’s servers around the world before you can test it (ie. your closest Google Play server might think you’re attempting to use a higher APK number than the one it recognises, because it hasn’t picked up the change yet).

I think that made sense.

Simon

Hi Simon,

Yes! That’s about it. I tried just now the apk from Google Play and it works. Thank you!

Yla