@mathew.smith

I don't think that is needed.

More detailed explanation:

If we inspect the path "/absolute-path-to-the-project/.fvm/flutter_sdk" carefully then we'll realize that it is not actually a folder but a symbolic link to the location where the selected flutter version is stored. ie. If you set the version 2.0.0 project-wise using the command "fvm use 2.0.0" then the path "/absolute-path-to-the-project/.fvm/flutter_sdk" will point to the location where that version is stored in the system(in my case that location is "/Users/crystal/fvm/versions/2.0.0" where crystal is my user name and the location is the default cache location which can be changed as well). Now when We change the version to 3.0.0 using "fvm use 3.0.0" then the path "/absolute-path-to-the-project/.fvm/flutter_sdk" will simply point to "/Users/crystal/fvm/versions/3.0.0" without us requiring to update the path in android studio which is still "/absolute-path-to-the-project/.fvm/flutter_sdk".

This explaination is when we change the flutter version within the same project. As for the different projects, android studio maintains separate settings for each of them, so we don't have to worry about that either.