Categories
android apk google-play in-app-billing

This version of the application is not configured for billing through Google Play

327

When I try to run my application with in-app billing I am getting the error: “This version of the application is not configured for billing through Google Play. Check the help center for more information”.

I have the billing permission already in the Manifest file and I have a signed .apk uploaded as a draft onto Google Play and I have also installed that same signed apk onto my phone.

Any help on how to solve this issue?

1

  • 2

    I have this problem on real device, but not on emulator. I install the same build on the emulator and device. I logged in as the same user on both emulator and device. On device I got this-version-of-the-application-is-not-configured-for-billing error, on emulator everything works normally and dialog with test card appears. What the difference?

    – Aleksey_M

    Dec 31, 2020 at 14:14

202

Ahh found the solution after trying for a couple of hours.

  1. Google takes a while to process applications and update them to their servers, for me it takes about half a day. So after saving the apk as a draft on Google Play, you must wait a few hours before the in-app products will respond normally and allow for regular purchases.
  2. Export and sign APK. Unsigned APK trying to make purchases will get error.

11

  • 82

    Wow, is this serious? Just ran into the same problem. Did everything Google asked me to do in order to test in-app billing, but still getting the same evasive error message. I guess I’ll have to wait and see. But does Google really expect us developers to wait hours each time we need to update our app in order to implement in-app billing? It seems quite inappropriate to me, to say the least.

    – Simon

    Aug 6, 2012 at 20:16

  • 8

    Can you test while connected to Android Studio / running while connected to the debugger? Or do you need to install the release apk via USB?

    Aug 1, 2013 at 19:37

  • 5

    Is there an easier way to test the purchase process other than, Android Tools > Export signed project… etc, then manually copy APK across to device, Test, …. repeat? I must be missing something?

    – wired00

    Aug 28, 2013 at 4:23

  • 4

    Seriously, I cannot use the application with debug certificate and test In-App Billing?

    – TacB0sS

    Sep 12, 2013 at 5:28

  • 8

    Note that you CAN use debug builds, straight from your IDE as you are working. You just need to change the debug keystore to one that matches your release store. See this post for more information on how: stackoverflow.com/questions/10886814/…

    May 14, 2014 at 4:23

202

Ahh found the solution after trying for a couple of hours.

  1. Google takes a while to process applications and update them to their servers, for me it takes about half a day. So after saving the apk as a draft on Google Play, you must wait a few hours before the in-app products will respond normally and allow for regular purchases.
  2. Export and sign APK. Unsigned APK trying to make purchases will get error.

11

  • 82

    Wow, is this serious? Just ran into the same problem. Did everything Google asked me to do in order to test in-app billing, but still getting the same evasive error message. I guess I’ll have to wait and see. But does Google really expect us developers to wait hours each time we need to update our app in order to implement in-app billing? It seems quite inappropriate to me, to say the least.

    – Simon

    Aug 6, 2012 at 20:16

  • 8

    Can you test while connected to Android Studio / running while connected to the debugger? Or do you need to install the release apk via USB?

    Aug 1, 2013 at 19:37

  • 5

    Is there an easier way to test the purchase process other than, Android Tools > Export signed project… etc, then manually copy APK across to device, Test, …. repeat? I must be missing something?

    – wired00

    Aug 28, 2013 at 4:23

  • 4

    Seriously, I cannot use the application with debug certificate and test In-App Billing?

    – TacB0sS

    Sep 12, 2013 at 5:28

  • 8

    Note that you CAN use debug builds, straight from your IDE as you are working. You just need to change the debug keystore to one that matches your release store. See this post for more information on how: stackoverflow.com/questions/10886814/…

    May 14, 2014 at 4:23

144

The same will happen if your published version is not the same as the version you’re testing on your phone.

For example, uploaded version is android:versionCode="1", and the version you’re testing on your phone is android:versionCode="2"

6

  • 3

    can u tell please me what if uploaded version is android:versionCode="1" and phone is android:versionCode="2" dose it ok or i have to change my apk google play ?.

    – Youddh

    Dec 17, 2012 at 7:35

  • 2

    What you need to do is to bump down the local version to “1” so it matches the current live version, as least temporarily for testing.

    – Romain

    Feb 12, 2013 at 13:30

  • 2

    Looks like there are 2 common fixes to this error depending on your situation. In my case it was this one.

    – Matt

    May 20, 2013 at 12:44

  • Thank you, this was the issue. Was debugging fine with release signed apk on my attached device. Then, changed the versioncode and it started getting the 1005 error. whew!

    Apr 12, 2014 at 1:22

  • @Anna be aware that -1005 is also USER_CANCELLED if you use iabHelper

    Mar 20, 2015 at 17:09