displayPrice returns "0" or "Free" when a 7-day Free Trial is active; unable to easily retrieve the base recurring price.

[aryan-xentrixlabs]

I am using flutter_inapp_purchase to display 16 different subscription plans. Each plan includes a 7-day free trial configured in both Google Play Console and App Store Connect. Currently, when fetching products, the displayPrice returns 0 or Free.

Users need to see the actual price they will be charged after the 7-day trial ends (e.g., "7 days free, then ₹999/month"). However, the plugin does not provide a unified way to get the base/original recurring price without complex manual parsing of native sub-objects.

Steps to Reproduce:

Configure a subscription product in Play Console/App Store Connect with a 7-day free trial.

Fetch the product details using getProducts().

Observe the value of product.displayPrice.

Expected Behavior: There should be a consistent property (like basePrice or recurringPrice) that returns the price of the subscription after the introductory period ends, regardless of whether a free trial is active.

Actual Behavior:

Android: displayPrice returns "Free". To get the real price, one must loop through subscriptionOfferDetailsAndroid -> pricingPhases -> pricingPhaseList and filter by recurrenceMode.

iOS: displayPrice returns "Free". The actual price is hidden inside introductoryPrice logic or requires manual formatting of the price double and currency.

[hyochan]

Thanks for the detailed report — I’ll double-check how we’re mapping displayPrice for subs with free trials across Android/iOS and whether we can expose something like a unified recurringPrice / basePrice (price after the intro period) in a consistent way.

Meanwhile, if your main goal is reliably showing “7 days free, then ₹999/month” without digging through the platform-specific sub-objects, you may want to consider using backend/provider validation to fetch normalized subscription metadata (including the post-trial recurring price) in a more consistent format.

In particular, verifyPurchaseWithProvider can make this easier because the provider response typically includes the normalized pricing/period information you need for UI, without you having to manually parse subscriptionOfferDetailsAndroid.pricingPhases or iOS introductory pricing formatting:

https://hyochan.github.io/flutter_inapp_purchase/api/core-methods?_highlight=verifypurchasewi#verifypurchasewithprovider

[hyochan]

@aryan-xentrixlabs Introduced fix in http://openiap.dev/docs/updates/notes#gql-1-3-14-google-1-3-25-apple-1-3-12. Will update the library either

[hyochan]

Done https://github.com/hyochan/flutter_inapp_purchase/releases/tag/8.2.2