in-app-billing

Android In App BIlling v3 - Wrong Subscription Trial Period

≡放荡痞女 提交于 2019-12-01 06:40:36
问题 I am using the Android In App BIlling v3 library, and when I call bp.subscribe(Activity, subscriptionID) I get the Google Play purchase window, but the biling period is always 'per day', and the trial period is always '1 day'. I have configured my subscription to have: Billing Period: Yearly Free Trial Period: 15 days Default Price: $12 Using the above configuration, my App shows the purchase details as: 1 day trial $12.00 / day Library documentation says nothing. Tried to Google it, can't

Google IAP verification has failed for many purchases

依然范特西╮ 提交于 2019-12-01 06:19:00
问题 I'm using Google IAP v3 in Android app. I've implemented signature checking using GoogleIabHelper class. I'm also checking the signature on the server side with almost the same code. In the server logs I've found a lot purchases are invalid. Here are example data for 2 valid purchases and one invalid: Valid purchases #1 orderId: 12399363269014736759.1358132323863451 purchaseTime: 1416079768157 purchaseToken: olcgkklnpigiceancikanedj.AO-J1O... dataSignature matches: yes response from

android: in app billing RESULT_SERVICE_UNAVAILABLE

有些话、适合烂在心里 提交于 2019-12-01 06:16:30
I got this kind of error from last night..i dont't know what's going on.Is there any problem from my side?. I didn't change my code but when i clear data or i restall the application it shows me like....!!!!!! frustrating........ 05-05 04:18:16.000: E/Finsky(17538): [1] NotifyingErrorListener.onErrorResponse: Server error on InAppPurchaseInformationRequest: com.android.volley.ServerError 05-05 04:18:16.010: D/Finsky(17538): [1] MarketBillingService.sendResponseCode: Sending response RESULT_SERVICE_UNAVAILABLE for request 227869xxxxxxx6110 to com.mypackage. MarketBillingService.sendResponseCode

Protection from Freedom

随声附和 提交于 2019-12-01 06:01:16
Just tried the Freedom app on our application and I could bought every in app purchase item with it. At least when running the Play Store 3.x. If I upgraded the play store to 4.x than the Freedom hack stopped working. Anyhow, is there a way to protect against it? Check the orderId returned. Correct orderIDs are of the form: [merchant ID].[actual order ID] Find your merchant ID in your Wallet account (last line on order page) and check in your app if it's the same. As the Freedom hack cannot by any means know your Wallet ID, the returned ID of hacked payments differs. Just refuse those payments

How to resolve “The item you were attempting to purchase could not be found”

无人久伴 提交于 2019-12-01 05:44:40
I´m testing my in-app billing and followed the following steps: Uploaded APK to the Market, created In-App items and published them (did not publish the app itself), exported a signed APK and installed that on a different device then my own (so there is a different primary account), but when I click on the button to purchase an item, it shows the itemname in a different view, but after a loading widget it gives the error: How to resolve “The item you were attempting to purchase could not be found I couldn´t find the solution on stackoverflow, can anyone give me more ideas? Thanks ricvieira If

android: in app billing RESULT_SERVICE_UNAVAILABLE

落爺英雄遲暮 提交于 2019-12-01 04:40:17
问题 I got this kind of error from last night..i dont't know what's going on.Is there any problem from my side?. I didn't change my code but when i clear data or i restall the application it shows me like....!!!!!! frustrating........ 05-05 04:18:16.000: E/Finsky(17538): [1] NotifyingErrorListener.onErrorResponse: Server error on InAppPurchaseInformationRequest: com.android.volley.ServerError 05-05 04:18:16.010: D/Finsky(17538): [1] MarketBillingService.sendResponseCode: Sending response RESULT

How to resolve “The item you were attempting to purchase could not be found”

[亡魂溺海] 提交于 2019-12-01 03:54:20
问题 I´m testing my in-app billing and followed the following steps: Uploaded APK to the Market, created In-App items and published them (did not publish the app itself), exported a signed APK and installed that on a different device then my own (so there is a different primary account), but when I click on the button to purchase an item, it shows the itemname in a different view, but after a loading widget it gives the error: How to resolve “The item you were attempting to purchase could not be

Google Play Developer API: “startTimeMillis” is updated when it should not

倾然丶 夕夏残阳落幕 提交于 2019-12-01 03:48:33
I am developing an application with in-app subscriptions. On our servers, I check the validity of each subscription through the Google Play Developer API . As stated in the docs, a request to the Purchases.subscriptions endpoint, returns something like that: { "kind": "androidpublisher#subscriptionPurchase", "startTimeMillis": long, "expiryTimeMillis": long, "autoRenewing": boolean } However, I am finding some strange behavior with it. When a user cancels a subscription through Google Play app, the "startTimeMillis" field is updated to the time of cancellation . According to the documentation,

In App Billing v3 IllegalArgumentException using IabHelper

好久不见. 提交于 2019-12-01 03:38:38
I've had in app billing v3 implemented in my app for about a week now. I used a lot of android's sample code to simplify the integration. I've been logging a crash fairly often that I can't seem to reproduce: Exception Type: java.lang.RuntimeException Reason: Unable to destroy activity {[package].billing.BillingActivity}: java.lang.IllegalArgumentException: Service not registered: [package].billing.util.IabHelper$1@40646a70 It seems to be breaking on this line: if (mContext != null) mContext.unbindService(mServiceConn); I'm binding this service in my onCreate method and disposing it in my

Making in-app purchases with an google play account different from the device primary account

浪尽此生 提交于 2019-12-01 03:38:25
Sorry if the title sound confusing. I hope that I can explain better here. We know that each device can have multiple google account of which the first created google account in the device will be the primary account. In google play app, user can actually select different google account to sign in to Google Play store on the device. If for example, the device primary account is myprimary@gmail.com and the user sign in to Google Play app with "anotheraccount@gmail.com". The user then made an in-app purchase. The question is, will the user still be able to received the purchased item? Does