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

The library conflicts with flutter_cache_manager because of different versions of the 'flutter_cache_manager' #54

Closed
YouCii opened this issue Mar 11, 2019 · 6 comments

Comments

@YouCii
Copy link
Contributor

YouCii commented Mar 11, 2019

The error log :

Because flutter_inappbrowser >=0.2.0 depends on uuid ^1.0.3 and flutter_cache_manager >=0.3.0 depends on uuid ^2.0.0, flutter_inappbrowser >=0.2.0 is incompatible with flutter_cache_manager >=0.3.0.


And because cached_network_image 0.6.2 depends on flutter_cache_manager ^0.3.1 and no versions of cached_network_image match >0.6.2 <0.7.0, flutter_inappbrowser >=0.2.0 is incompatible with cached_network_image ^0.6.2.
So, because ecns_flutter depends on both cached_network_image ^0.6.2 and flutter_inappbrowser ^0.5.51, version solving failed.
@YouCii
Copy link
Contributor Author

YouCii commented Mar 11, 2019

How can I solve such issues?

@pichillilorenzo
Copy link
Owner

I'm just releasing the new version 0.6.0 with uuid ^2.0.0, so I think it will solve your problem!

@YouCii
Copy link
Contributor Author

YouCii commented Mar 11, 2019

@pichillilorenzo Thanks for your reply. Currently i use 'cached_network_image: any' to handle the conflict.

@pichillilorenzo
Copy link
Owner

Ok! However, I published the new version right now!

@YouCii
Copy link
Contributor Author

YouCii commented Mar 11, 2019

Great, I have already got it.

This was referenced Jul 6, 2020
Copy link

This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug and a minimal reproduction of the issue.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Nov 14, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants