Android java.exe finished with non-zero exit value 1 [closed]

Answer 1

In my case setting Java Max Heap Size from 2g to 1g worked.

Add following to application module's build.gradle file

android {
    dexOptions {
        javaMaxHeapSize "1g"
    }
}

Answer 2

I've had the same issue just now, and it turned out to be caused by a faulty attrs.xml file in one of my modules. The file initially had two stylable attributes for one of my custom views, but I had deleted one when it turned out I no longer needed it. This was apparently, however, not registered correctly with the IDE and so the build failed when it couldn't find the attribute.

The solution for me was to re-add the attribute, run a clean project after which the build succeeded and I could succesfully remove the attribute again without any further problems.

Hope this helps someone.

Answer 3

All you need to do is to kill some of the running process and free the space on your Memory(RAM). You can try closing some of the high memory consuming program. You can also try restarting the Android Studio. It worked for me.

Answer 4

For me this works:

defaultConfig {
    multiDexEnabled true
}

Answer 5

Solution

1.Just clean the project and check its working or not

2.Just Restart android studio after closing all the rubbish tasks

3.If both the above things not working add this in gradle.build file

android {

    dexOptions {
        incremental = true;
        preDexLibraries = false
        javaMaxHeapSize "4g" 
    }

}

Answer 6

After adding a jar file to a project's lib folder and after adding it to the build.gradle file as compile'path example' when you sync the gradle it add an additional line as compile files('libs/example.jar'). You just need to remove the line you previously added to the build.gradle file i.e. the compile'path example' after the gradle sync. You also need to remove the line compile fileTree(dir: 'libs', include: '*.jar')