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

yaml dependency with flutter 2.0.4 #34

Closed
danielle-carr opened this issue Apr 15, 2021 · 7 comments · Fixed by #35
Closed

yaml dependency with flutter 2.0.4 #34

danielle-carr opened this issue Apr 15, 2021 · 7 comments · Fixed by #35

Comments

@danielle-carr
Copy link

Flutter has now marked version 2.0.4 as stable https://flutter.dev/docs/development/tools/sdk/releases

in my pubspec.yaml the below two dependencies are included
environment_config: ^2.2.5
flutter_launcher_icons: ^0.9.0

When i execute flutter pub get I am getting the below error when using flutter 2.0.4

Because environment_config >=2.2.2 depends on yaml ^2.0.0 and flutter_launcher_icons >=0.9.0 depends on yaml ^3.0.0-nullsafety.0, environment_config >=2.2.2 is incompatible with flutter_launcher_icons >=0.9.0.
So, because myapp depends on both environment_config ^2.2.5 and flutter_launcher_icons ^0.9.0, version solving failed.

Are there any plans to update yaml dependency?

@TatsuUkraine
Copy link
Owner

hi. Yes for sure, I was waiting for all deps been migrated to null-safety (#29) . In your particular case deps conflict happens because of launcher icons package. I can try to update deps, but for now I'm not sure if it possible, meanwhile you can try to use dependency_overrides in a deps config to force yaml deps to some particular version.

@TatsuUkraine
Copy link
Owner

@danielle-carr new version is available on pub.dev, feel free to reopen this issue if you get any additional deps conflicts after update

@mlagast
Copy link

mlagast commented Apr 21, 2021

Hi @TatsuUkraine, thanks a lot for this new version.
When I run this command "dart pub outdated --mode=null-safety", the lib is still marked as not compatible for null safety

@TatsuUkraine
Copy link
Owner

@mlagast it won't be null safety compatible because it uses deps that still not migrated (#29 ) at this point I updated deps that was causing conflicts. Unfortunately can't migrate this project untill code_builder is migrated to null, unless you have any workarounds for this

@TatsuUkraine
Copy link
Owner

Oh, nvm) it seems code_build rolled out null safe version 🔥

@TatsuUkraine
Copy link
Owner

@mlagast package is migrated to null-safe, a new version should be available on pub.dev

@mlagast
Copy link

mlagast commented Apr 26, 2021

thanks a lot @TatsuUkraine

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.

3 participants