in-app-billing

Google Play Order ID updated to new format

◇◆丶佛笑我妖孽 提交于 2019-11-28 09:14:04
All my recent Android app purchases show a new order ID format. The OLD format: [merchant ID].[actual order ID] We could use this format to check if the prefix of the order ID matches with the merchant ID and prevent possible hacks by apps like Freedom. The NEW format: GPA. 1234-5678-9123-45678 All my recent orders start with " GPA. " (yes the additional dot is also there) There is a 17 digit number divided into 4 blocks The first 3 blocks contain 4 digits each and the last having 5 digits I want to know what does this number represent, the significance of the sub-blocks, is the merchant ID

Why Can't Google's Market Billing Sample Build in a Signed Release Version?

旧城冷巷雨未停 提交于 2019-11-28 07:27:40
问题 I tried looking into similar problems, but the solutions offered there do not seem to fit my particular situation: I initially followed the instructions for Configuring and building the sample application for In-app Billing, replacing the security key with the public key from Google's Developer account and changing the package name from com.example to com.billtheape . I then built a non-release version and ran a "sanity check" on my Android phone. Everything went OK (except for accessing the

User is not eligible for this purchase - in app billing

风流意气都作罢 提交于 2019-11-28 06:51:36
I'm getting "User is not eligible for this purchase" message from google play while trying to purchase as a test. I've uploaded singed apk in google play, published the billing item(in app product), saved the apk as draft, still getting this error. Also I was trying to purchase from test user device. Edit: The actual reason for this error: If an unauthorized user try to purchase an item then this message should appear. So if the App is not published, a non test user should get this error while try to purchase. I realized that, Google play takes time to update the changes in app store. So you

in-app billing doesn't work: “IAB Helper is not set up”

六眼飞鱼酱① 提交于 2019-11-28 06:49:20
I tried to include in-app billing in my app and for the purpose of testing, based the whole procedure on the "TrivialDrive" example for version 3 of in-app billing (and implementing the unmodified versions of the IAB files as supplied in the "util" subdirectory of the demo), but it doesn't work for me - on LogCat, just before the app terminates with an error, it gives the message "In-app billing error: Illegal state for operation (launchPurchaseFlow): IAB Helper is not set up. " (right after the startRegistered() function has been fired and given me the LOG message "Register button clicked;

IabHelper PurchaseFinishedListener

∥☆過路亽.° 提交于 2019-11-28 05:54:10
If I send a purchase intent via the standard String mySku = "android.test.purchased"; mHelper.launchPurchaseFlow(this, mySku, 10001, mPurchaseFinishedListener); I am able to purchase the item and it will store and I can query the item and that works fine too. The only thing that doesn't work is is the PurchaseFinishedListener. I've got it coded pretty much identical to the sample app however it doesn't seem to get called at all. 12-12 01:40:47.248: D/IabHelper(23502): Calling getPurchases with continuation token: null 12-12 01:40:50.116: D/IabHelper(23502): Starting async operation:

iOS How I can load multiple in-app items

≯℡__Kan透↙ 提交于 2019-11-28 05:04:31
问题 Is there a way to load multiple items together on in-app billing section on itunes connect dashboard (for example with a .csv file like Android)? 回答1: You can use the Application Loader to mass import in app purchases: https://itunesconnect.apple.com/docs/UsingApplicationLoader.pdf Read the "Creating a Package from a File" section on page 15: You can create a package containing the In-App Purchase you want to submit to iTunes by importing details from an Application Loader file and adding and

Google Play error “Error while retrieving information from server [DF-DFERH-01]”

[亡魂溺海] 提交于 2019-11-28 04:37:39
I'm just finishing a game for android and I'm testing out the in app purchase functions. I'm sending testing using android.test.purchased It was working fine until a few hours ago. But now when I click the "accept and buy" in google play, the store gives the error. Google play error "Error while retrieving information from server [DF-DFERH-01]" Does anyone know what this error means? Try this, as it solved in my case on a Samsung mobile phone: 1. Open the "Google Play" app and press the home button to return 2. Go to Settings → Applications → Manage Applications 3. Select the "ALL" tab, Search

Testing Android In App Billing real purchases

此生再无相见时 提交于 2019-11-28 03:16:36
What are the conditions to properly test real purchases, when i already have tested my app using test product like android.test.purchased ? There are few steps that you need to pass, remembering, that some of them need some time to update on Google Play servers. For this example, let's use com.example.product as our real product Id. Any time it shows up in this example change it to your own. UPLOAD APK FILE You CAN'T test REAL PURCHASES in DEBUG mode. You need to download an app from Beta, so Google know it's ok to make purchases in the app. Check if you have BILLING permission in

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

风流意气都作罢 提交于 2019-11-28 02:50:40
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? If not, how can I "reset" its state to not owned? I am using the util package from the Google In-App

Testing Android Market in-app billing with dummy credit card credentials

随声附和 提交于 2019-11-28 02:26:48
问题 I have configured an Android application to use the in-app billing module as documented at: http://developer.android.com/guide/market/billing/index.html It works fine when tested using the UK development team's accounts which have real credit cards associated with them. However, part of my development team is based in China, and as Google Billing does not operate in China, they are unable to test the billing functionality. Understandably the team is uncomfortable sharing personal card details