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
summarised flutter doctor output given by flutter create is grammatically dubious #6304
The summarised flutter doctor output given by flutter create is grammatically dubious:
[✓] Flutter is fully installed. (on Mac OS, channel master)
[✓] Android toolchain - develop for Android devices is fully installed. (Android SDK 24.0.3)
[-] iOS toolchain - develop for iOS devices is partially installed; more components are available.
[x] Flutter IDE Support is not installed. (No supported IDEs installed)
[✓] Connected devices is fully installed.
Only the first of these actually makes sense. The others are quite confusing.
Do we need those suffixes on the toolchain ones? Can we just say Android toolchain rather than Android toolchain - develop for Android devices? It should be pretty clear what those are for.
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
sethladd commentedon Oct 13, 2016
I might shorten the iOS line to "iOS toolchain - missing critical components"
As I understand it , you would not be able to develop for iOS given your current state.
mit-mit commentedon Feb 28, 2017
Do we need those suffixes on the toolchain ones? Can we just say
Android toolchainrather thanAndroid toolchain - develop for Android devices? It should be pretty clear what those are for.Merge remote-tracking branch 'upstream/master' into issue-flutter#6304
Roll engine a8890fd to 8471862 (#22153)
dnfield commentedon Jun 15, 2019
This was fixed in #19676
github-actions commentedon Aug 15, 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.