VS Code shows 'No Devices' for a connected Android phone or emulator
No DevicesShort answer
VS Code only shows what Flutter and adb can already see. Run flutter devices in a terminal first. If it lists nothing, the problem is on the phone or the USB link: debugging off, the RSA prompt not accepted, a missing driver or udev rule. If the terminal sees it, open the folder that holds pubspec.yaml.
Fix it fast
1Find out which cause you have
Ask Flutter and adb directly. This separates a phone-side problem from a VS Code problem.
flutter devices adb devices2Match what you see, then jump to its fix
- 1
adb devices shows nothing, or the phone never showed an 'Allow USB debugging' dialogUSB debugging is off, or the computer was not authorisedFix - 2
Nothing appears on Windows or Ubuntu even with debugging on, while a different cable or phone worksThe operating system has no way to talk to the phoneFix - 3
The phone is authorised and plugged in, but no tool lists itThe adb server is stuckFix - 4
flutter devices lists the device, but the VS Code status bar still says No Devices and shows no Flutter versionThe emulator is not running, or VS Code is not looking at the Flutter projectFix
- 1
What does the error look like?
No DevicesVisual Studio Code can't detect emulator device or phone connected
Cause 1 of 4
USB debugging is off, or the computer was not authorised
1Check
On the phone open Settings, Developer options, and confirm USB debugging is on. Android shows an RSA key dialog the first time; it must be accepted on an unlocked phone.
adb devices2Fix
Turn on USB debugging, unplug and reconnect the cable, unlock the phone, and accept the dialog. If you refused it before, use the Revoke adb debugging authorizations setting and connect again.
flutter devices3Verify
The phone appears in the list with its model name.
adb devicesConfirmed by developer.android.com
Cause 2 of 4
The operating system has no way to talk to the phone
1Check
Windows needs a USB driver for the phone, from the manufacturer. On Ubuntu your user must be in the plugdev group and udev rules must cover the device. Try a second cable first.
id2Fix
On Windows install the OEM driver. On Ubuntu add yourself to plugdev, install the udev rules package, then log out and in.
sudo usermod -aG plugdev $LOGNAME
sudo apt-get install android-sdk-platform-tools-common3Verify
After logging in again, id lists plugdev and adb devices shows the phone.
id
adb devicesConfirmed by developer.android.com
Cause 3 of 4
The adb server is stuck
1Check
Android Studio has a Connection Assistant that scans the USB port again and can restart the ADB server.
adb devices2Fix
In Android Studio choose Tools, then Troubleshoot Device Connections, and use Restart ADB server on its last page. Then reload the VS Code window.
flutter devices3Verify
flutter devices lists the phone after the restart.
flutter devicesConfirmed by developer.android.com
Cause 4 of 4
The emulator is not running, or VS Code is not looking at the Flutter project
1Check
The Flutter extension reads the project from a VS Code workspace folder. If pubspec.yaml sits in a subfolder that was not opened as a workspace folder, the status bar stays empty. An emulator must also be started.
flutter emulators2Fix
Open the folder that contains pubspec.yaml, or add it as a workspace folder. Start an emulator, then click the device name in the status bar and pick it.
flutter emulators --launch <emulator_id>3Verify
The status bar shows the Flutter SDK version and the selected device.
flutter doctorConfirmed by docs.flutter.dev
How do I stop it coming back?
- Run flutter devices in a terminal before blaming the editor.
- Keep a spare USB cable, so a bad cable can be ruled out quickly.
- Keep the Flutter and Dart extensions updated.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Every cause above names the document that confirms it. I have not reproduced this fix on a machine of my own yet, so read it as documented guidance, not a test report. Found a mistake? Tell me.
Which stack is behind this page?
Projects of mine built on the same technologies:
- TaxiDexMy own multi-tenant taxi dispatch SaaS: API, dispatcher portal, driver and passenger apps, and the servers underneath.
- QistLockA NestJS and React SaaS driving an Android Device Owner agent that locks financed phones when payments lapse.
- Dispatch ProA real-time logistics platform: Flutter apps, Spring Boot services and a Kafka event pipeline on AWS.
Related fixes
Mobile apps
Google Play says the app does not support 16 KB memory pages
check_elf_alignment.sh reports UNALIGNED for a library under lib/arm64-v8a
Google Play requires apps that target Android 15 or higher and ship native .so libraries to run on devices with 16 KB memory pages; from 1 February 2027 it will block updates that do not.
5 causes, each with a fixMobile apps
Gradle cannot find com.google.firebase:firebase-analytics-ktx
Required by: project :app
Firebase moved the Kotlin extensions into the main modules and stopped releasing the -ktx modules in July 2025.
2 causes, each with a fixMobile apps
Gradle cannot create LibraryVariantBuilderImpl in a Flutter Android build
Could not create an instance of type com.android.build.api.variant.impl.LibraryVariantBuilderImpl
This error appears when the Android Gradle plugin (AGP) cannot run in the Gradle or IDE you use.
3 causes, each with a fixMobile apps
Flutter release build cannot open the keystore: HmacPBESHA256 not available
Algorithm HmacPBESHA256 not available
The keystore is a PKCS12 file protected by a newer algorithm than the Java that is reading it understands.
3 causes, each with a fixMobile apps
Android install error: the package conflicts with an existing package of the same name
The package conflicts with an existing package by the same name
Android allows only one app per application ID, and an update must be signed with the same certificate as the installed version.
3 causes, each with a fixMobile apps
Android resource linking fails with resource android:attr/lStar not found
error: failed linking references.
The lStar attribute exists only from Android API 31.
2 causes, each with a fix