Cordova or Ionic Android build says no build tools are installed
Error: No installed build tools found. Please install the Android build tools versionShort answer
Cordova looks for Android SDK Build-Tools inside the SDK that ANDROID_HOME points to. The error means that folder has no matching Build-Tools, or ANDROID_HOME points at the wrong place. Install the Build-Tools major version that matches your cordova-android release with sdkmanager, then build again.
Fix it fast
1Find out which cause you have
Print which SDK the build sees, which cordova-android version the project uses, and which Build-Tools are installed there.
echo "$ANDROID_HOME" cordova platform ls ls "$ANDROID_HOME/build-tools"2Match what you see, then jump to its fix
- 1
ls "$ANDROID_HOME/build-tools" is empty, or shows only an older major versionThe required Build-Tools version is not installedFix - 2
echo "$ANDROID_HOME" prints nothing, or a path with no build-tools folderANDROID_HOME is unset or points at a folder that is not the SDKFix - 3
sdkmanager: command not found when you try the install commandsdkmanager is not available to install the toolsFix
- 1
What does the error look like?
Error: No installed build tools found. Please install the Android build tools versionPlease install the Android build tools version
Cause 1 of 3
The required Build-Tools version is not installed
1Check
Cordova documents one Build-Tools range per cordova-android release: 15.x needs ^36.0.0, 14.x needs ^35.0.0, 13.x needs ^34.0.0, 12.x needs ^33.0.2. Compare the output of cordova platform ls with that list.
cordova platform ls
ls "$ANDROID_HOME/build-tools"2Fix
Install a Build-Tools version inside the range for your cordova-android release. Package names have the form build-tools;version.
sdkmanager --list | grep "build-tools;"
sdkmanager "build-tools;36.0.0"3Verify
The Build-Tools folder now has the version, and the build gets past the check.
ls "$ANDROID_HOME/build-tools"
cordova build androidConfirmed by cordova.apache.org
Cause 2 of 3
ANDROID_HOME is unset or points at a folder that is not the SDK
1Check
Cordova reads ANDROID_HOME for the SDK location. On Linux the usual place is ~/Android/Sdk. A variable set in one terminal is not there in another shell or in an IDE.
echo "$ANDROID_HOME"
ls "$ANDROID_HOME"2Fix
Export ANDROID_HOME to the real SDK folder and add the SDK tool folders Cordova lists to PATH. Put the lines in your shell startup file so they stay.
export ANDROID_HOME=~/Android/Sdk
export PATH=$PATH:$ANDROID_HOME/cmdline-tools/latest/bin:$ANDROID_HOME/platform-tools3Verify
Open a new terminal and confirm the variable is set and the folder has build-tools.
echo "$ANDROID_HOME"
ls "$ANDROID_HOME/build-tools"Confirmed by cordova.apache.org
Cause 3 of 3
sdkmanager is not available to install the tools
1Check
sdkmanager ships in the Command-line Tools package. Cordova tells you to install Android SDK Command-line Tools (latest) from Android Studio's SDK Manager, SDK Tools tab, and to put cmdline-tools/latest/bin on PATH.
ls "$ANDROID_HOME/cmdline-tools/latest/bin/sdkmanager"2Fix
Install the Command-line Tools package, then run sdkmanager by its full path until PATH is fixed.
"$ANDROID_HOME/cmdline-tools/latest/bin/sdkmanager" "build-tools;36.0.0"3Verify
sdkmanager lists the Build-Tools package as installed.
"$ANDROID_HOME/cmdline-tools/latest/bin/sdkmanager" --list_installedConfirmed by developer.android.com
How do I stop it coming back?
- After you upgrade cordova-android, read its requirement table again and install the matching Build-Tools.
- Keep ANDROID_HOME in your shell startup file and in your CI configuration.
- Use the JDK that your cordova-android version asks for: 17 for cordova-android 13 and later.
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
sdkmanager command not found after installing the Android SDK
bash: sdkmanager: command not found
sdkmanager lives in the Android Command-line Tools package, at cmdline-tools/latest/bin inside the SDK folder.
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
adb cannot connect to its daemon or start the server
* daemon started successfully *
The adb server is a background process on your computer that listens on TCP port 5037.
2 causes, each with a fixMobile 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
adb tcpip 5555 fails because no device is found
adb: more than one device/emulator
adb tcpip only works while the device is attached and listed by adb, because it tells the phone to start listening on port 5555.
4 causes, each with a fixMobile apps
The Android Emulator says /dev/kvm is not found
KVM acceleration can NOT be used
The emulator wants a hypervisor and cannot find one.
4 causes, each with a fix