in-app-billing

In-App Billing test: android.test.purchased already owned

由 China☆狼群 提交于 2019-11-26 18:47:28
问题 I am currently testing In-App Billing for a future app, and after I successfully "bought" the test item "android.test.purchased" the first time, I now receive the response code 7 every time I try to buy it again, which means that I already own this item. 12-15 23:02:14.149: E/IabHelper(19829): In-app billing error: Unable to buy item, Error response: 7:Item Already Owned From what I understand, this purchase is supposed to always be possible, right? So that the developer can test his/her app?

Why is the Google Play Billing Library not shown up in the SDK Manager?

由 只愿长相守 提交于 2019-11-26 17:16:01
问题 I'd like to make an android application with in app purchases, I read often that I have to download the Google Play Billing Library from SDK Manager (e.g. http://www.techotopia.com/index.php/An_Android_Studio_Google_Play_In-app_Billing_Tutorial#Installing_the_Google_Play_Billing_Library ), but I can't find it there. Does I need this file? If yes, how can I manage that it is shown to me? On the developers.android webside is nothing written of the Google Play Billing Library, but if I copy

Is it possible to debug locally Google Play's in-app billing in Android Studio?

由 纵饮孤独 提交于 2019-11-26 15:59:59
问题 I am getting this error testing in-app subscription products locally. authentication is required. you need to sign in to your google account I was able to check the the inventory for the product but shouldn't I also be able to purchase it? There are a number of posts about why this error might occur which I thought were addressed: the product is released in the beta channel with in-app billing enabled i am logged into Play Store with a test user licensed account on the device. Is the only way

Server-side verification of Google Play In-app billing version 3 purchase

由 六月ゝ 毕业季﹏ 提交于 2019-11-26 15:28:53
问题 I'm unable to find a straight answer as to how I verify an in-app billing purchase on the server before making downloadable content available to the user. I use in app-billing version 3. I purchase managed products using code based on the IabHelper class from the TrivialDrive sample code. Everything is fine and dandy and the purchase is successfully completed, I get a full Purchase object back and the following original JSON data: { "orderId":"12999763169054705758.1364365967744519",

Android: Which response code does in-app billing V3 return upon timeout?

由 眉间皱痕 提交于 2019-11-26 14:44:28
问题 Which response status code(s) will the Google Play In-App Billing Serv{ice,er} V3 return upon a network timeout condition? Is this uniform amongst all of its functions? 回答1: I will describe my findings here. I have tested this on an AVD with a fully featured GP installed (GP Store V3.10.10, GP Services 2.0.12, G Services Framework 4.1.2), by pulling the host's plug. The getPurchases() method returns a cached result if possible (please note that we're not talking about a cache outside of the

In-App billing connect to Firebase and get Products

由 喜欢而已 提交于 2019-11-26 14:25:13
问题 I'm starting to create an APP where I can buy items from it. Could be like this: where you can see an Image , Name of product , and Price . Well, I allready have a Sign-in with Google made with Authentication Firebase and I store it on Firebase database , I'd like to create the following this structure that @Alex Mamo recommend to me : Firebase-root | --- users | | | --- uid1 | | | --- //user details (name, age, address, email and so on) | | | --- products | | | --- productId1 : true | | | --

onIabPurchaseFinished never called.

由 本秂侑毒 提交于 2019-11-26 12:36:42
问题 I\'ve been trying to set up in-app billing for my first app, and have been using the android.test.purchased sku. The purchase come through, and I manage to get the SKU into my inventory, but, as the title says, onIabPurchaseFinished, is never called. I think it may have something to do with this Log: \"Couldn\'t save which view has focus because the focused view com.android.internal.policy.impl.PhoneWindow$DecorView@406743d0 has no id\". That pops up, right before going of to Google Play. I\

Google In-App billing, IllegalArgumentException: Service Intent must be explicit, after upgrading to Android L Dev Preview

由 冷暖自知 提交于 2019-11-26 11:14:43
My in-app billing code was working fine until I upgraded to the Android L Dev Preview. Now I get this error when my app starts. Does anyone know what's changed about L that causes this or how I should change my code to fix this? android { compileSdkVersion 'android-L' buildToolsVersion '20' defaultConfig { minSdkVersion 13 targetSdkVersion 'L' ... ... compile 'com.google.android.gms:play-services:5.+' compile 'com.android.support:support-v13:21.+' compile 'com.android.support:appcompat-v7:21.+' ... ... The error when the app starts: 06-29 16:22:33.281 5719-5719/com.tbse.wnswfree D

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

由 十年热恋 提交于 2019-11-26 05:53:25
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? Luten This error may be caused by several reasons. Here is the list of requirements for the Google IAB testing. Prerequisites: AndroidManifest must include "com.android

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

由 风格不统一 提交于 2019-11-26 01:56:23
问题 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: This error may be caused by several reasons. Here is the list of
订阅 in-app-billing