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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Please consider upgrade the dependencies to the latest Dart 3 / File 7.0 #417

Open
MagnusJohansson opened this issue May 28, 2023 · 10 comments

Comments

@MagnusJohansson
Copy link

馃彈 Enhancement Proposal

Since the package file is now at v7.0.0 , to be Dart3 compliant, it would nice if flutter_cache_manager also upgrades its dependencies to include file version 7.0.0

Resolving dependencies...
Because no versions of cached_network_image match >3.2.3 <4.0.0 and cached_network_image 3.2.3 depends on flutter_cache_manager ^3.3.0, cached_network_image ^3.2.3 requires flutter_cache_manager ^3.3.0.
Because flutter_cache_manager 3.3.0 depends on file ^6.0.0 and no versions of flutter_cache_manager match >3.3.0 <4.0.0, flutter_cache_manager ^3.3.0 requires file ^6.0.0.
Thus, cached_network_image ^3.2.3 requires file ^6.0.0.
So, because my_app depends on both cached_network_image ^3.2.3 and file ^7.0.0, version solving failed.

Pitch

Pitch? Well, if this package is intended to be relevant in the near future , it would behove the maintainers to keep up to date.

Platforms affected (mark all that apply)

  • [ x] 馃摫 iOS
  • [ x] 馃 Android
@MagnusJohansson
Copy link
Author

... I see there's already a PR for #414

@clintonrocksmith
Copy link

Yes this is important for us @renefloor

Is there anything we can do to get the release rolled out?

Thanks mate

@clintonrocksmith
Copy link

FYI, I emailed them using their company form on their website

@WongResearch
Copy link

I second what @clintonrocksmith said - this is important. Would be great if this can be looked at. Thank you in advance @renefloor

@hadoudait
Copy link

any updates on this?

@Carapacik
Copy link
Contributor

@mateusfccp
Copy link

mateusfccp commented Jul 3, 2023

Although the changelog says that the new version supports file: 7.0.0, having both file: ^7.0.0 and flutter_cache_manager: ^3.3.1 in my pubspec.yaml results in the following:

host@HOST ~/D/r/c/tory (flutter_v3.10)> flutter pub get
Resolving dependencies... (7.0s)
Because path_provider >=2.0.0 <2.0.8 depends on
  path_provider_linux ^2.0.0 and flutter_cache_manager
  >=3.0.0-nullsafety.0 depends on path_provider ^2.0.0,
  flutter_cache_manager >=3.0.0-nullsafety.0 requires
  path_provider_linux ^2.0.0 or path_provider ^2.0.8.
And because path_provider >=2.0.8 depends on path_provider_linux
  ^2.0.1, flutter_cache_manager >=3.0.0-nullsafety.0 requires
  path_provider_linux ^2.0.0.
And because path_provider_linux >=2.0.0 <2.1.8 depends on
  xdg_directories ^0.2.0 and path_provider_linux >=2.1.8 depends on
  xdg_directories >=0.2.0 <2.0.0, flutter_cache_manager
  >=3.0.0-nullsafety.0 requires xdg_directories >=0.2.0 <2.0.0.
And because xdg_directories >=0.2.0 depends on process ^4.0.0
  which depends on file ^6.0.0, flutter_cache_manager
  >=3.0.0-nullsafety.0 requires file ^6.0.0.
So, because media_content depends on both file ^7.0.0 and
  flutter_cache_manager ^3.3.1, version solving failed.

I had to revert to file: ^6.0.0 for this package to work.

cc @Carapacik

@Carapacik
Copy link
Contributor

Carapacik commented Jul 3, 2023

I think this error with process package
google/process.dart#75
flutter/flutter#129787

@sparrow001
Copy link

I agree, I am also having a version solve conflict between a package and path_provider, which boils down to the process package using file: ^6.0.0.

@Carapacik
Copy link
Contributor

process removed from xdg_directories
https://pub.dev/packages/xdg_directories/changelog#101

Still waiting for the PR megre to work correctly with file 7.0.0
Baseflow/flutter_cached_network_image#845

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

No branches or pull requests

7 participants