Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages
Flutter and app store releases

Expo cannot start the Android emulator: spawn adb ENOENT

ErrorError: spawn adb ENOENT

Short 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.

  • Applies to Expo SDK 54, Node.js 22, Android Studio, macOS, Windows 11
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Fix it fast

  1. 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_HOME
  2. 2Match what you see, then jump to its fix

    1. 1adb --version says command not found, while the SDK is installedplatform-tools is not on PATHFix
    2. 2ANDROID_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. 3The platform-tools folder does not exist inside the SDK folderThe Android SDK Platform-Tools package is not installedFix

What does the error look like?

  • Error: spawn adb ENOENT
  • spawn 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/null

2Fix

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/.zshrc

3Verify

adb now prints its version from the terminal that starts Expo.

adb --version

Confirmed by docs.expo.dev

Did this fix it?

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-tools

3Verify

The platform-tools folder lists an adb file, and adb --version works.

ls "$ANDROID_HOME/platform-tools"
adb --version

Confirmed by docs.expo.dev

Did this fix it?

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 devices

Confirmed by developer.android.com

Did this fix it?

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:

Related fixes

Mobile 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 fix

Mobile 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

Next step

Want this handled for good?

I look after servers, apps and releases end to end. Tell me what keeps breaking.