[in_app_purchase][android]: Add Google Play Offers support

[AlaaEddineCharbib]

Google Play introduced offers to subscriptions. but apparently there is still no support to this feature in the in_app_purchase plugin, or at least this is what I could conclude after going through the GooglePlayProductDetails and SkuDetailsWrapper codes.

For iOS it is possible to get the list of a product discounts using the AppStoreProductDetails' skProduct object.
is it possible to have such a thing for Android too?

[GaryQian]

cc @GaryQian

[antonionicolau]

Hey @AlaaEddineCharbib It's nice that If your app supports the in-app purchase workflow(described in Making In-app Billing requests), your app automatically supports in-app redemption of promo codes. You'll only need to implement it for IOS, not need for Android

[erperejildo]

Hey @AlaaEddineCharbib It's nice that If your app supports the in-app purchase workflow(described in Making In-app Billing requests), your app automatically supports in-app redemption of promo codes. You'll only need to implement it for IOS, not need for Android

Automatically you mean? It doesn't work for me, only takes one of the plans created:

https://stackoverflow.com/questions/74599781/flutter-get-different-plans-from-subscription

[erperejildo]

@danagbemava-nc do we know when will this be supported? Or a roadmap to know exactly how long I can delay my new subscriptions for?

I can also create other subscriptions in my google play console in the meantime and later on, when this is supported create them as plans/offers but I will encounter 2 issues here:

• The original subscriptions can't be removed at all
• The IDs will be different and I will face some problems with users with the original subscriptions
• If I have new plans/offers this will be confusing having other separate (and active) subscriptions
• Extra logic in my app

I understand we are talking about different departments here (google play console, Flutter, etc.) but this will affect our earnings and TBH all these departments belong to the same company (I'm saying this because I had these problems already in the past with this and other libraries). This issue was created 3 months ago, there are people interested but again, we have an issue without responses from the team. So some extra info will be appreciated please

[danagbemava-nc]

do we know when will this be supported? Or a roadmap to know exactly how long I can delay my new subscriptions for.

@erperejildo, unfortunately, I cannot provide that information

[seunghwanly]

It has been almost 6 months trying to get the Non-renewing Subscription from Play Store using the in_app_purchase plugin.

App Store fetches all the

1. Auto-renewable Subscriptions
2. Non-renewable Subscriptions
   by using the queryProductDetails( ) method.

But, the Play Store only retrieves Auto-renewable Subscriptions none of the Non-renewable Subscriptions can be fetched.

Are there any updates on this issue?

[erperejildo]

do we know when will this be supported? Or a roadmap to know exactly how long I can delay my new subscriptions for.

@erperejildo, unfortunately, I cannot provide that information

who should I get in contact with? Becase I was trying to create my new subscriptions but instead of creating 3 I'll have to create 6 with extra logic to detect plans within same subscriptions (because all of them will be separate and different subscriptions at the end).

I could wait to see if this is going to be supported but not much since I'm going to lose money. So any way to get more information about this support?

[seunghwanly]

In my case, I needed this feature asap, so I just replaced the deprecated method(querySkuDetailsAsync) to queryProductDetailsAsync. I had a couple of jobs like,

• created a new data model class, which covers ProductDetails
• created a new method for Dart and Java
• revised & created methods and classes in test codes, (in_app_purchase_android > test > billing_client_wrappers)
• added a separate interface called buyNonConsumableInAndroid for the new subscription model in Play Store

But, I wondered how I could handle the new class(ProductDetails in BillingClient v5) with the previous class(ProductDetails in in_app_purchase_platform_interface).

Since the Play Store announced the new model(multiple base plans inside the one-subscription, 1:N (Subscription: Base plans)), it was hard to wrap up the previous class(ProductDetails in in_app_purchase_platform_interface) with the new class(ProductDetailsWrapper).

Here is the sample code below.

/// Generate a [GooglePlayProductDetails] object based on an Android
  /// [ProductDetailsWrapper] object.
  factory GooglePlayProductDetails.fromProductDetails(
    ProductDetailsWrapper productDetails,
  ) {
    return GooglePlayProductDetails(
      id: productDetails.productId,
      title: productDetails.title,
      description: productDetails.description,
      price: productDetails.price ?? 'unknown',
      rawPrice:
          (productDetails.oneTimePurchaseOfferDetails?.priceAmountMicros ??
                  productDetails.subscriptionOfferDetails?.first.pricingPhases
                      .first.priceAmountMicros ??
                  0) /
              1000000.0,
      currencyCode:
          productDetails.oneTimePurchaseOfferDetails?.priceCurrencyCode ??
              productDetails.subscriptionOfferDetails?.first.pricingPhases.first
                  .priceCurrencyCode ??
              'USD',
      currencySymbol:
          productDetails.oneTimePurchaseOfferDetails?.formattedPrice[0] ??
              productDetails.subscriptionOfferDetails?.first.pricingPhases.first
                  .formattedPrice[0] ??
              r'$',
      productDetails: productDetails,
    );
  }

And the getter method for ProductDetailsWrapper.

String? get price =>
      oneTimePurchaseOfferDetails?.formattedPrice ??
      subscriptionOfferDetails?.first.pricingPhases.first.formattedPrice;

The reason why I set the price, rawPrice, currencyCode, etc. in this way is that I just needed to handle a single case like 👉 Subscription: Base Plan = 1: 1

Are there any ideas for this migration? Here is my repository link which I'm working on.

[wosika]

It's been six months, no support plan?😥

[sandesh-dearreal]

When should be expect this to be added?

[erperejildo]

It's been six months, no support plan?😥

When should be expect this to be added?

never wait for something like this guys. Specially if it affects your earnings

[github-actions]

This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.