Android Studio 3.0 - the server does not submit a request

Question

After a clean install of Android Studio, I always get an error

Error: java.util.concurrent.ExecutionException: java.lang.RuntimeException: the server does not request the request. Check the logs for details.

and

Error: execution completed for task ': Application: mergeDebugResources'. Error: java.util.concurrent.ExecutionException: java.lang.RuntimeException: the server does not request the request. Browse magazines for more information.

Java updated and installed path.

I'm new to Android Studio, what should I try?

Answer 1

We ran into the same problem and were able to find the root cause: the error message means that Gradle cannot connect to some workflows. In our case, the process was for 'aapt2'. Running 'ldd aapt2' showed that some shared libraries were missing (mostly GLIBC). Since we use Docker based on Alpine Linux, it comes with 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 specify your OS, do you also use Docker and AlpineLinux?

Answer 2

In my case, I did not need to reload sdk. I closed Android Studio and ran the following command in the terminal:

 sudo chmod 777 -R ~/Desktop/AndroidStudio 

... where ~ / Desktop / AndroidStudio was the folder structure after Root that I needed to mention in order to grant permission to read all SDK packages and perform the required operation as needed in Android Studio, because my Sdk folder was inside "~ / Desktop / AndroidStudio. "

I am running Android Studio 3.0.1 on Ubuntu 16.04 LTS. This worked fine for me :-)

Answer 3

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

and performed a new installation, which was resolved.

Answer 4

This error occurred due to the fact that you accidentally deleted the executable flag from aapt2 , which is located in $ANDROID_HOME/build-tools/27.0.2 .

Try the following:

• Reboot sdk (recommended)

followed by

• sudo chmod 777 -R $ANDROID_HOME

Note: $ANDROID_HOME is where I install android sdk

Hope this helps!

Answer 5

I had this problem on lubuntu-16 32bit (as well as some other problems). all problems were resolved when I upgraded my system to the 64-bit version of lubuntu-16.

Answer 6

Here is how I fixed this problem:

1.Deleted.gradle folder.

2. Closed android studio and runs as administrator.

At the beginning of Android Studio, the deleted folder will be restored.

Answer 7

If possible, delete the project build folder and the Android project project with any other build version.

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

Answer 8

I ran into the same problem and it turned out that I mixed up the file permissions inside the android-sdk folder (more specifically, the android-sdk / build-tools / {version} files), and some binaries lacked permission to execute .

In my case, I just gave x permissions for the corresponding files in this directory, but if you are not sure, I suggest you delete the Android sdk file, completely delete its directory and install it again again.

Answer 9

sudo chmod 777 -R $ ANDROID_HOME

Note: $ ANDROID_HOME is where you put the Android SDK

Hope this helps !!

Answer 10

Therefore, after a long study of the issue, I have a specific solution. Let's take a look at that.

Go to Android Studio → Help → Show Login Files

In the folder that opens, open the idea.log file.

This will give you a log file that contains process logs from the moment the studio starts. Now in this file you should look for possible problems. For some, the problem may be related to

java.io.IOException: cannot start the program "/ home / mmt / Android-Sdk / android-sdk-linux_x86 / emulator / emulator-check": error = 13, permission denied

For some others, this may be some other. The fact is that this file contains many irrelevant logs, and you must identify the one that causes this problem. For me, after discovering the above problem, I gave permission to this particular folder using the following commands

cd $ ANDROID_HOME / sudo chmod -R 777 emulator /

After that, rebuild your project and tadaaa .. the problem is solved.

Answer 11

for me it was a virus that damaged my files from the "build tools" folder. so I uninstalled everything and made a fresh install of Android Studio, SDK and build tools.

Answer 12

For me, this is a side effect of another problem that I have not yet caused. From time to time I get aapt2 errors, because some file /tmp/ld-linux-x86-64.so.2 "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 run this file and everything starts working again. I suspect this may be due to the fact that I actually have two adb installations (one via ubuntu via apt and one from Android studio), but I did not have time to dive deeper.

Answer 13

If you are in Windows 10 (sigh), close android studio and right-click on the android studio icon and select "Run as administrator" in the "more" menu.

Build again.

Answer 14

You can run Android Studio as an administrator.

Hope this helps you.

Do this way:

• Right click
• select "Run as administrator"

Yours faithfully,