Configure FVM and IDEs for better support for different development environments.
FVM will create a relative symlink in your project from
.fvm/flutter_sdk to the cache of the selected version. Add it to your
You can configure the fvm cache directory by setting
FVM_HOME environment variable. If nothing is set the default fvm path will be used. You are also able to change the directory by setting the
--cache-path on the config. See below
There are some configurations which you can change on FVM. All settings set on CLI are compatible with the Sidekick(GUI).
You can use a different Flutter repo, a fork or as a local cache, by setting the
FVM_GIT_CACHE environment variable.
Location where Flutter SDK versions will be stored. If nothing is set, the default will be used.
You might have to restart your IDE and the Flutter debugger to make sure it uses the latest version of the configurations in some situations.
You can add the version symlink for a dynamic switch. VS Code will always use the version selected within the project for all IDE tooling. Also, remove the flutter SDK from search to make things easier.
VSCode has the ability for you to switch between all cached Flutter SDKs using
Flutter: Change SDK.
fvm list to show you the cache path to the versions.
You can see all the versions installed by FVM in VS Code by just providing path to
Alternatively, you can specify only selected versions. The following snippet will cause VS Code to show only
dev versions of Flutter.
To change current Flutter version open a project and select
Flutter: Change SDK in the command palette. You should see all the versions as depicted in the following screenshot.
- Go to
Languages & Frameworks -> Flutteror search for Flutter and change Flutter SDK path.
- Copy the absolute path of fvm symbolic link in your root project directory. Example:
- Apply the changes.
- Restart Android Studio to see the new settings applied.
You now can Run and Debug with the selected versions of Flutter.