Flutter issue - Flutter_driver from sdk depends on file 5.0.6 and flutter_gallery depends on file 5.0.7 - flutter

I got this issue using flutter packages get:
Because every version of flutter_driver from sdk depends on file 5.0.6 and flutter_gallery depends on file 5.0.7, flutter_driver from sdk is forbidden.
So, because flutter_gallery depends on flutter_driver any from sdk, version solving failed.
pub upgrade failed (1)
I don't know what I am supposed to do here, I was trying to compile this flutter example: https://github.com/flutter/flutter/tree/master/examples/flutter_gallery

This may be because flutter dependencies are locked to fixed versions.
You can check this in the pubspec.yaml for flutter_driver which is in
\flutter\packages\flutter_driver
and compare it to the latest version at GitHub
If so, flutter upgrade won't necessarily update the dependencies versions. Doing a forced update of the packages may resolve your problem.
flutter update-packages --force-upgrade

Related

Because every version of flutter_test from sdk depends on path 1.8.2 other package depends on path ^1.8.3,

(I already tried this: Because every version of flutter_test from sdk depends on path 1.8.1 openfoodfact: any)
I want to add a package ("openfoodfacts") to my pubspec file.
When I do it via Terminal: flutter pub add openfoodfacts it added the version openfoodfacts: ^0.0.8 which is old. Current version is 2.2.1.
When I try to upgrade, I receive this error:
Because every version of flutter_test from sdk depends on path 1.8.2 and openfoodfacts >=2.0.0 depends on path ^1.8.3, flutter_test from sdk is incompatible with openfoodfacts >=2.0.0.
So, because meatcheat depends on both openfoodfacts ^2.2.1 and flutter_test from sdk, version solving failed.
Anybody a clue what is wrong, or who can i upgrade flutter test to path 1.8.3?
I don't really not what flutter does, but I even reinstalled flutter, and they still install an outdated version of path.
use this command:
flutter update-packages --force-upgrade
and everything works fine.

Can't pub-get from pubspec.yaml file in Flutter app

Every time I want to install a package it gives this error, how do I fix it? The error output is below:
The current Dart SDK version is 2.12.3.
The current Flutter SDK version is 0.0.0-unknown.
Because image_picker >=0.3.0 requires Flutter SDK version >=0.1.4 and image_picker <0.3.0 requires SDK version >=1.8.0 <2.0.0, image_picker is forbidden.
So, because firebase depends on image_picker any, version solving failed.
Running "flutter pub get" in firebase...
pub get failed (1; So, because firebase depends on image_picker any, version solving failed.)
You check your flutter version and check that dependency version and change the dependency version otherwise remove the version.
You have to either:
Downgrade the version of image_picker to match the flutter SDK version you currently use, or
Upgrade your flutter SDK version to a version above or equal to 1.8.0. (preferred solution).

flutter HERE Maps SDK - dependency on ffi: 1.0.0 - conflicting with another plugin

running into the following issue where Here SDK is conflicting with another plugin (file_picker)...
Because every version of here_sdk from path depends on ffi 1.0.0 and file_picker >=4.0.0 depends on ffi ^1.1.2, here_sdk from path is incompatible with file_picker >=4.0.0.
So, because AppName depends on both file_picker 4.1.3 and here_sdk from path, version solving failed.
pub get failed (1; So, because AppName depends on both file_picker 4.1.3 and here_sdk from path, version solving failed.)
The issue is the "ffi: 1.0.0" in Here's pubspec.yaml which locks in version 1.0. For reference, I am using 4.8.3 of the SDK. Is there any reason why Here doesn't use the carat ^ notation so that pub can use the latest 1.x version and not the hardcoded 1.0.0 version? I can go in and change the pubspec.yaml version myself for Here SDK, but i don't want to introduce any incompatibility. Technically this should be ok because of semantic-versions, but of course i don't want to make any assumptions.
thoughts? thanks!
We are evaluating upgrading ffi version but there is no certain timeline on this by when this will be available. It is possible to change the ffi version in the pubspec.yml but as explained above that it is risky.

Added get it dependency. IDE gave version solving error

Because every version of integration_test from sdk depends on collection 1.15.0-nullsafety.5 and get_it >=6.0.0 depends on collection ^1.15.0, integration_test from sdk is incompatible with get_it >=6.0.0.
So, because mcuapp depends on both get_it ^6.0.0 and integration_test any from sdk, version solving failed.
pub get failed (1; So, because mcuapp depends on both get_it ^6.0.0 and integration_test any from sdk, version solving failed.)
Process finished with exit code 1
Note: I had recently upgraded Dart and flutter
You can try to remove the version int the pubspec.yaml and replace it with any.
This however might break code, since it will use an other version of the package. In some cases some packages are not compatible with other packages at all
Update all dependencies from pubspec.yaml file because some of your updated dependencies and depending on old version dependencies. Just
Go to [pub.dev][1] > search your dependencies > copy updated version to pubspec.yaml file > run flutter pub get > flutter pub upgrade
[1]: https://pub.dev/

I am getting an error in flutter setup in android studio in windows, i already updated and having latest version of flutter and android studio

After completing all steps like SDK download, path setup in windows getting this error in flutter setup.
This error is occuring before creating flutter project.
The current Dart SDK version is 2.9.2. Because flutter_tools depends on test >=1.16.0-nullsafety which requires SDK version >=2.10.0-0 2.11.0, version solving failed. pub get failed (1; Because flutter_tools depends on test >=1.16.0-nullsafety which requires SDK version >=2.10.0-0 2.11.0, version solving failed.)
Please show your pubspec file. If you have tried all possible solutions and can't figure out the issue, I would say to try and reinstall it.