[in_app_purchase] users don't get the trial period offer after upgrading to a new version

[mikron123]

Steps to reproduce

On Android, the subscription process is charging the users instead of offering the only offer (3 days free trial) like it used to be.

I didn't find any documentation or a hint in the change logs, is it a bug or a syntax change?

Expected results

Subscription offer has to be offered immediately

Actual results

on purchase, the user is being charged without suggesting the offer.

[darshankawar]

@top2429 Please don't mix issues. File a new issue with all requested details so that we can track and address it properly.

[darshankawar]

@mikron123
Can you provide flutter doctor -v, previous plugin in which it worked as usual and the version you upgraded to in which you are seeing the reported error ? Also, please provide us reproducible code sample.

[mikron123]

@mikron123 Can you provide flutter doctor -v, previous plugin in which it worked as usual and the version you upgraded to in which you are seeing the reported error ? Also, please provide us reproducible code sample.

I do not see any error, that's the thing. It just doesn't offer the 3 days trial, and the subscription on the Google Play Console hasn't changed at all. As well as the in app purchase code on my end: _connection.buyNonConsumable(purchaseParam: purchaseParam);

I upgraded from version 3.0.8 to 3.1.13

EDIT: I just checked it going back to 3.0.8 - it shows the offer in the IAP dialog, 3.1.13 doesn't. Is it a known issue which was fixed later on?

EDIT 2: 3.2.0 (latest) gives the same result - no trial offer indication. Has the API changed?

[mikron123]

To narrow it down - version 3.1.5 offers the trial, >= 3.1.6 ignores the trial offer. Is there a code syntax made to select the offer alongside the purchase? The example doesn't reflect it, nor does the purchase code.

[darshankawar]

Can you upgrade to latest version and re-run your scenario to check if it persists still or not ? There have been few updates for Android as I see from changelog.

[mikron123]

Can you upgrade to latest version and re-run your scenario to check if it persists still or not ? There have been few updates for Android as I see from changelog.

Version 3.2.0 - Same result. As said, I went over all the versions in between, simply changing the version and then running - it started on 3.1.6

[darshankawar]

This seems to be similar to #143514 in which you have already commented, so I suggest you to follow-up in it for further updates. Closing this as a duplicate. If you disagree, write in comments and I'll reopen it.