React Native on Android could not find Build Tools

What causes the following problem? Android SDK version not supported?

Starting JS server... Building and installing the app on the device (cd android && gradlew.bat installDebug)... FAILURE: Build failed with an exception. * What went wrong: A problem occurred configuring project ':app'. > failed to find Build Tools revision 23.0.1 
+86
javascript android reactjs react-native
Oct. 15 '15 at 17:40
source share
10 answers

You may need to update your build tools.

I encountered a problem when trying to update from the GUI, it did not display the exact minor version, so I could not update it.

This was resolved by looking at the available versions from the terminal:

 android list sdk -a 

 [...] Packages available for installation or update: 156 1- Android SDK Tools, revision 24.4 2- Android SDK Platform-tools, revision 23.0.1 3- Android SDK Platform-tools, revision 23.1 rc1 4- Android SDK Build-tools, revision 23.0.1 

[...]

And installing the correct version with:

 android update sdk -a -u -t 4 
+132
Oct. 15 '15 at 19:55
source share

Just a note - it's possible to get this error because the only version of the installed build tools is too new.

I got exactly the error that OP got (complaining that native-native could not find Editing Build Tools 23.0.1). When I checked my Android SDK Manager, I saw this:

screenshot showing 23.0.2

I naively thought that installing the latest version of Build-tools (23.0.2 at the time of writing) would work, but apparently not. In addition, installing 23.0.1 fixes the problem.

+71
Dec 13 '15 at 20:42
source share

I also had a problem with a newer version of the Build SDK tools (the same as with Mark), but I managed to resolve it with a modification of android/app/build.gradle and setting the correct version, for example.

 android { compileSdkVersion 23 buildToolsVersion "23.0.2" ... 

UPDATE: As Mark noted, it is only wise to update a small (or patch) version in this way. Another reason not to update this version is when you have many third-party libraries with your own part - you can end up updating all of them. Thus, you should weigh the possible benefits of a newer version and a bit more work.

+25
Jan 21 '16 at 16:20
source share

Need to change 4 files

grep buildToolsVersion * -r | grep 23.0.1

 Examples/Movies/android/app/build.gradle: buildToolsVersion "23.0.2" Examples/UIExplorer/android/app/build.gradle: buildToolsVersion "23.0.2" ReactAndroid/build.gradle: buildToolsVersion "23.0.2" local-cli/generator-android/templates/src/app/build.gradle: buildToolsVersion "23.0.2" 
+4
Feb 01 '16 at 17:47
source share

I want to change the android project project.gradle to:

  compileSdkVersion 23 buildToolsVersion "23.0.3" defaultConfig { applicationId "com.demoproject" minSdkVersion 16 targetSdkVersion 23 versionCode 1 versionName "1.0" ndk { abiFilters "armeabi-v7a", "x86" } 
+3
Jun 06 '16 at 4:03
source share

This means that the Android build tools installed on your system are something different from your application configuration file (your configuration file points to 23.0.1), but you probably have 23, 24 or 25.0. * on your system.

The solution to this problem :

Edit the build.gradle file located in anroid/app in the project folder

Find the buildToolsVersion entry "23.0.1" and replace it with the latest version available on your system.

You can find it here: C:\Program Files (x86)\Android\android-sdk\build-tools

OR install the version available in this file on your system (with the SDK manager).

Good luck.

+3
Feb 02 '17 at 18:49
source share

If you have build tools for version 24.0.1, then in build.gradle update as buildToolsVersion "24.0.0" In my Android / Sdk / build-tools / 24.0.1 / source.properties it had Pkg.Revision=24.0.0

+1
Aug 03 '16 at 3:19
source share

Find the version number in the / Users / username / Library / Android / sdk / build -tools directory, and then change the buildToolsVersion version number to match the gradle configuration

+1
Dec 08 '16 at 6:16
source share

I had this problem trying to build on the command line after checking the source documentation. I solved this problem by opening a project in Android studio. Inappropriate dependencies will appear in the snackbar assembly failure at the bottom of the application. For each failure, click the link to solve the problem.

0
Apr 13 '17 at 22:07 on
source share

From the Android SDK manager v25, you need to install the right build tools directly from Android Studio, because the android command no longer works:

install from android studio

0
May 31 '17 at 21:40
source share



All Articles