Expo cannot start the Android emulator: spawn adb ENOENT
Error: spawn adb ENOENTShort answer
ENOENT means the tool that launched adb could not find an executable named adb on your PATH. Either the Android SDK platform-tools folder is not on PATH, ANDROID_HOME points to the wrong folder, or the platform-tools package is not installed. Check adb in a fresh terminal first.
Fix it fast
1Find out which cause you have
Open a brand new terminal (not the one you edited settings in) and ask the shell where adb is. If it prints nothing or says not found, the PATH is the cause.
adb --version echo $ANDROID_HOME2Match what you see, then jump to its fix
- 1
adb --version says command not found, while the SDK is installedplatform-tools is not on PATHFix - 2
ANDROID_HOME is set, but adb is still not found, or the path does not existANDROID_HOME points to a folder that is not the SDKFix - 3
The platform-tools folder does not exist inside the SDK folderThe Android SDK Platform-Tools package is not installedFix
- 1
What does the error look like?
Error: spawn adb ENOENTspawn adb ENOENT
Cause 1 of 3
platform-tools is not on PATH
1Check
The Expo environment guide says to add the emulator and platform-tools folders of the SDK to PATH. Look for those lines in your shell profile.
grep -n ANDROID_HOME ~/.zshrc ~/.zprofile ~/.bashrc ~/.bash_profile 2>/dev/null2Fix
On macOS, add the three lines from the Expo guide to ~/.zshrc (zsh) or ~/.bashrc (bash), then reload the file. On Windows, add %LOCALAPPDATA%\Android\Sdk\platform-tools to the Path user variable in the environment variable dialog.
export ANDROID_HOME=$HOME/Library/Android/sdk
export PATH=$PATH:$ANDROID_HOME/emulator
export PATH=$PATH:$ANDROID_HOME/platform-tools
source $HOME/.zshrc3Verify
adb now prints its version from the terminal that starts Expo.
adb --versionConfirmed by docs.expo.dev
Cause 2 of 3
ANDROID_HOME points to a folder that is not the SDK
1Check
Compare the variable with the SDK location Android Studio shows under Settings > Languages & Frameworks > Android SDK > Android SDK Location. On Windows the default is %LOCALAPPDATA%\Android\Sdk; in PowerShell you can list the variables.
echo $ANDROID_HOME
ls "$ANDROID_HOME/platform-tools"2Fix
Set ANDROID_HOME to the exact SDK location Android Studio shows, and build the PATH entries from that variable, then open a new terminal.
# macOS default location, change if Android Studio shows another one
export ANDROID_HOME=$HOME/Library/Android/sdk
export PATH=$PATH:$ANDROID_HOME/platform-tools3Verify
The platform-tools folder lists an adb file, and adb --version works.
ls "$ANDROID_HOME/platform-tools"
adb --versionConfirmed by docs.expo.dev
Cause 3 of 3
The Android SDK Platform-Tools package is not installed
1Check
adb ships in the Android SDK Platform-Tools package, which the SDK Manager installs into android_sdk/platform-tools/. If that folder is missing, the package is not installed.
ls "$ANDROID_HOME"2Fix
In Android Studio open the SDK Manager, go to the SDK Tools tab and install Android SDK Platform-Tools. Alternatively download the standalone Platform Tools package from Android and point PATH at its folder.
# after installing, confirm the binary exists
ls "$ANDROID_HOME/platform-tools/adb"3Verify
adb devices runs without ENOENT and lists your emulator once it is booted.
adb devicesConfirmed by developer.android.com
How do I stop it coming back?
- Keep ANDROID_HOME and the PATH lines in one shell profile file, and restart the terminal after editing it.
- Start Expo from the same terminal where adb --version already works.
- After moving or reinstalling the SDK, update ANDROID_HOME before anything else.
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.
- WorkforceA field app, an admin console and a self-hosted Node.js server for push and reconciliation.
Related fixes
Mobile apps
adb prints 'server version doesn't match this client; killing...'
adb server version doesn't match this client; killing...
adb runs a background server, and every adb command is a client.
3 causes, each with a fixMobile apps
Android Studio says it cannot find adb
'adb' is not recognized as an internal or external command, operable program or batch file.
adb is shipped in the SDK Platform-Tools package, in the platform-tools folder of your Android SDK.
3 causes, each with a fixMobile apps
Gradle cannot run node in a React Native Android build
Process 'command 'node'' finished with non-zero exit value 1
The React Native Gradle plugin starts node for bundling.
3 causes, each with a fixMobile apps
adb cannot start because something already holds its port
adb start-server failed
The adb server must bind local TCP port 5037, and every adb client talks to it there.
2 causes, each with a fixMobile apps
The phone shows as unauthorized and Android Studio will not run the app
adb devices lists the phone but Android Studio cannot deploy to it
An unauthorized phone means it has not trusted this computer's RSA key.
3 causes, each with a fixMobile apps
Android Studio cannot pair the phone over Wi-Fi
The Pair devices over Wi-Fi dialog lists no device
Wireless pairing needs the phone on Android 11 or higher and on the same Wi-Fi network as the computer, with current Platform-Tools.
4 causes, each with a fix