in-app-billing

My [UNMANAGED] in-app purchase won't work, Before it works perfectly which I can purchase successfully using Test Accounts. But it suddenly won't work, as I remember what I did to Merchant Account is only add more 2-4 Test Accounts. Then after adding, my in-app purchase won't work. So I updated the public key and upload an Apk as draft. But still won't work. When the app is in google play page I received a LogCat error: 11-20 17:00:18.840: E/Finsky(2182): [187] FileBasedKeyValueStore.delete: Attempt to delete 'paramsqE9ZgJf5Z6GeZu1wwGPosw' failed! Then when I click the Buy & Accept button I

I'm trying to add in-app purchase for my existing published app that didn't previously have billing permission. I've uploaded an updated APK with billing permission, but didn't activate it since I don't want to publish this draft. However, I can't add in-app product - it still says "the current application version does not use the BILLING permission". Any way to solve/work around this problem? Change Android version code in Androidmanifest.xml file. android:versionCode="1" suppose if your Application version code is 1 now change to 2 来源： https://stackoverflow.com/questions/14068781/adding-in

When there is an auto-renewing subscription, consider the following model situation: user buys 1 month subscription, lets say in January cancels renewal then waits until March (>1 month) and buys same subscription again Does the AppStore return (on receipt verification) a new original_transaction_id for the new purchase? Or rephrased, can original_transaction_id be used for grouping receipts to determine intervals when user had active subscription? Because in sandbox, when there is a simulated situation like this, it returns always original_transaction_id from the FIRST purchase of given

I currently have two versions of my app in the Android market, a paid one and a free one. But I want to integrate in-app billing into my free application, and charge customers on a subscription base, for a lower price than the current price of the paid app. But how should I handle this for existing customers? It seems unfair to let them pay again for use of the paid functionality, while they were the early adopters of my application. Ideally I implement something that will give the existing users access to the unlocked functionality in my free application. Any ideas of how to accomplish this?

I have developed an Android app which I want to be available both as free and paid version. What is the best approach? I can think of three solutions: Split the project into two branches and maintain both of them. Create a library project and have two additional projects, one 'Free' and one 'Paid' version. Use in-app billing. Q: Which solution is the best? And why? Some things to consider: My app is around 1.5 MB (AdMob excluded). I'm currently targeting Android 2.2 (Froyo). I do have some server APIs that would benefit from knowing if the client is paid or not. I seek to avoid my app being

Hi am using new Play Billing Library for in app subscriptions. https://developer.android.com/google/play/billing/billing_library.html Everthing works perfect and am able to subscribe the product. But i didn't find any ways to check the purchase state of subscription. I mean whether it is active or expired. In the documentation it says : You can then call a variety of methods on the Purchase object to view relevant information about the item, such as its purchase state or time. But there is no purchase state method in Purchase Object, check link below https://developer.android.com/reference/com

Our beta app uses android.test.purchased so customers can test for free. But recently something broke with consuming these test products. The purchase process still works fine but when we try to consume: int response = ms.consumePurchase(3, mContext.getPackageName(), token); This now always returns RESULT_DEVELOPER_ERROR == 5 . The data passed appears valid, token is inapp:com.lootworks.swords:android.test.purchased which I think is correct for the static test products. Simultaneously all our earlier app versions also stopped working and we did not change our code, so it sure seems like

I've been struggling with Android IAB v3 for a while now. I have it working consistently on my test devices. However, my crash reporting service shows two recurring crashes: one for null pointer exception and one for illegal state exception. I've tried updating the Google sample code w/ numerous suggestions from Stackoverflow users facing similar problems. I've gone through the "read crash reports, do research, attempt to fix crashes, submit update, see same crash reports again" cycle a few times. I think it's time for a different approach. If you were starting with Android IAB today, what

YES, I've read all the docs @ developer.android.com and I do understand it all with one basic exception - what it was introduced for. Since all order responses from Google Play come signed by inaccessible-by-anyone private key and are being verified by paired public key (in my case on external server, so it is also inaccessible for third person) there's simply (almost) no way to spoof. All those nonces are just redundant way of securing the purchases. And what's more, the docs say nothing about the situation, when: I purchase an item; Generate nonce and send it to Google Play; Have a crash, so