I have error when i start running android
What went wrong:
A problem occurred evaluating project ':app'.
> SDK location not found. Define location with sdk.dir in the local.properties file or with an ANDROID_HOME environment variable.
I have error when i start running android
What went wrong:
A problem occurred evaluating project ':app'.
> SDK location not found. Define location with sdk.dir in the local.properties file or with an ANDROID_HOME environment variable.
local.properties
paste your Android SDK path like below
sdk.dir = C:\\Users\\USERNAME\\AppData\\Local\\Android\\sdk
sdk.dir = /Users/USERNAME/Library/Android/sdk
sdk.dir = /home/USERNAME/Android/Sdk
Replace USERNAME
with your user name
Now, Run the react-native run-android
in your terminal.
I don't think it's recommended to update the local.properties
file to get to add the missing environment vars.
sdk can be installed on /Library/Android/sdk or /usr/local/ to be sure check it by
which sdkmanager
export ANDROID_HOME=$HOME/Library/Android/sdk
or
export ANDROID_HOME="/usr/local/share/android-sdk"
Then add it to the $PATH
export PATH=$ANDROID_HOME/tools:$PATH
export PATH=$ANDROID_HOME/platform-tools:$PATH
export PATH=$ANDROID_HOME/build-tools/28.0.1:$PATH
export ANT_HOME=/usr/local/opt/ant
export MAVEN_HOME=/usr/local/opt/maven
export GRADLE_HOME=/usr/local/opt/gradle
export ANDROID_HOME=/usr/local/share/android-sdk
export ANDROID_SDK_ROOT=/usr/local/share/android-sdk
export ANDROID_NDK_HOME=/usr/local/share/android-ndk
export INTEL_HAXM_HOME=/usr/local/Caskroom/intel-haxm
I used brew cask
to install Android SDK following these instructions.
More info see https://developer.android.com/studio/intro/update#sdk-manager
Updated steps for React Native0.58 to get started on MAC/Unix
nano ~/.bash_profile
export ANDROID_HOME=$HOME/Library/Android/sdk
export PATH=$PATH:$ANDROID_HOME/emulator
export PATH=$PATH:$ANDROID_HOME/tools
export PATH=$PATH:$ANDROID_HOME/tools/bin
export PATH=$PATH:$ANDROID_HOME/platform-tools
Control+S to save
Control+X to exit
Y to save changes
source ~/.bash_profile
echo $PATH
adb devices
For Windows Users
One simple solution is to set the SDK path to the Enviroment Variables list.
Note:
Your Android Sdk is generally located in
C:\Users\YourUserName\AppData\Local\Android\Sdk
Make sure to close your current terminal because your terminal holds all of your pre-existing Environment Variables.
Your project is not finding the SDK set in the Project Settings via the path provided, so the project needs to be pointing in the right direction, and you have a couple options to accomplish this, but let's start by finding the correct SDK folder first.
From Package Manager
If you are using a package-based JRE install like Java 8 JRE via a the custom PPA in a Debian-based distribution, or used OpenJDK, the directory will most likely be /usr/lib/jvm/java-8-oracle (or whatever version you have chosen). You can find this path set in the JAVA_HOME environment variable:
$ echo $JAVA_HOME
/usr/lib/jvm/java-8-oracle
Manual Download
If you have installed via the Java JRE/SDK download, it will be wherever you placed the folder, e.g. /home/username/jdk-8u121_1.8.0 (or something similar).
Scripted installs may even add the SDK to /opt/java-8-oracle, but as of this writing, the Java Install instructions leave the folder placement in your hands.
Android Studio 2.2
Lastly if you are using Android Studio, the SDK is placed where you have set it to place the SDK files downloaded through the Studio's SDK Manager. By going to File > Settings > Appearance & Behavior > System Settings > Android SDK, you can find the SDK location setting at the top with the option to change, and the default folder being ~/Android/Sdk.
Now that we know where the SDK is, it is time to let react-native know.
Option 1: Set with local.properties
This method is very simple, and all that is needed is creating the file local.properties in the following folder, where Project_Folder is the base of your React-Native application:
Project_Folder/Android/App
In your local.properties, you want to set the variable sdk.dir to the path of your SDK folder:
sdk.dir=/home/username/Android/Sdk
While this is the easiest way to remedy the issue, it is not the best, especially if you work with multiple projects. For every project, you will have to create this file for every project, and if the folder changes plan on changing this file for each project's local.properties.
Once the file is saved, rerun the react-native run-android command.
Option 2: Settings Folders with Environment Variables
The other option is to set the SDK folders to the local environment variables that React-Native looks for by default. To do so, we will add the ANDROID_HOME path. As a bonus we can also add our android tools in the same place. We need to add this to rather the .bash_profile or .profile files in our home directory, which are loaded last, so we can make sure that nothing else is overriding the settings we make. Since these are in your home directory, there is no need to edit with escalated privileges.
**$ vim ~/.profile** (use nano or pico if you prefer)
In the file add the following lines replacing the SDK folder with the one you found above. I will be using the Android Studio folder as an example:
export ANDROID_HOME="~/Android/Sdk"
export PATH=$PATH:~/Android/Sdk/tools:~/Android/Sdk/platform-tools
Save the file, then apply the profile settings:
$ source ~/.profile
$ echo $ANDROID_HOME
/home/dbrown/Android/Sdk
If the Sdk folder shows correctly, congratulations! Re-run your react-native command, and watch the app build process continue forward.
If you still have issues
If for some reason you receive the error "> failed to find target with hash string 'android-23' in: your/sdk/folder, you need to make sure that the project's build version and the version of the SDK installed match (React-Native defaults to 23.0.1). You can find the default version in Project_Folder/android/app/build.gradle, and then searching for buildToolsVersion. You can of course change the version from this file, or in Android Studio go to File > Project Structure to change the Project SDK. I would not suggest changing this version unless you absolutely know what you are doing, otherwise install the SDK version the project is looking for.
This answer is for MacOs Catalina
user or zsh
users as your Mac now uses zsh as the default login shell and interactive shell.
If you follow along with the docs of React Native Setting up the development environment
guide. Then do the following.
Firstly check if local.properties
file exists or not.
If the file does not exist then create and add the following line.
sdk.dir=/Users/<youcomputername>/Library/Android/sdk
After doing the above changes now do the following.
~/.zshrc
using a code-editor. In my case I use vimvim ~/.zshrc
export ANDROID_HOME="/Users/<yourcomputername>/Library/Android/sdk"
export PATH=$ANDROID_HOME/emulator:$PATH
export PATH=$ANDROID_HOME/tools:$PATH
export PATH=$ANDROID_HOME/tools/bin:$PATH
export PATH=$ANDROID_HOME/platform-tools:$PATH
Make sure to add the above line correctly else it will give you a weird error.
Save the changes and close the editor.
Finally, now compile your changes
source ~/.zshrc
I get this working in my case. I hope this helps you.
The best solution I can find is as follows:
This is how the gradle file will look like:
If everything has gone well with your machine setup and you can compile the project using the Android Studio then nothing will stop you to build your app through react-native cli build android command.
With this approach, not only you will solve the problem of SDK, you will also resolve many issues related with your machine setup for Android development. The import will automatically find SDK location and create local.properties. Hence you don't need to worry about manual interventions.
For Linux Users
Your app is not getting the path of android-sdk, so If you are using linux (ubuntu), than you need to add a file named "local.properties" and save it inside the android folder, which is created inside your app folder.
You need to add below line inside local.properties file, which is the path of your android-sdk lies inside your system inside system in order to run the app.
sdk.dir=/opt/android-sdk/
save and rerun the command react-native run-android
OR
you can open terminal, type
sudo nano ~/.bashrc
and paste the below path at the end of the file
export ANDROID_HOME="/opt/android-sdk/"
and restart your computer and run again react-native run-android after that.
Note:- If you put set path in .bashrc file, then you don't even need to create local.properties file.
If you create and android studio
project, You can see a local.properties
file is created inside your project root directory. When you create a react native project, It doesn't create that file for you. So you have to create it manually. And have to add skd dir to it. So create a new file inside android folder ( on root ). and put your sdk path like this
sdk.dir=D\:\\Android\\SDK\\android_sdk_studio .
Remember: remove single \ with double. Just like above.
If local.properties file is missing, just create one in the "project/android" folder with 'sdk.dir=/Users/apple/Library/Android/sdk' and make sure your SDK in on that location.
for creating a file with custom extensions on mac refer the following link
How do I save a TextEdit (mac) file with a custom extension (.sas)?
There are 2 ways to solve this issue:
Simple run your react native Android project in the android studio it will automatically generate your local.properties file in react native Android project.
a. Go to React-native Project -> Android
b. Create a file local.properties
c. Open the file
d. Paste your Android SDK path like below
The problem is that you have misconfigured the environment variables. You have to use (in Windows) the SDK of: C:\Users\YOUR_USERNAME\AppData\Local\Android\Sdk
For more information: https://facebook.github.io/react-native/docs/getting-started
Select: React Native CLI Quickstart in the Android development environment section in point 3. Configure the ANDROID_HOME
environment variable
If you do it as you have it right now you must configure each project to use your environment variables and if the project is among several people with their equipment it can cause a problem. If you do it as I have told you, you will not have to configure any project.