in-app-billing | 易学教程

IllegalStateException in IAB V3

阅读更多关于 IllegalStateException in IAB V3

I am trying to impliment android in app billing v3 and my application crashes with the following error Can't start async operation (consume) because another async operation(consume) is in progress Stack trace is given below 02-25 16:56:54.811: E/AndroidRuntime(6913): FATAL EXCEPTION: main 02-25 16:56:54.811: E/AndroidRuntime(6913): java.lang.IllegalStateException: Can't start async operation (consume) because another async operation(consume) is in progress. 02-25 16:56:54.811: E/AndroidRuntime(6913): at com.seven.BillingHelper.IabHelper.flagStartAsync(IabHelper.java:711) 02-25 16:56:54.811: E

How to convert openssl_pkey_get_public and openssl_verify to C

阅读更多关于 How to convert openssl_pkey_get_public and openssl_verify to C

Now I'm looking for a way to verify the signature from 'Google inapp billing' system. I've found 'openssl_pkey_get_public' and 'openssl_verify' functions in php(it is very easy and simple!!), but no example or document for C or C++;;;(I spend last two days for searching it..OTL...) now I have : - public key - signature - purchase data from google I want to implement verifying code using C or C++ Is there someone who knows how I can get it? I've searched belows.. - http://www.nlnetlabs.nl/downloads/publications/hsm/hsm_node21.html It deals with 'openssl EVP'..but it tells about HSM(hardware

How to migrate from a paid android application to an application paid for with in-app billing?

阅读更多关于 How to migrate from a paid android application to an application paid for with in-app billing?

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

How to check purchase state of subscription in all new Play Billing Library?

阅读更多关于 How to check purchase state of subscription in all new Play Billing Library?

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

Consistent secure Google Play in-app purchase scenario with own web server

阅读更多关于 Consistent secure Google Play in-app purchase scenario with own web server

问题 I've read several times all the docs in the Android Developer Guide and became familiar with nice Google presentation Evading Pirates and Stopping Vampires Finally I tried to implement in-app billing scenario involving my own web server in accordance to the presentation above. Here are the main points of interaction with my server: Before making REQUEST_PURCHASE request to Google I make a request to my web server to register a new purchase. If the request succeeds I get a nonce from the

Invalid expire date after subscription purchase

阅读更多关于 Invalid expire date after subscription purchase

i've got an android app with in-app subscriptions. After the user has purchased a subscription, i request the "validUntilTimestampMsec" and "initiationTimestampMsec" through our backend by the Google API. The returning timestamp "initiationTimestamp" is correct and represents the time the user has made the purchase, but the returning timestamp "validUntilTimestamp" has always a difference of +12 hours to the real valid-until time i need. The function i use to retrieve the date is simmilar to both timestamps. Where does the 12 hours come from and how can i get the correct time. The expire date

Can't re-buy in-app billing item on Google Play after it was refunded

阅读更多关于 Can't re-buy in-app billing item on Google Play after it was refunded

I implemented in-app billing into my app and am now testing its handling of refunds. I bought my app's managed in-app billing item with a test account and refunded it. My app got the refund broadcast as expected and it sees that the item was refunded when restoring transactions, so everything is good up to that point. My problem is that I can't re-buy the item to test other scenarios. When I try to purchase the item, the Google Play interface comes up and displays an error message saying "You already own this item." with 2 buttons "OK" and "Details". If I press details, Google Play crashes and

Android InApp Billing - what are really nonces for?

阅读更多关于 Android InApp Billing - what are really nonces for?

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

How to test In App Subscription in android

阅读更多关于 How to test In App Subscription in android

问题 I've integrated In app purchase api(v3) in my existing app successfully. I've also created in app subscription in google play and added subscription id in code. In Google developer website i've read that to test in app purchase we need to add email id's in Settings section. So i've added test email id's there and saved it(please see the attached image). Then i've purchased the subscription successfully but money got deducted from my google wallet account. Is there any thing that i missed to

In-App Billing: Inventory not correct; makes user purchase again

阅读更多关于 In-App Billing: Inventory not correct; makes user purchase again

Edit*** still looking for an answer to my original question. Why won't Android see the item has been bought previously instead of making the user pay again? Setting SharedPreferences is an OK idea, but what if the user uninstalls? They would have to buy again. I do not want this for the users. Thank you. I tried to figure out why the app does not inventory correctly, I took this from TrivialDrive and tried to make it my own. I believe I removed all the consume and I only have one item to purchase; a premium upgrade. This should be bought only once and never charged twice. When I compile and