Accepted answer

It seems that cleaning this specific project doesn't work but cleaning all open project does the trick.

I leave this question if someone else get this issue.


I didn't collide with this problem, but if you have ADT 8 revision or later, so you should read it's dependencies better: "ADT 8.0.0 is designed for use with SDK Tools r8. If you haven't already installed SDK Tools r8 into your SDK, use the Android SDK and AVD Manager to do so." (


I've run into this problem constantly and can not get R to be resolved to a variable after making projects clean, in addition to not being able to find aapt - Error executing aapt. Please check aapt is present at C:\AndroidSDK\android-sdk-windows\platform-tools\aapt.exe

None of the suggestions on this page make any sense or have helped in anyway. I'm using nothing but API 8 onwards.


I solved this problem by checking 'build automatically' under project menu.


I have faced the same problem after updating the SDK. I find out that the AUTOGENERATE folder doesn't have any file. What I done is :


  1. rollback the SDK version to 16
  2. Install all the tool provided.
    • SDK TOOLS (Version 16)
    • Platform Tools
  3. install the SDK 4.0
  4. Restart the eclipse

It solved!


Following did the trick for me. Had to do the build dep as some of the lib dependencies were missing.

sudo apt-get install lib32z1 
sudo apt-get build-dep lib32z1
sudo apt-get install lib32stdc++6 lib32z1 lib32z1-dev

Restart eclipse


For me, the problem was that Eclipse 4.4 was looking for aapt without "bin/" at the end of the path.

Since I could not find a way to configure this path, I symlinked the aap executable from the "bin" subdirectory to the "23.0.0_rc1" directory one level higher. This works now.


My issue with aapt got solved by simply chmod a+x platform-tools/aapt


Starting build-tool 23, aapt has been moved under the ./bin directory

waiting for Eclipse ADT to be updated , one can just create a symbolic link to aapt

cd <path_to_your_android_sdk_folder>/build-tools/23.0.0_rc1
ln -s ./bin/aapt aapt

this will create a symlinc


pointing to actual aapt tool laying here


and eclipse will be able to build android project back again :-)


In the terminal execute this command :

chmod a+x platform-tools/aapt

it solved the problem for me

(in 64bit you have to install ia32-libs with this command : sudo apt-get install ia32-libs)


  • Check you have Android SDK version required installed and the path in Eclipse->preferences->android->SDK Location is correct.
  • Check file permissions. Run:

    chmod a+x aapt
  • If you are using Linux 64-bits. You'll see this hint:

    Hint: On 64-bit systems, make sure the 32-bit libraries are installed: sudo apt-get install ia32-libs        line 1  Android ADT Problem

    To fix it, you'll have to install 32-bits libraries:

    sudo apt-get install ia32-libs


    sudo apt-get install lib32z1

    Maybe you'll need to install other libraries (libstdc++6:i386 libgcc1:i386 zlib1g:i386 libncurses5:i386) or the emulator (libsdl1.2debian:i386). In my case it was enough installing libstdc++6

    sudo apt-get install lib32stdc++6

For more information you can check this question: How to resolve Error executing aapt in Android/Eclipse?


The aapt location has been changed recently. You can find it under:



I solved this problem by adding a / after my android-sdk path in...

Eclipse->preferences->android->SDK Location:


I found that this could be fixed by installing the ia32-libs package as the Android sdk requires 32-bit libraries.

Related Query

More Query from same tag