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

every version of some_other_library depends on version.... #112

Closed
devsef opened this issue Aug 23, 2021 · 2 comments
Closed

every version of some_other_library depends on version.... #112

devsef opened this issue Aug 23, 2021 · 2 comments

Comments

@devsef
Copy link

devsef commented Aug 23, 2021

Hi.
I tried to solve the issues by following the articles
#26
#25
#11
but it did not solve the problem

First I get following error at pub get:
Because excel >=1.0.4 <2.0.0-null-safety depends on xml ^4.1.0 and flutter_svg 0.22.0 depends on xml ^5.0.0, excel >=1.0.4 <2.0.0-null-safety is incompatible with flutter_svg 0.22.0. And because no versions of flutter_svg match >0.22.0 <0.23.0, excel >=1.0.4 <2.0.0-null-safety is incompatible with flutter_svg ^0.22.0. So, because wine_region depends on both flutter_svg ^0.22.0 and excel ^1.1.5, version solving failed. pub get failed (1; So, because wine_region depends on both flutter_svg ^0.22.0 and excel ^1.1.5, version solving failed.)

After following the mentoined solutons I get following errors:
Because excel <2.0.0-null-safety depends on archive ^2.0.0 which depends on crypto ^2.0.0, excel <2.0.0-null-safety requires crypto ^2.0.0. And because google_fonts 2.1.0 depends on crypto ^3.0.0 and no versions of google_fonts match >2.1.0 <3.0.0, excel <2.0.0-null-safety is incompatible with google_fonts ^2.1.0. So, because wine_region depends on both google_fonts ^2.1.0 and excel ^1.1.5, version solving failed. pub get failed (1; So, because wine_region depends on both google_fonts ^2.1.0 and excel ^1.1.5, version solving failed.)

So I can't find any combination of libraries that works. Is there any solution available?

@neiljaywarner
Copy link

anyupdate on this?

@FauconSpartiate
Copy link
Contributor

This issue has now been fixed, version 2.0.1 that just released fixed many package conflicts.

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

3 participants