8

I'm trying to add in-app purchase for my existing published app that didn't previously have billing permission. I've uploaded an updated APK with billing permission, but didn't activate it since I don't want to publish this draft. However, I can't add in-app product - it still says "the current application version does not use the BILLING permission". Any way to solve/work around this problem?

Violet Giraffe
  • 32,368
  • 48
  • 194
  • 335
  • You upload it and activate it. Then save as draft, **not publish**. You can still save as a draft for a live app, if you upload a new version – Blundell Dec 28 '12 at 21:28
  • @Blundell: I don't understand. I can activate/deactivate APKs, and I can save the whole thing, which will make all the active APKs published. I don't see a way to activate and save without publishing. – Violet Giraffe Dec 29 '12 at 08:59
  • I have done this myself and trying to remember the steps, hence comment and not answer. I've got this vague memory that, if you upload it don't activate it like you said and hit save (so your unactivated apk has the permission) you should be able to add items! Are you sure you've got the billing permissions correct? I know it's possible so you are just going to have to do some trial and error – Blundell Dec 29 '12 at 12:43
  • @Blundell: Permissions are correct. When I activate the new dummy APK (version 36, and the APK I need to remain published is 34) I get a message: `Error: APK version 34 supports all the same devices as other APKs with higher versions. It would not be served. Please deactivate an APK.` – Violet Giraffe Dec 29 '12 at 13:02
  • why don't you try to sign your apk and test the in-app billing in that way...I guess it should work, because while app is signed with android debug key, you can't test in-app... – hardartcore Dec 29 '12 at 13:13
  • @Android-Developer: if it was unsigned Google Play wouldn't let me upload it. – Violet Giraffe Dec 29 '12 at 14:06
  • No, it should be signed with your key, but im not sure if you must upload it to the store. Just sign an apk file with another key, not android debug, and try with the test products if you will be able to use them. – hardartcore Dec 29 '12 at 14:15
  • @Android-Developer: I think you misunderstood my question. I'm having problem with adding products to Google Play in the first place. That's exactly what I need to do right now. – Violet Giraffe Dec 29 '12 at 14:54
  • Do you have a merchant account in google? If you don't have and your country is not supported you won't be able to add in-app products until you add a merchant account. – hardartcore Dec 29 '12 at 16:38
  • @Android-Developer: Yes I have it. As stated in the question, the proble I need to solve is `the current application version does not use the BILLING permission`. – Violet Giraffe Dec 29 '12 at 18:16
  • hmm that's not something which I had to deal while i was implementing in-app billing to my app.My suggestion in that case is just to add in-app permission to your current app and upload it without any other changes and publish it. After that I guess you will be able to create in-app products and everything you need. Hope that helps and works for you. – hardartcore Dec 29 '12 at 19:01
  • Check this out: http://developer.android.com/google/play/billing/billing_testing.html on the bottom you have 6 steps that needs to be done in order to test in app purchase. And also verify that you done this: The application does not need to be published, but the item does need to be published – Alex Jan 01 '13 at 20:11
  • @Alex: That's not what I need, it's about testing new application that you upload from scratch, no problems there. – Violet Giraffe Jan 01 '13 at 20:14
  • @Violet Giraffe There is nothing about a new application, I used those steps to add in-app purchase into my existing, published app. Of course version of application that you test should be a new one with defined permission – Alex Jan 02 '13 at 14:14
  • @VioletGiraffe Did you ever figure a way around this? I published my app a few hours ago with Billing permissions (just bit the bullet and tried disabling those features... even though there is a ton of other features in this update that are not test ready, but whatever thanks google play) and still seeing that stupid message. Did it take a few hours for it to come through? – K2xL May 11 '13 at 21:12
  • @K2xL: it did take a few hours. – Violet Giraffe May 11 '13 at 21:31

1 Answers1

1

Change Android version code in Androidmanifest.xml file.

android:versionCode="1"

suppose if your Application version code is 1 now change to 2

laxman
  • 1,884
  • 4
  • 15
  • 22