You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Unable to find suitable Visual Code toolchain. Visual Studio 2019 Community problem. #37831
C:\Program Files (x86)\Microsoft Visual Studio\Installer>vswhere.exe -json -utf8 -latest
Visual Studio Locator version 2.6.7+91f4c1d09e
Copyright (C) Microsoft Corporation. All rights reserved.
That means that vswhere is giving us incorrect information. Could you file a bug against vswhere and reference it here? Hopefully they can figure out why it's not finding your install, and depending on the underlying cause we can see if it's something we can work around in the Flutter tool (or at least provide suggestions for in the tool).
Based on discussion there, the fallback check should be passing -all to catch cases where there is an install that is present but not complete/working. We can parse out the relevant key/value pair(s), which we'll need to look up, and expose to doctor to provide a different error message.
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, including the output of flutter doctor -v and a minimal reproduction of the issue.
Activity
stuartmorgan-g commentedon Aug 8, 2019
This (the requested information):
is not the same as what you actually ran:
Could you provide the output of running with exactly the requested flags?
Ali-NS commentedon Aug 8, 2019
Here is the correct command as request :
stuartmorgan-g commentedon Aug 8, 2019
That means that vswhere is giving us incorrect information. Could you file a bug against vswhere and reference it here? Hopefully they can figure out why it's not finding your install, and depending on the underlying cause we can see if it's something we can work around in the Flutter tool (or at least provide suggestions for in the tool).
Ali-NS commentedon Aug 8, 2019
Here is the link microsoft/vswhere#198, thank you
stuartmorgan-g commentedon Aug 8, 2019
Based on discussion there, the fallback check should be passing
-allto catch cases where there is an install that is present but not complete/working. We can parse out the relevant key/value pair(s), which we'll need to look up, and expose todoctorto provide a different error message.github-actions commentedon Aug 13, 2021
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, including the output of
flutter doctor -vand a minimal reproduction of the issue.