Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bump package_info_plus to 4.0.0 #13

Open
Willian199 opened this issue May 12, 2023 · 1 comment
Open

Bump package_info_plus to 4.0.0 #13

Willian199 opened this issue May 12, 2023 · 1 comment

Comments

@Willian199
Copy link

After upgrading flutter to 3.10 and device_info_plus to 9.0.0;

It started showing an error when running flutter pub get.

Error:

Because package_info_plus >=1.4.1 <1.4.3 depends on package_info_plus_windows ^1.0.5 which depends on win32 ^2.0.0, package_info_plus >=1.4.1 <1.4.3 requires win32 ^2.0.0.

And because package_info_plus ^1.4.3 depends on package_info_plus_windows ^2.0.0, package_info_plus ^1.4.1 requires win32 ^2.0.0 or package_info_plus_windows ^2.0.0.

Because package_info_plus_windows >=2.1.0 depends on win32 >=2.7.0 <4.0.0 and package_info_plus_windows >=2.0.0 <2.1.0 depends on win32 ^2.7.0, package_info_plus_windows >=2.0.0 requires win32 >=2.7.0 <4.0.0.

Thus, package_info_plus ^1.4.1 requires win32 >=2.0.0 <4.0.0.
And because flutter_app_version_checker >=0.3.1 depends on package_info_plus ^1.4.2, flutter_app_version_checker >=0.3.1 requires win32 >=2.0.0 <4.0.0.

And because device_info_plus 9.0.0 depends on win32 ^4.1.4 and no versions of device_info_plus match >9.0.0 <10.0.0, flutter_app_version_checker >=0.3.1 is incompatible with device_info_plus ^9.0.0.
So, because s1mobile depends on both device_info_plus ^9.0.0 and flutter_app_version_checker ^0.3.2, version solving failed.
@lukehutch
Copy link

The latest version of package_info_plus is currently 8.0.0... same issue again

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants