Android: Google Play in-app purchase offer not working with Paywall

[sdsantos]

• I have updated Purchases SDK to the latest version
• I have read the Contribution Guidelines
• I have searched the Community
• I have read docs.revenuecat.com
• I have searched for existing Github issues

Describe the bug

• On Google Play, I have a non-consumable in-app purchase (premium) with a "Discounted offer" named half-price
• I have a Paywall with a single package, with a Promotional Offer for Play Store with half-price
• When showing the paywall, both in debug and release, it fails to apply the discounted offer, and falls back to the default price without it.

These are the relevant logs I can find:

I  ℹ️ Missing productDetails: UnfetchedProduct{productId='premium', productType='subs', statusCode=3}
I  ℹ️ Product not found: premium - Product Type: subs, Reason: PRODUCT_NOT_FOUND, Serialized doc ID: 
W  Configured offer 'half-price' for package '$rc_lifetime': product has no subscription options. Falling back to default option.
W  Could not process value for variable 'product.relative_discount' for package '$rc_lifetime'. Please check that the product for that package matches the requirements for that variable. Defaulting to empty string.

1. Environment
   1. Platform: Android
   2. SDK version: 10.3.1
   3. OS version: Android 12
   4. Android Studio version: 2025.3.4
   5. How widespread is the issue: 100%
2. Debug logs that reproduce the issue: see above
3. Steps to reproduce, with a description of expected vs. actual behavior: see above
4. Other information (e.g. stacktraces, related issues, suggestions how to fix, links for us to have context, eg. stackoverflow, etc.)

Additional context

If I run Purchases.sharedInstance.awaitGetProducts(listOf("premium"), ProductType.INAPP) I can see the offer fine.

[fire-at-will]

Hi @sdsantos, thanks for reporting!

What exactly do you see when you run Purchases.sharedInstance.awaitGetProducts(listOf("premium"), ProductType.INAPP)?

[sdsantos]

Hi @sdsantos, thanks for reporting!

What exactly do you see when you run Purchases.sharedInstance.awaitGetProducts(listOf("premium"), ProductType.INAPP)?

[GoogleStoreProduct(productId=premium, basePlanId=null, type=INAPP, price=Price(formatted=€5.99, amountMicros=5990000, currencyCode=EUR), name=Premium, title=Premium (...), description=..., period=null, subscriptionOptions=null, defaultOption=null, productDetails=ProductDetails{jsonString='{"productId":"premium","type":"inapp","title":"Premium (...)","name":"Premium","description":"...","localizedIn":["en-US"],"skuDetailsToken":"xxx=","oneTimePurchaseOfferDetails":{},"oneTimePurchaseOfferDetailsList":[{"priceAmountMicros":5990000,"priceCurrencyCode":"EUR","formattedPrice":"€5.99","offerIdToken":"xxx==","purchaseOptionId":"legacy-base","offerTags":[]},{"priceAmountMicros":2990000,"priceCurrencyCode":"EUR","formattedPrice":"€2.99","offerIdToken":"xxx","offerId":"half-price","purchaseOptionId":"legacy-base","offerTags":[],"discountDisplayInfo":{"percentageDiscount":50},"fullPriceMicros":5990000,"validTimeWindow":{"startTimeMillis":1763665200000}}]}', parsedJson={"productId":"premium","type":"inapp","title":"Premium (xxx)","name":"Premium","description":"xxxx","localizedIn":["en-US"],"skuDetailsToken":"xxxx=","oneTimePurchaseOfferDetails":{},"oneTimePurchaseOfferDetailsList":[{"priceAmountMicros":5990000,"priceCurrencyCode":"EUR","formattedPrice":"€5.99","offerIdToken":"xxxx==","purchaseOptionId":"legacy-base","offerTags":[]},{"priceAmountMicros":2990000,"priceCurrencyCode":"EUR","formattedPrice":"€2.99","offerIdToken":"xxx","offerId":"half-price","purchaseOptionId":"legacy-base","offerTags":[],"discountDisplayInfo":{"percentageDiscount":50},"fullPriceMicros":5990000,"validTimeWindow":{"startTimeMillis":1763665200000}}]}, productId='premium', productType='inapp', title='Premium (...)', productDetailsToken='xxx=', subscriptionOfferDetails=null}, presentedOfferingIdentifier=null, presentedOfferingContext=null)]

[bilqisium]

Hey @sdsantos,

Unfortunately, Google Play's Discounted offers on non-consumable in-app purchases aren't currently supported by our Paywalls on Android.

The Promotional Offer for Play Store field is built for subscription base-plan offers, so for an INAPP product like premium it can't resolve half-price and falls back to the default price. Our docs currently scope it to subscriptions.

The log lines show that the SDK is attempting to match this product as a subscription, not INAPP.

The workaround I can suggest for now is to model the discounted price as a separate IAP (e.g. premium_half_price at €2.99) and switch to it via a second paywall or Targeting rule.

In the meantime, I'm asking internally whether we are planning on supporting for this.

[sdsantos]

Hey @sdsantos,

Unfortunately, Google Play's Discounted offers on non-consumable in-app purchases aren't currently supported by our Paywalls on Android.

The Promotional Offer for Play Store field is built for subscription base-plan offers, so for an INAPP product like premium it can't resolve half-price and falls back to the default price. Our docs currently scope it to subscriptions.

The log lines show that the SDK is attempting to match this product as a subscription, not INAPP.

The workaround I can suggest for now is to model the discounted price as a separate IAP (e.g. premium_half_price at €2.99) and switch to it via a second paywall or Targeting rule.

In the meantime, I'm asking internally whether we are planning on supporting for this.

I guess nothing clearly stated that offers for in-app purchases were supported, but I also didn't find anything stating otherwise. And it felt like something obvious. It's an offer-id, just like for subscriptions.

If I understand correctly, your suggestion only allows us to show the lower price, like an offer has been applied, right? But the difference when an offer is applied, is that the user sees the discount (not just the lower price) in the purchase Google Play dialog. That's one the things we're looking for when using offers.

[bilqisium]

If I understand correctly, your suggestion only allows us to show the lower price, like an offer has been applied, right? But the difference when an offer is applied, is that the user sees the discount (not just the lower price) in the purchase Google Play dialog. That's one the things we're looking for when using offers.

The workaround I suggested can be used to show both prices and the discount. You could for instance inject the prices using custom variables, and even conditionally show it using rules (with custom variables).

[arnabJ]

@bilqisium I understand we have workarounds to show a discounted pricing. But, they are counter-intuitive. Require a lot of work on the developer's end and may even require an app update in certain scenarios. Also it creates a nightmare situation were all possible entitlements need to be maintained and checked in all future versions of the app to determine if the user has any applicable plan purchased. Say, for example, in my app I would have to check both, "premium" and "premium_half_price", entitlements. If any user has any of the plans purchased, they are eligible for the premium features. If, in future, I release another offer say "premium_new_year_2027", I will have to check that for the lifetime of my app as well.

In my app I offer multiple One time Purchase Items to give user's the choice to pay for only the features they need. If I wan to release offers for each item the workaround is little to no help for me.

It shouldn't be up for question whether RevenueCat will support a feature/option from Google Play or not. The only question which should come up is how fast can it bring it to it's users after a feature is released or updated. 7+ months is definitely late. Personally I believe RevenueCat's position doesn't gives it the option to choose what features it will support as the developers dependent on it can't mix and merge feature via its SDK and natively without risk of issues and instability.

Even the new Chargebacks refund policy needs to be implemented at the earliest otherwise it will adversely effect developers.

I hope I was able to point out my views without offending you or anyone from the team. RevenueCat is quite useful but with features missing may lead developers to move away from them if they have to choose between the benefits RevenueCat provides and the latest features Google Play introduced and requires to be implemented.