Android Studio 3.0 - No server to serve request

We ran into the same issue, and have been able to find the root cause: The error message means that Gradle cannot connect to some worker processes. In our case, the process was for 'aapt2'. Running 'ldd aapt2' indicated that some shared libraries were missing (mainly GLIBC). Since we're using Docker based on Alpine Linux, it comes with a reduced GLIBC (glibc-musl). The solution was to simply install glibc in the Docker container.

I suggest you run ldd build-tools/{version}/aapt2 to see which libraries are missing from the OS. You did not mention your OS, are you also using Docker and AlpineLinux ?

Had to uninstall Android studio and delete the following SDK folder in AppData folder Delete .gradle folder delete .AndroidStudio Projects folder

and did a fresh install which solved .

I had this problem on lubuntu-16 32bit (and also some other problems too). all of the problems were solved when I updated my system to lubuntu-16 64-bit.

sudo chmod 777 -R $ANDROID_HOME

Note: $ANDROID_HOME is the location where you put android sdk

Hope this helps !!

If it is possible for you, please delete the build folder of project and test building android project with any other version of build-tools.

in my case, build-tools version: 26.0.2 had problem, I tested with 27.0.3 and it solved my problem unbelievably :)

So after investigating the issue for long , I have a concrete solution . Let`s look into it.

Go to Android Studio -> Help -> Show Log In Files

In the subsequent folder that opens, open idea.log

This would present you with a log file which contains logs of processes right from when the studio started. Now in this file, you have to search for the possible issue. For some the issue might be due to

java.io.IOException: Cannot run program "/home/mmt/Android-Sdk/android-sdk-linux_x86/emulator/emulator-check": error=13, Permission denied

For some others, it may be some other. The point is that this file contains lot of irrelevant logs and you have to identify the one that is causing this issue. For me , after discovering the above issue, I granted permission to that particular folder using the below commands

cd $ANDROID_HOME/sudo chmod -R 777 emulator/

After this, rebuild your project and tadaaa.. problem resolved.

for me it was a virus that corrupted my files from the "build tools" folder. so I uninstalled everything and made a new installation of android studio, SDK and build tools.

For me, this is the side effect of another issue that I haven't root caused yet. Every once in a while, I get aapt2 failures because some file /tmp/ld-linux-x86-64.so.2 is "busy", with the following error message.

AAPT err(Facade for 1745790725): cp: cannot create regular file '/tmp/ld-linux-x86-64.so.2': Text file busy
Slave 1745790725 failed to start java.lang.RuntimeException: AAPT slave failed to start. Please make sure the current build tools (located at ~/.../android-sdk-linux/build-tools/27.0.3/aapt2) are not corrupted.

When this happens I just rm that file and everything starts working again. I suspect this might be caused by me actually having two installs of adb (one through ubuntu via apt and one from Android studio) but I haven't had time to dive deeper.

I already had latest version of build-tool installed, so I just had to give permission to Android_home:

chmod 777 -R $ANDROID_HOME

and build again. This worked for me.

If you are on Windows 10 (sigh), close android studio and then right click on android studio icon and select 'Run as Administrator' from 'more' menu.

Build again.