in-app-billing | 易学教程

Restore transaction inapp purchase android

阅读更多关于 Restore transaction inapp purchase android

问题 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. 回答1: 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:

What should be the developer payload in android in-app billing v3 api?

阅读更多关于 What should be the developer payload in android in-app billing v3 api?

问题 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

Android In-App Billing : Security.java says “Signature Verification Failed”

阅读更多关于 Android In-App Billing : Security.java says “Signature Verification Failed”

问题 I have implemented a test app with Android's In-App Billing. I have filled in my Public Key in the Security.java file. Everything works, but when I submit the payment, the app crashes. I receive an error in LogCat that says "Signature Verification Failed", which corresponds to this bit of code: if (!sig.verify(Base64.decode(signature))) { Log.e(TAG, "Signature verification failed."); return false; } If I change that bit to return true instead of return false, then everything works properly -

Token that identify the user

阅读更多关于 Token that identify the user

问题 I'm developing an android application and I would like some functionality of the application is not free. I have thought to use in-app Billing Version 3 API, so I have defined an "In-App Product" in the developer console. After reading the documentation, I know that when I start the purchase flow I should pass in a string token that helps the application to uniquely identify the user who made the purchase. But how could I obtain a string token that identify the user? Thanks 回答1: you can use

In App billing not working after update - Google Store

阅读更多关于 In App billing not working after update - Google Store

I have implemented In-App billing in my app - and very recently google has updated it,previously i was testing the in-app billing with "android.test.purchased" and it was working fine (Buy full Version and Restore full version). Now i took the changed classes from here https://code.google.com/p/marketbilling/source/detail?r=7bc191a004483a1034b758e1df0bda062088d840 After that i am not able to test the app it gives the following error in the Logcat "IabHelper: In-app billing error: Purchase signature verification FAILED for sku android.test.purchased ". I have checked with my key, package name

“The item you were attempting to purchase could not be found” Android in-app billing

阅读更多关于 “The item you were attempting to purchase could not be found” Android in-app billing

I am receiving this error while testing my app. The app is signed and uploaded to the alpha testing portion of the developer console. The in-app item has the status "Active". I have entered an account other than my developer account in "testing access". I am using a device with the primary account in the "testing access" and not the developer account. I have double checked the spelling of my SKU. The exact same .apk was uploaded to Developer Console and installed on the test device. I have double checked the license key. I have waited more than 12 hours for SKU and testing accounts to be

In app billing v3 Android non-consumable items

阅读更多关于 In app billing v3 Android non-consumable items

问题 I'm starting with In App Billing and I would like to sell some magazines in my app. If one user buy one magazine he can read it always. I read about consumable and non-consumable in app billing but I didn't understand how can I make a non-consumable item and how can I manage it. I have to create a consumable item in google developer console and than specify in my app with a variable that the item is non-consumable? Thank you in advance 回答1: First, The In-app Billing Version 3 service only

Android In App Billing: securing application public key

阅读更多关于 Android In App Billing: securing application public key

From Android In App Billing version 3 (TrivialDrive)sample application coming with sdk MainActivity.java /* base64EncodedPublicKey should be YOUR APPLICATION'S PUBLIC KEY * (that you got from the Google Play developer console). This is not your * developer public key, it's the *app-specific* public key. * * Instead of just storing the entire literal string here embedded in the * program, construct the key at runtime from pieces or * use bit manipulation (for example, XOR with some other string) to hide * the actual key. The key itself is not secret information, but we don't * want to make it

Implementing In App purchases in Android?

阅读更多关于 Implementing In App purchases in Android?

Edit : Android now supports in-app billing ! Original question: It looks like Android won't natively support in-app purchases for a while, and when it does there might be a huge user base with devices that don't support them. What's the best way to implement iPhone-like (additional content or services) in-app purchases in Android using the Android Market if possible? The solution should consider in particular: For all kinds of in-app purchases: Android Market's 24-hour cancellation policy For consumables/non-consumables: storage of additional content (ie: use precious application memory to

How to implement In-App Billing in an Android application?

阅读更多关于 How to implement In-App Billing in an Android application?

It seems that it is quite complicated to implement In-App Billing in an Android app. How could I do this? The sample app from the SDK only has one Activity, which kind of over-simplifies it for an application like mine that has multiple Activities. sfratini Well, I'll try to explain what I experienced. I don't consider myself an expert on this but I broke my head several days. For starters, I had a very bad time trying to understand the workflow of the example and the application. I thought it should be better to start with a simple example however its much difficult to separate the code in