in-app-billing

问题 I am going to implement managed in app billing in android I have tried a trivial sample application but when I run the app on a device it gives me error. I don't understand what I am doing wrong and why this error occurred. First display popup when I click OK than it give me error on log. Second display popup 06-23 14:37:04.912: E/Trivial Drive(19340): **** Trivial Drive Error: Error purchasing: IabResult: User canceled. (response: -1005:User cancelled) 回答1: It is simple: Google Play In-app

问题 I implemented In-app Billing (v3) according to Android's Implementing In-app Billing guide. All works fine, until I rotate the device, then immediately rotate it back to it's original orientation. Actually, sometimes it works, and sometimes it crashes with: java.lang.IllegalStateException: IabHelper was disposed of, so it cannot be used. Seems this is related to the asynchronous nature of IAB, though I'm not positive. Any thoughts? 回答1: You're probably getting the exception because somewhere

问题 I had implemented inApp purchase in my application but sometimes it gives me NPE, below is stack trace. I can post the code also if anyone interested. java.lang.RuntimeException: Unable to start service com.market.BillingService@48400380 with null: java.lang.NullPointerException at android.app.ActivityThread.handleServiceArgs(ActivityThread.java:3063) at android.app.ActivityThread.access$3600(ActivityThread.java:125) at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2096) at

问题 Please do not close this as duplicate without reading everything. Case Summary: Two google test accounts were used for IAP transactions using the same app build. One works, one doesn't. Both google accounts have working credit cards and can buy IAP from other apps. More Details: We have a new Unity-Android build released to our testers and we have 2 different google accounts for IAP testing. Surprisingly, one account can do test purchases successfully without a glitch, while the other one

问题 I've been playing around the the Dungeons app and also my own billing code and pretty much have everything working except for one strangeness. It seems that no matter what I do I can't get the DEVELOPER_PAYLOAD to show up in the JSON signed response. If I'm reading thing right, the docs seem to say that I should see the developer_payload in the JSON market response. The Dungeons app seems to think it should see the developer_payload in the json too. I haven't gotten it to work in my code and

问题 in a nutshell: Can I work with the Google Play Android Developer API from server-side without providing any app in the play store? Background: I'm working on a project which provides apps with monthly subscriptions. The coresponding data of each subscription (purchase token, date etc) gets stored in the backend database. Now I want to create a cronjob that iterates through each of these datasets.And for each subscription I'd like to contact the Google API to retrieve the information if the

问题 I have setup In-App Billing for the first time using the new v3 API. It is working correctly on my devices but I have received a lot of error reports from other users. One of them is: java.lang.IllegalStateException: IAB helper is not set up. Can't perform operation: queryInventory at my.package.util.iab.IabHelper.checkSetupDone(IabHelper.java:673) at my.package.util.iab.IabHelper.queryInventory(IabHelper.java:462) at my.package.util.iab.IabHelper$2.run(IabHelper.java:521) at java.lang.Thread

问题 I am making an In-app purchase test with test account but the response from google is same as the purchase made from real account. How to check if the purchase is test based on the response from google? 回答1: Yes, you can check that from the purchaseType field of the Google's Purchases.subscriptions API response refer. Field : purchaseType Type : integer Description : The type of purchase of the subscription. This field is only set if this purchase was not made using the standard in-app

问题 Now I managed to sign the apk (using Eclipse Android Tools) and adb install .. to the device for testing. But this removed the debug function, e.g. "step over" which make problem tracing much more difficult. Is it possible to debug the inapp billing using Eclipse? 回答1: When you go through the in app billing documentation, you kinda realize that it can take substantial amount of time to understand this complex piece of technology. Most developers feel the need for a working HelloWorld, and

问题 We're having problems verifying some of payment transactions (Google In App Billing V3). It looks like data of cumbersome transactions follows a different format than what we can see in transactions we have no problems verifying. Transactions that we are able to verify OrderId : Two numbers separated with a dot: 92299713162054702728.1224255970239541 Signature : Always includes base64 padding at the end, 345 characters long Transactions that fail to verify OrderId : One number: