Create a new Android Studio 0.2.3 project - Unable to start the Gradle daemon process

I am having serious problems with Android Studio. I completely uninstalled Android Studio and any copies of Eclipse on my PC. Then I deleted the .gradle.android folders in the users folder. Then I reinstalled the latest version on my PC. Updated .gradle and .android folders.

Now I am trying to create a new project. I installed everything normal and then the following error appears:

gradle error message when trying to create new project.

I read a few posts, most of which are for older versions of Android Studio. My SDK is updated, and yes, I have the installed Android 2 support repository, as well as support for the Android Rev 18 library.

Why it should be so complicated that I just do not understand.

Relations Adrian Wrayford

+8
android-studio daemon gradle gradle-daemon
source share
6 answers

Well, I managed to solve this after many hours of trying.

First of all, I use Windows 7 with 16 GB of RAM, and that was the path to the system that was truncated! This left me without the correct GRADLE_HOME path.

I manually downloaded the latest version of Gradle -1.7. Android studio 0.2.3 used 1.6, but subsequently, to my manual fix, 0.2.5 uses Gradle -1.7.

I created a system variable: GRADLE_HOME with a value: D: \ gradle -1.7, which points to my Gradle install guide.

I broke my "real path" (before windows truncated it) into "extended" path variables, thereby reducing my actual path and pasting the following at the end of the path:% GRADLE_HOME% / bin;% JAVA_HOME% / bin;

There are many references to accessing a truncated Windows path in stackoverflow. And that was all it took to get it working.

Hope I can help someone else!

+6
source share

The only way I worked with is to add this line

org.gradle.jvmargs=-Xmx512m -XX:MaxPermSize=512m

to gradle.properties

+10
source share

I got the same error, but the main reason was my online security package. I am using Comodo and I found that a disabled auto sandbox solved the problem.

+4
source share

I solved this problem by moving my Gradle folder to the root of the drive, as I suspected it was some kind of path problem. This did not solve it immediately, but it worked after a reboot.

0
source share

I deleted the projects that were shown when Android Studio started. This fixed this issue for me.

0
source share

I just closed Android Studio, deleted the gradle folder from the Android Studio folder and reopened the studio. He rebuilt it, and now it works great.

0
source share

All Articles