Hei, I've worked out a theory that seems to hold up.
1/ Starting with the assumption "Perhaps the error is actually meaningful" I got some logs to prove Google Play Services generates the fault. Which it appears to do. 2/ Then I worked on the assumption I do not see the opt-in promised Testing version because Google Play thinks I've already got it. That is to say, I assumed if the alpha APK Release certificate and the Manifest version number matches that which was "adb shell pm install'ed" onto my phone - as the docs/stackoverload posts imply you should - then Google Play doesn't offer the release Testing version. In fact, it might be just the Manifest version number alone that is compared. So either you shouldn't adb shell the release onto your device - or if you do, then you should delete it. Or install an older version. 3/ The undocumented theory - the act of installing a release APK includes its traversal of Google Play Services, which record it's permissions. If you don't traverse it on installation, Google Play Services has no record of the release permissions and will refuse runtime "manifest level" access requests, like in-app billing. So "adb shell'ing" the latest release version onto your device will result in the Error. Hope this theory helps On Saturday, December 19, 2015 at 9:19:10 AM UTC, julian wrote: > > Hei, > > Problem: I get the Error "This version of the application is not > configured for billing through Google Play". I don't want to get this. > Please see attached images. > > My app is published to alpha and I only wish to test in-app billing. > My app uses IABv3. > Mine is the only account on the test device. It is not the same as the > developer identity. The test device is recognised in the list of supported > devices. > I have successfully used SKU "android. test.purchased" for a couple of > months. > With the alpha debug build loaded from studio, this sku works perfectly > with my app license key, resulting in the "30 minutes..." invite. So I > deduce google play recognises my public license key. > Using the release alpha build loaded using "adb shell pm install..." > android.test.purchased also works perfectly. > Using a non-existent SKU results in the different "authentication is > required" error. So I deduce google play recognises my correct sku. > Perhaps the error is actually meaningful. The alpha testers opt-in page > suggests I should expect to get a Testing version - I don't see this > happening. Maybe I am not getting the testing version, but just running the > adb-loaded version, and this is why I see the error? > > The ONLY changes I have made in the alpha build from my totally otherwise > working and publishable development build are to replace the SKU and the > LICENSE KEY with correct (yes i checked) values. > > This app is my first attempt at a release, and is a new experience for me. > I have read numerous google guides, as in > http://developer.android.com/index.html#q=in-app%20billing. > I have searched stackoverflow likewise. I have multplie times checked the > list given on > http://stackoverflow.com/questions/11068686/this-version-of-the-application-is-not-configured-for-billing-through-google-pla, > > although I have not tried debugging with the release certificate. > > It is very likely I am not doing something that needs doing. > Any hints greatly appreciated. > Many thanks. > julian > > -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. To post to this group, send email to android-developers@googlegroups.com. Visit this group at https://groups.google.com/group/android-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/android-developers/ad211247-603e-4ac5-86e8-d1e063d22b0e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
