Gradle Android and the ANDROID HOME SDK location

Question

edit   aug-2016   That question is from November 2013  while Android Studio was still in Developer Preview mode     Currently  AS v2 2  Aug-2016  during instalation AS asks to choose the SDK folder  or install on their default  and it automatically applies to which ever project you re opening   That means any possible workaround or fix is irrelevant as the issue is not reproducible anymore   original question   we have this project with several modules that is already configured and executes correctly on another developer PC using a wrapper  I cloned the complete git submodules into my machine   Below it s a directly print of my command line       gradlew  FAILURE  Build failed with an exception     Where  Build file   home budius project name ActionBar-PullToRefresh library build gradle  line  1    What went wrong  A problem occurred evaluating project   ActionBar-PullToRefresh library    gt  SDK location not found  Define location with sdk dir in the local properties file or with an ANDROID HOME environment variable     Try  Run with --stacktrace option to get the stack trace  Run with --info or --debug option to get more log output   BUILD FAILED  Total time  6 378 secs    echo  ANDROID HOME  home budius Applications android-studio sdk      so  as you can see the ANDROID HOME is there  What else do they want  What s wrong here   running on Ubuntu 13 04  edit   I already created a local properties file with sdk dir  lt path gt  on the project root and it works  But that makes the code harder to port across systems n build server  so the question is still open    Anyone knows why the ANDROID HOME is not working and what to do to make it work

User · Answer

Just delete the sdk dir inside the local preoperties file and set the ANDROID HOME environment variable   It worked for me

User · Answer

This works for me     export ANDROID HOME  path to sdk      gradlew

User · Answer

I came across the same problem when opening a cloned git repository  The local properties file is automatically added to the  gitignore file as it is specific to the build environment of each machine and is therefore not part of the repo   The solution is to import the project instead of just opening it after you have cloned it from git  this forces android studio to create the local properties file specific to your machine   File    Import Project

User · Answer

I have just solved the exact same issue by adding the ANDROID HOME as a system wide variable  In Ubuntu it should be in  etc profile or in a shell script file in  etc profile d   Then logout and login again  now Gradle should recognize the ANDROID HOME variable

User · Answer

If you are using windows plantform  please try run Android Studio as Administrator

User · Answer

in windows  I set ANDROID HOME E  android adt-bundle-windows-x86 64-20131030 sdk Then it works as expect    When in Linux  you need to set sdk dir    The script uses two different variables

User · Answer

That question is from November 2013  while Android Studio was still in Developer Preview mode     Currently  AS v2 2  Aug-2016  during instalation AS asks to choose the SDK folder  or install on their default  and it automatically applies to which ever project you re opening   That means any possible workaround or fix is irrelevant as the issue is not reproducible anymore

User · Answer

Your local properties file might be missing  If so add a file named  local properties  inside  local properties and provide the sdk location as following    sdk dir C  Users  AppData Local Android Sdk

User · Answer

On OSX  IntelliJ won t pick up the environment variables you set in your  bash profile or  bash rc etc     Try this  substituting the value of your own sdk location   launchctl setenv ANDROID HOME  usr local opt android-sdk  Then restart IntelliJ and Bob s your uncle   Here is a reference to the problem  stated more generally  https   emmanuelbernard com blog 2012 05 09 setting-global-variables-intellij

User · Answer

You said that versioning local properties creates problems for you  I ve hacked together a script which uses android command line tool to refresh the local properties file across the machines that are involved in the production  The android update project command  besides the local properties produces a lot of unwanted trash  at least for me  which is the reason for all those rm commands at the end of the script      bin bash scname   0  echo    scname   updating local properties     ln -fs src main AndroidManifest xml android update project -t 24 -p    pwd   echo    scname      done  echo    scname   removing android update project junk      rm -v project properties rm -v build xml rm -v proguard-project txt rm -v AndroidManifest xml echo    scname      done    This script is the first thing we run on any new machine where we code  It has to be run in the root project directory  Of course  android studio may have a GUI way of dealing with this  but I wouldn t know as I use a different editor  I also can t claim that the solution is general  but it  Works For Me   tm

User · Answer

The Android Gradle plugin is still in beta and this may simply be a bug  For me  setting ANDROID HOME works  but we may be on different versions  please try again with the most recent version and let me know if it works or not    It s also worth setting the environment variable ANDROID SDK as well as ANDROID HOME   I have seen issues with this on some machines  so we do create local properties in those cases - I have also noticed that the latest version of Android Studio will create this file for you and fill in the sdk dir property   Note that you shouldn t check local properties into version control  we have added it to our gitignore so that it doesn t interfere with porting the code across systems which you rightfully identified as a potential problem

User · Answer

Copy the local properties to root folder and run again

User · Answer

i encountered the same error but in my case i was cloning a project  the cloned project was built with Android API 22 which i did not install at the time i had API 24 and 25 installed         so i had to download the sdk tools for API 22

User · Answer

I have set the ANDROID HOME    PATH OF MY ANDROID SDK  to my environment variable  That solution works for me

User · Answer

In Linux  try to run studio sh from a terminal and set the ANDROID HOME in this terminal  This worked for me

User · Answer

For Windows    Add ANDROID HOME to the Environment Variables   ANDROID HOME   C  Users YOUR USERNAME AppData Local Android sdk  Add  ANDROID HOME  platform-tools to the PATH

User · Answer

I faced the same issue  though I had local properties file in my main module  and ANDROID HOME environment variable set at system level    What fixed this problem was when I copied the local properties file which was in my main project module to the root of the whole project  i e the directory parent to your main module   Try copying the local properties file inside modules and the root directory  Should work

User · Answer

I have faced with the same issue on Ubuntu both local properties and ANDROID HOME was added   but build fail persisted  So workaround is to  add following lines   export ANDROID HOME  home  lt user gt  Android Sdk export PATH  PATH  home  lt user gt  Android Sdk tools  directly to the studio sh script  inside  usr local android-studio bin   Maybe it will be helpful

User · Answer

export ANDROID HOME  xxx xxx  in shell  then use it by System env ANDROID HOME in gradle file   PS  don t forget the  export  keywords to make the ANDROID HOME global

User · Answer

I have the same problem  seems the sample code can not find the android environment  instead to try to fix that I just remove the sample code from settings gradle and then the installation goes fine   after that just import the project in eclipse and that s all

User · Answer

This worked for me  Ubuntu    Add ANDROID HOME  path to android-sdk to  etc environment   Reboot

User · Answer

MAC OSX    Open up Terminal and edit the file       bash profile  to add   export ANDROID HOME   Library Android sdk export PATH   PATH    ANDROID HOME  tools export PATH   PATH    ANDROID HOME  platform-tools   Run   source    bash profile Restart the Terminal and Android Studio

User · Answer

Installing Build-Tools 23 0 1 instead of 23 0 2 fixed this issue for me

User · Answer

How to do it on MAC OSX   1  Open up Terminal  and Edit  vi    bash profile If there is no file there  just add it   2  Add  Change to YOUR USER NAME and add this     Java var home  JAVA HOME   usr libexec java home  ANDROID HOME   Users  lt YOUR USER NAME gt  Library Android sdk   3  Run source    bash profile   4  Run echo  JAVA HOME  echo  ANDROID HOME   5  If your output is    usr libexec java home  Users  lt YOUR USER NAME gt  Library Android sdk  So you are good   and RESTART android studio   And  Make sure that you have java      java -version  And gradle     gradle --version

User · Answer

I ve solved the problem  This works for me   In      my current project    I ve created a file called local properties and put inside     sdk dir  my current path to sdk   In the console I need to do     set ANDROID HOME  my current path to sdk   Hope this helps

User · Answer

In my case settings gradle was missing   Save the file and put it at the top level folder in your project  even you can copy from another project too   Screenshot reference     Hope this would save your time

User · Answer

I came across a similar problem  Somehow  I did not have a build folder in my project  By copying this folder from another project to my project I was having an issue with  this fixed this problem

User · Answer

For whatever reason  the gradle script is not picking up the value of ANDROID HOME from the environment  Try specifying it on the command line explicitly    ANDROID HOME  lt sdk location gt    gradlew

User · Answer

On my system  Ubuntu 20 04 after two version upgrades from 19 04  the symptoms were as if gradle  4 4 1 installed from APT repos  ignored ANDROID HOME environment variable  while picking up the sdk dir value from local properties if I created one   The reason appeared to have been that java command referred to openjdk version  11 0 7   After I installed openjdk-8-jdk package and did update-alternatives --config java to make the default java be version 8   1 8 0 252    gradle started working as expected

User · Answer

solutions   1 add  sdk dir path of sdk   2 execute gradlew with evn variable like following    ANDROID HOME path of sdk   gradlw

[android] Gradle, Android and the ANDROID_HOME SDK location

Examples related to android

Examples related to gradle

Examples related to android-build

Examples related to android-gradle-plugin