Google In-App Purchases Not Working

Solar2D Android
#2

You should try IAP Badger, which streamlines IAP and makes it easier to work with in Corona apps:

https://forums.coronalabs.com/topic/59137-iap-badger-a-unified-approach-to-in-app-purchases

#3

According to Google:

BILLING_RESPONSE_RESULT_DEVELOPER_ERROR 5 Invalid arguments provided to the API. This error can also indicate that the application was not correctly signed or properly set up for In-app Billing in Google Play, or does not have the necessary permissions in its manifest

http://developer.android.com/google/play/billing/billing_reference.html

There are three things this identifies:

  1. It’s not signed correctly.

  2. Something isn’t setup correctly in Google Play

  3. You’re missing permissions.

Your permissions look right. I doubt you could upload the app if it wasn’t signed correctly. BTW: you can upload it as Alpha or Beta status and be able to test it. You don’t have to make it live.

This leaves #2 as the most likely issue.

Rob

#4

Thanks for the feedback Alex & Rob.

Rob,

I have confirmed that my product ID’s in Google play match what is in the code.  What else might be set up wrong in Google Play? 

Thanks!

#5

One gotcha with building an app through Corona SDK while using the Google IAP v3 plugin is that you need to ensure these options in the android build dialog match the APK you’ve uploaded to Google Play Dev Console. Otherwise, your purchases won’t work:

Application Name

Version Code

Version Name

Package

Furthermore, make sure you sign with the same keystore as the app you uploaded to Google Play Dev Console.

#6

When I’ve had this error in the past, I’m sure it was because I was testing an app that had a version code that was later/larger than the last version I’d uploaded to Google Play console.

#7

I’m having similar problems with Google IAP, was there a conclusion/fix?

#8

Hello!

I have app A published on store A (mine). It works fine. I can buy IAP products as tester with my C account.

But I have an other app B, published on store B (that of my client, where I have permissions). On that one, I’m having the error: “Unable to buy item(response:5: Developer Error)” when trying to buy items as alpha tester. I even tried with product “android.test.purchased”, or with an invented product id, but I got the same result.

Both apps are done with Corona. In both aps iap is managed the same way. And both are signed with the same certificate.

For B app, on build.settings I have:

android ={ usesPermissions = {             "android.permission.INTERNET",             "com.android.vending.BILLING", }, }, plugins =     {     -- ADS         ["plugin.google.play.services"] =         {             publisherId = "com.coronalabs"         },                  -- IAP         ["plugin.google.iap.v3"] =         {             publisherId = "com.coronalabs",             supportedPlatforms = { android=true }         },     }, 

On config.lua:

   license =     {         google =         {         -- key taken from Services and APIs section of B app             key = "MIIBIjANB...wIDAQAB"         },     }, 

I’ve checked too what Ajay says… App Name and Package Name are the same on Corona Simulator and on Play Store, and the version number on Play Store is set automatically from apk, so it’s the same too.

Thank you for you time

#9

Hi mariona dsr,

Just to clarify, app B is published on Google Play Dev Console with the same keystore as app A?

If that’s the case, you’ll probably need to use a separate keystore for app B than app A.

#10

Hello!

Yes, I use the same certificate, from the same keystore, to sign both apps.

I’ll try with different keys and I let you know. Thank you!

#11

:o

I’m really ashamed to confess than the true problem was not the certificate, nor the package name, nor nothing so difficult.

I was just that the parameter that I passed to store.purchase doesn’t exist.

So, if someone never have this problem, “Unable to buy item(response:5: Developer Error)”, verify at least three time that you are passing something as product identifier  ;) 

Thank you Ajay for your attention.

#12

You should try IAP Badger, which streamlines IAP and makes it easier to work with in Corona apps:

https://forums.coronalabs.com/topic/59137-iap-badger-a-unified-approach-to-in-app-purchases

#13

According to Google:

BILLING_RESPONSE_RESULT_DEVELOPER_ERROR 5 Invalid arguments provided to the API. This error can also indicate that the application was not correctly signed or properly set up for In-app Billing in Google Play, or does not have the necessary permissions in its manifest

http://developer.android.com/google/play/billing/billing_reference.html

There are three things this identifies:

  1. It’s not signed correctly.

  2. Something isn’t setup correctly in Google Play

  3. You’re missing permissions.

Your permissions look right. I doubt you could upload the app if it wasn’t signed correctly. BTW: you can upload it as Alpha or Beta status and be able to test it. You don’t have to make it live.

This leaves #2 as the most likely issue.

Rob

#14

Thanks for the feedback Alex & Rob.

Rob,

I have confirmed that my product ID’s in Google play match what is in the code.  What else might be set up wrong in Google Play? 

Thanks!

#15

One gotcha with building an app through Corona SDK while using the Google IAP v3 plugin is that you need to ensure these options in the android build dialog match the APK you’ve uploaded to Google Play Dev Console. Otherwise, your purchases won’t work:

Application Name

Version Code

Version Name

Package

Furthermore, make sure you sign with the same keystore as the app you uploaded to Google Play Dev Console.

#16

When I’ve had this error in the past, I’m sure it was because I was testing an app that had a version code that was later/larger than the last version I’d uploaded to Google Play console.

#17

I’m having similar problems with Google IAP, was there a conclusion/fix?

#18

Hello!

I have app A published on store A (mine). It works fine. I can buy IAP products as tester with my C account.

But I have an other app B, published on store B (that of my client, where I have permissions). On that one, I’m having the error: “Unable to buy item(response:5: Developer Error)” when trying to buy items as alpha tester. I even tried with product “android.test.purchased”, or with an invented product id, but I got the same result.

Both apps are done with Corona. In both aps iap is managed the same way. And both are signed with the same certificate.

For B app, on build.settings I have:

android ={ usesPermissions = {             "android.permission.INTERNET",             "com.android.vending.BILLING", }, }, plugins =     {     -- ADS         ["plugin.google.play.services"] =         {             publisherId = "com.coronalabs"         },                  -- IAP         ["plugin.google.iap.v3"] =         {             publisherId = "com.coronalabs",             supportedPlatforms = { android=true }         },     }, 

On config.lua:

   license =     {         google =         {         -- key taken from Services and APIs section of B app             key = "MIIBIjANB...wIDAQAB"         },     }, 

I’ve checked too what Ajay says… App Name and Package Name are the same on Corona Simulator and on Play Store, and the version number on Play Store is set automatically from apk, so it’s the same too.

Thank you for you time

#19

Hi mariona dsr,

Just to clarify, app B is published on Google Play Dev Console with the same keystore as app A?

If that’s the case, you’ll probably need to use a separate keystore for app B than app A.

#20

Hello!

Yes, I use the same certificate, from the same keystore, to sign both apps.

I’ll try with different keys and I let you know. Thank you!

#21

:o

I’m really ashamed to confess than the true problem was not the certificate, nor the package name, nor nothing so difficult.

I was just that the parameter that I passed to store.purchase doesn’t exist.

So, if someone never have this problem, “Unable to buy item(response:5: Developer Error)”, verify at least three time that you are passing something as product identifier  ;) 

Thank you Ajay for your attention.