in-app-billing

My question is centered around handling in-app purchases for consumables with Google's In-App Billing API. ( https://developer.android.com/google/play/billing/api.html#consumetypes ) Their documentation describes consumables as: Consumable products In contrast, you can implement consumption for products that can be made available for purchase multiple times. Typically, these products provide certain temporary effects. For example, the user's in-game character might gain life points or gain extra gold coins in their inventory. Dispensing the benefits or effects of the purchased product in your

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 Android Market server, of course, since by design it only works with a signed release version). Then I

I am trying to integrate In app billing v3 in my app. I call the following function to initialize. public static void SetupInappBilling() { mHelper = new IabHelper(context, base64EncodedPublicKey); mHelper.enableDebugLogging(true); mHelper.startSetup(new IabHelper.OnIabSetupFinishedListener() { public void onIabSetupFinished(IabResult result) { if (result.isSuccess()) { Log.e("tag", "connected"); ConnectionEstablished = true; } else { Log.e("tag", "not connected"); ConnectionEstablished = false; } } }); } but i dont get call back in OnIabSetupFinishedListener Can anyone tell me how to fix this

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)? 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 editing the metadata. When creating a package from a file, be sure to use the Application Loader template.

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, or personal account information with others. Does anybody know a work around for this? While in

How to do restore transaction in in-app billing purchase android. So far I have searched in all links. I didn't find exact infromation. I have used BillingHelper.restoreTransactionInformation(BillingSecurity.generateNonce()) but it returns nothing. Can anyone help me to come out of this problem. Any help would be appreciated. The V3 of the api does not require anymore to restore the purchases. Can directly query for purchased items. Please read the section Querying for Purchased Item of: http://developer.android.com/google/play/billing/billing_integrate.html and the getPurchases() method

I am implementing in-app billing in my app to unlock premium features. The in-app billing sets up correctly. Everything seems fine except the 'developer payload' thing. The sample app says /* * TODO: verify that the developer payload of the purchase is correct. It will be * the same one that you sent when initiating the purchase. * * WARNING: Locally generating a random string when starting a purchase and * verifying it here might seem like a good approach, but this will fail in the * case where the user purchases an item on one device and then uses your app on * a different device, because on