Open sethladd opened 7 years ago
The problem here was that I had some old version of adb on my path. I somehow installed adb via homebrew, and it was version 23. I was trying here to connect to API version 25.
I removed all android packages from homebrew, and went into Android Studio and downloaded the proper SDK tools for version 25.
flutter doctor didn't report any issue, because it was just saying:
[✓] Android toolchain - develop for Android devices (Android SDK 23.0.2)
• Android SDK at /Users/sethladd/homebrew/opt/android-sdk
• Platform android-23, build-tools 23.0.2
• Java(TM) SE Runtime Environment (build 1.8.0_91-b14)
Maybe we can do some version checking when flutter run
is run, and check if my tools are sufficient to connect to the Android version?
Basically, this bug could be reconsidered as "flutter doctor isn't helping me when I have older adb/android sdk when I'm targeting a newer android sdk version"
Sounds like a very good warning to add to flutter doctor
. FYI @danrubel
Similar to part 2 of https://github.com/flutter/flutter/issues/6513#issuecomment-255968306
It seems to check if adb
is in a valid SDK directory and SDK version is >= 25
Not sure if this fully covers the problem.
I used the Android Virtual Device Manager to create a new x86 + 7.1.1 instance, with API 25.
I've tried a few times, I can't get the starter app to start...