Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

@giorgio79 Is this version bump required? Could a user not just call pub upgrade to pull the latest version of the dependency?

Are you submitting the app after building it with the latest in_app_purchase_android version? If so, this version bump won't solve that problem. Your pubspec.lock should tell you which version you're using.

Summarizing from offline discussion: we generally don't require updates to transitive dependencies, but there's something of a special case here since updating the Android implementation package is necessary. Enough people who don't run flutter pub upgrade are getting confused about this that bumping to 0.2.3 (not +5) would be reasonable here.

it seems a simple pub upgrade won't do

Are you sure you ran flutter pub upgrade, not flutter pub get? You should only still be using the old version of the implementation package if you did the latter.

I haven't had in_app_purchase_android in my pubspec list as the plain in_app_purchase package https://github.com/flutter/plugins/blob/main/packages/in_app_purchase/in_app_purchase/pubspec.yaml includes it in the pubspec.yaml, but an older version!

I always run flutter pub upgrade when I edit the codebase, so everything was up to date. You need to have in_app_purchase_android in the pubspec to resolve this issue, which I did now, and the alert is gone, but the only reason I installed in_app_purchase_android separately is to make this issue go away.

I haven't had in_app_purchase_android in my pubspec

That is normal. flutter pub upgrade updates transitive dependencies as well.

in_app_purchase package includes it in the pubspec.yaml, but an older version!

That's a minimum range constraint, not a pinned version. It will resolve to the latest version less than 0.3.0, which includes 0.2.3+5.

I always run flutter pub upgrade when I edit the codebase, so everything was up to date.

If you still have the version where you saw this in version control, please file an issue and provide the output of flutter pub outdated and flutter pub upgrade when run against that version. If running upgrade didn't update your transitive dependencies that's a bug.

You need to have in_app_purchase_android in the pubspec to resolve this issue

This should not be the case.

closing in favor of #6595