in-app-billing

问题 I understand that google does not allow the transfer of app ownership with in app-subscription from one developer account to another. I have been waiting for them to enable that feature but till now, it is not available and there is no ETA on it. I have a paid app with in-app-subscription as part of it. A company is looking to acquire my app but the transfer is not possible. So I am thinking about alternatives. Should I create another identifcal app and ask users in my old app to move to this

问题 I want to publish an Android app with 7 days as trial period. Currently I have developed an app but I need some guidance. I have very little experience and cannot seem to find any useful documentation about implementing a free trial period, so any help would be much appreciated. 回答1: In-app purchase does not support the case of a trial directly because the in-app billing is a simple one-time purchase model. Your trial of the full-features, entirely within your own code. Specifically you'll

问题 I'm attempting to implement the new inapp billing implementation as the trivial drive 2 implementation appears to have dropped support. The following code to create my mSkuDetails map gives me an odd method clash error. It's copied right from the docs except for the Map insertion line. List<String> skuList = new ArrayList<> (); skuList.add("item1"); skuList.add("item2"); SkuDetailsParams.Builder params = SkuDetailsParams.newBuilder(); params.setSkusList(skuList).setType(BillingClient.SkuType

问题 I'm attempting to implement the new inapp billing implementation as the trivial drive 2 implementation appears to have dropped support. The following code to create my mSkuDetails map gives me an odd method clash error. It's copied right from the docs except for the Map insertion line. List<String> skuList = new ArrayList<> (); skuList.add("item1"); skuList.add("item2"); SkuDetailsParams.Builder params = SkuDetailsParams.newBuilder(); params.setSkusList(skuList).setType(BillingClient.SkuType

问题 I am using android InAppBilling to purchase the products in my Application. I'm following the documentation on https://developer.android.com/google/play/billing/billing_integrate.html According to the documentation we can buy only one product at a time. Bundle buyIntentBundle = mService.getBuyIntent(3, getPackageName(), sku, "inapp", "bGoa+V7g/yqDXvKRqq+JTFn4uQZbPiQJo4pf9RzJ"); But in my android application, i have an option to buy All In-App-Purchases . So my question is how can i implement

问题 I am using android InAppBilling to purchase the products in my Application. I'm following the documentation on https://developer.android.com/google/play/billing/billing_integrate.html According to the documentation we can buy only one product at a time. Bundle buyIntentBundle = mService.getBuyIntent(3, getPackageName(), sku, "inapp", "bGoa+V7g/yqDXvKRqq+JTFn4uQZbPiQJo4pf9RzJ"); But in my android application, i have an option to buy All In-App-Purchases . So my question is how can i implement

问题 I am facing an issue after installing and implementing in-app purchase plugin Flutter team provided. What I did so far: added 2 products on Play Store that are visible and active. submitted build for alpha testing, since that is required for in-app purchase to work. added InAppPurchaseConnection.enablePendingPurchases(); at the app launch created a sequence of requests to the app store out of which last one fails with nasty log I can't work around bool available = await _iap.isAvailable(); if

问题 I am facing an issue after installing and implementing in-app purchase plugin Flutter team provided. What I did so far: added 2 products on Play Store that are visible and active. submitted build for alpha testing, since that is required for in-app purchase to work. added InAppPurchaseConnection.enablePendingPurchases(); at the app launch created a sequence of requests to the app store out of which last one fails with nasty log I can't work around bool available = await _iap.isAvailable(); if

问题 Which states on onBillingSetupFinished should I handle? What I mean is, there are 12 possible states on the BillingResponseCode interface: int SERVICE_TIMEOUT = -3; int FEATURE_NOT_SUPPORTED = -2; int SERVICE_DISCONNECTED = -1; int OK = 0; int USER_CANCELED = 1; int SERVICE_UNAVAILABLE = 2; int BILLING_UNAVAILABLE = 3; int ITEM_UNAVAILABLE = 4; int DEVELOPER_ERROR = 5; int ERROR = 6; int ITEM_ALREADY_OWNED = 7; int ITEM_NOT_OWNED = 8; But I imagine only a few of them are really send to this

问题 I'm developing an app that contains In App Billing non consumable product (Life time Subscription). User has one email associated with Play Store on his device. Scenario: User A create new account using user1@test.com and purchase Lifetime Subscription and logout. User B create new account using user2@test.com and trying to purchase. but he get response BillingClient.BillingResponse.ITEM_ALREADY_OWNED . How do i differ each user to buy item? I'm using 'com.android.billingclient:billing:2.2.1'