in-app-billing

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

好久不见. 提交于 2019-11-27 13:14:29
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 to test actual purchases via the beta/alpha channels - not straight from android studio. This post

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

守給你的承諾、 提交于 2019-11-27 11:20:52
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", "packageName":"my package name", "productId":"77", "purchaseTime":1366217534000, "purchaseState":0,

Google Play In-App Purchase returns error code -1008: null puchaseData or dataSignature

那年仲夏 提交于 2019-11-27 11:12:22
问题 I am attempting to implement Google Play in-app purchase v3, after successfully implementing it in v2. However, every single time I attempt to purchase one of my real in-app products, I receive the following follow-up error: IAB returned null purchaseData or dataSignature (response -1008:Unknown error) This is coming from the IabHelper.java class, line 452: if (purchaseData == null || dataSignature == null) { logError("BUG: either purchaseData or dataSignature is null."); logDebug("Extras: "

android in app billing purchase verification failed

十年热恋 提交于 2019-11-27 10:34:21
问题 i' having trouble implementing in app billing in my android app. i'm getting a purchase signature verification failed. In a first time i tough it was the base64 key but i checked it many times and i'm still getting the error, then after i took a look at the Security.java file and i found this method which i edited for get some informations about what was wrong: public static boolean verifyPurchase(String base64PublicKey, String signedData, String signature) { if (TextUtils.isEmpty(signedData)

How to verify purchase for android app in server side (google play in app billing v3)

元气小坏坏 提交于 2019-11-27 10:03:36
I have a simple app (needs user login with account). I provide some premium features for paid users, like more news content. I need to record if the user has bought this item in my server database. When I provide data content to user's device, I can then check the user's status, and provide different content for paid user. I checked the official Trivialdrive sample provided by Google, it does not provide any sample code for server-side verification, here are my questions. I found the sample use my app's public key inside to verify purchase, it looks not good, I think I can just move the

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

旧时模样 提交于 2019-11-27 09:30:57
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? 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 Service here but a direct call of getPurchases). Of course, this means that one will almost always get a

Billing API v3 IabHelper NullPointerException

落花浮王杯 提交于 2019-11-27 09:24:28
问题 edit 4/15: Catching nullpointer in IabHelper appears to have stopped this problem. I am no longer seeing the exceptions being thrown, I'm going to accept this as an answer. edit 4/04: A little bit of a deeper dive. There are try catch blocks that handle RemoteExceptions and JSONExceptions for the queryPurchases method, but no NullPointerException handling. What I am going to try is include NullPointer Exception handling so IabHelper looks like this when trying to querySkuDetails: catch

In-App billing connect to Firebase and get Products

久未见 提交于 2019-11-27 09:08:20
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 | | | --- productId2 : true | --- products | | | --- productId1 | | | | | --- productName: "Apples" | | | | | -

the item you requested is not available for purchase

╄→尐↘猪︶ㄣ 提交于 2019-11-27 06:17:40
I'm trying to integrate Android Market in-app purchases into my app, but unfortunately coming across an annoying error every time I try to purchase a real inapp product. I've taken the sample application (Dungeons) and added it to my app. I've updated the Public Key and also updated the list of products to the following: /** An array of product list entries for the products that can be purchased. */ private static final CatalogEntry[] CATALOG = new CatalogEntry[] { new CatalogEntry("full", "Full v", Managed.MANAGED), }; I've exported the application using Eclipse, and installed it on my phone

Does In App Billing support multiple accounts?

|▌冷眼眸甩不掉的悲伤 提交于 2019-11-27 06:00:41
问题 Does InApp billing (V2 or V3) works for a user who uses several accounts and makes the purchase with an account that isn't the primary one? PD: Some explanation required, no simple Yes/No 回答1: In App Billing support multiple accounts reported as a bug in code.google, have a look at it According to Mr.Sergej (posted in G+ android dev community) in-app products purchased with the first account won't be active anymore while using multiple user accounts!. 回答2: InApp billing just charges the user