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
Flutter Doctor "Android SDK does not have the proper build-tools." is misleading #6529
The following output is misleading as the build-tools in my android sdk were up to date - I just hadn't installed the SDK platform part of the sdk.
$ flutter doctor
[✓] Flutter (on Linux, channel master)
• Flutter at <redacted>
• Framework revision 2ac7d67e6a (85 minutes ago), 2016-10-25 10:40:54
• Engine revision a8604ba9d2
• Tools Dart version 1.21.0-dev.0.0
[-] Android toolchain - develop for Android devices
• Android SDK at <redacted>
x Android SDK does not have the proper build-tools.
• Try re-installing or updating your Android SDK.
[✓] Atom - a lightweight development environment for Flutter
• flutter plugin version 0.2.6
• dartlang plugin version 0.6.42
Device <redacted> is not authorized.
You might need to check your device for an authorization dialog.
[✓] Connected devices
• None
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
mit-mit commentedon Nov 2, 2016
I suggest we change it to
Android SDK is missing command line tools; download from https://goo.gl/XxQghQ).mit-mit commentedon Nov 2, 2016
CC @danrubel
Update flutter doctor text
stevenroose commentedon Jan 19, 2018
What exactly is missing when you get this message? I get it, I'm on Arch and I installed both
android-toolsandandroid-platform.Add support for text shadows and roll engine (26 commits) (#22449)
github-actions commentedon Sep 4, 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.