-
Notifications
You must be signed in to change notification settings - Fork 406
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
[BUG] Resolving Dependencies Fail #241
Comments
I'm getting the same issue. I'm running on stable channel, and can get the 0.8.1 version loaded but not the 0.9.0. However when I do get 0.8.1 it won't run complaining the SDK is not the right version. running pub get does not clear the issue. dev_dependencies: Because flutter_launcher_icons >=0.9.0 depends on args 2.0.0 and every version of flutter_driver from sdk depends on args 1.6.0, flutter_launcher_icons >=0.9.0 is incompatible with flutter_driver from sdk. dev_dependencies: Atlas:time_pie_02 tobylewis$ flutter pub get Atlas:time_pie_02 tobylewis$ pub run flutter_launcher_icons:main Atlas:time_pie_02 tobylewis$ dart --version Atlas:time_pie_02 tobylewis$ flutter doctor • No issues found! |
As a quick fix: since both flutter_driver and flutter_launcher_icons are both dev dependencies, you can just comment out flutter_driver during icon creation and restore after icon creation is complete, then you can obviously comment out flutter_launcher_icons and uncomment flutter_driver again. |
Any update on this? I believe #245 is related to this issue. |
Looks like it has been fixed with the 0.9.0 version. |
I'm getting this error: Because archive >=3.0.0-nullsafety.0 <3.0.0 depends on crypto ^3.0.0-nullsafety.0 and image >=3.0.0-nullsafety.0 <3.0.1 depends on archive ^3.0.0-nullsafety.0, image >=3.0.0-nullsafety.0 <3.0.1 requires crypto ^3.0.0-nullsafety.0 or archive ^3.0.0. |
Because flutter_launcher_icons >=0.9.0 depends on args 2.0.0 and every version of flutter_driver from sdk depends on args 1.6.0, flutter_launcher_icons >=0.9.0 is incompatible with flutter_driver from sdk.
The text was updated successfully, but these errors were encountered: