finished with non zero exit value

AndroidAndroid Gradle-Plugin

Android Problem Overview


I am trying to import my project. but when I run the application I am getting the following error:

Error: Execution failed for task ':app:processDebugResources'.
 > com.android.ide.common.process.ProcessException:      
   org.gradle.process.internal.ExecException: Process 'command 'C:\Users\Vishnu  Ruhela\AppData\Local\Android\sdk\build-tools\21.1.2\aapt.exe'' finished with non- zero exit value 1

here is my gradle file

apply plugin: 'com.android.application'

android {
    compileSdkVersion 21
    buildToolsVersion "21.1.2"
    defaultConfig {
        applicationId "com.example.vishnuruhela.signup"
        minSdkVersion 15
        targetSdkVersion 21
        versionCode 1
        versionName "1.0"
    }
    buildTypes {
        release {
            minifyEnabled true
            proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro'
        }
    }
    productFlavors { }
}

dependencies {
    compile fileTree(dir: 'libs', include: ['*.jar'])
    compile 'com.android.support:appcompat-v7:21.0.3'
    compile project(':listView1')
}

Android Solutions


Solution 1 - Android

I was getting this exact same error. I ran the command

./gradlew assembleDebug --info

Where "assembleDebug" was replaced with the assemble task for a debug version of the flavor I wanted.

Look for output

> Successfully started process 'command '/usr/local/opt/android-sdk/build-tools/21.1.2/aapt''

Right below that was an error describing a resource which I used in a layout file but which was missing from the dimensions files. Fixing this fixed the build issue.

Solution 2 - Android

At first you go to

Build -> Clean Project 

and then go to

Build -> Rebuild Project

and finish the error is a way

Solution 3 - Android

Install the latest version of the build tools. Adjust your build.gradle to use

android {
    compileSdkVersion {X}
    buildToolsVersion "{X.Y.Z}"
   ...
}

Proper values should match your installed SDK. Could be 23.0.3 at the time of this post.
or check and remove duplicate dependencies from list.

Enjoy :)

Solution 4 - Android

Follow this simple steps to recover this error:

Method 1:

-Go to File->project structure->Project
-Check Android plugin Version and change it to 1.3.0(Latest one)
-Go to File->project structure->app->Properties->Build Tools Version
-Change it to latest one(22.0.1). Also do this for any other module you have for your project.
-Clean and build project.

Note: If your build tool version is less than 22.0.1 then you may still face same error while gradle build so please update your SDK from SDK Manager to latest one then restart android studio and follow above steps.

Method 2:

-If you don't want to update build tools version or you don't have latest SDK version just Go to File->project structure->Project.
-Check Android plugin Version and change it to 1.0.0(Older one)
-Clean and build project.

I recommended Method 1.

Solution 5 - Android

I had the same problem after replacing some .png image resources with .jpg pictures.

I deleted appname/app/build, than I selected Build -> Rebuild project and finally it worked without any errors.

Solution 6 - Android

In my case, answers of taciosd and Netero pointed in the correct direction. By analyzing:

gradle assembleDebug --stacktrace --debug 

Linux:

./gradlew assembleDebug --stacktrace --debug

i found out that one filepath in the assets folder was too long and aapt.exe stopped by returning 1 (and no specific error message) when processing that file. It seems that files with non ASCII characters in names are not accepted as well.

Solution 7 - Android

I had this same exact error all of a sudden the other day. I did a "Clean Project" and a "Rebuild Project" and never saw the error again.

I've only got a few months of Android development under my belt. But whenever I get an unexplained error like this, "Clean Project" and/or "Rebuild Project" are the first things I try.

Solution 8 - Android

i had the same problem i resolve it by removing files that i added in the assets folder and those files name contains insupported characteres like "é" , " ", "ï" "è"... by renaming those name files or removing them you will have no problem.

Solution 9 - Android

BuildToolsVersion & Dependencies must be same with Base API version.

buildToolsVersion '23.0.2' & compile 

&

com.android.support:appcompat-v7:24.0.0-alpha1

can not match with base API level.

It should be

compile 'com.android.support:appcompat-v7:21.0.3'

Done

Solution 10 - Android

Errors in the execution of aapt in task processDebugResources or processReleaseResources generally happen when one or more resources of your project are unsupported.

To find out go to the root dir of your project and run:

gradle processDebugResources --debug

This will print aapt specific error. In my case it was a file in the assets folder whose name had invalid character (LEÃO.jpg). aapt doesn't support some characters in the Latin alphabet.

But, as I explained your problem can be other than that. To know for sure you have to run processDebugResources with the option --debug.

Solution 11 - Android

I have faced the same error while compiling. I tried all the methods here but failed only one thing worked but it takes a lot of time. by running this code on CMD to debug my app and shows me the missing tag in my XML layout.

gradle processDebugResources --debug

The best approach is to analyze the error not just ignoring it.

To run this code I installed Java JDK and then set Environment Variable: for JAVA_HOME and Gradle.

for gradle

C:\Program Files\Android\Android Studio\gradle\gradle-4.6\bin

for java

JAVA_HOME=C:\Program Files\Java\jre1.8.0_191

Solution 12 - Android

You have to do the following instructions :

Click on Build located in the toolbar, then

Clean project -> Rebuild Project

Solution 13 - Android

enter image description here

Please make sure that compileSdkVersion, buildToolsVersion and targetSdkVersion have the same version number. I also have this error because it has different version. This solution worked for me.

I hope it can help you all.

Solution 14 - Android

when our code has layout.xml file error ,we get this error message. Check your xml files again.

Solution 15 - Android

look through your styles.xml files for a @+id/ I had one in styles.xml in values-v17 which I don't recall creating. This is what I had to change in the end and not build tools 21.1.2 to 22.0.1 as suggested.

Solution 16 - Android

I also had the same error with my images .. Just rename the extension from ".png" or whatever you have to ".jpg"

Solution 17 - Android

I had the same problem.

Try renaming the files in assets folder with characters other than alphabets, numbers and underlines.

Specially, look for apostrophes and European alphabets not common in English.

Solution 18 - Android

I build with command:

./gradlew build --info

It show more error message, my problem is there is special characters in the file name.

Solution 19 - Android

I too was facing this issue just because i had renamed my project folder while project was opened in Android Sudio.So,Android Studio created another folder in that directory of my window.

I found in my build.gradle(Module:app), all the support libraries were updated and was throwing error on compile time of project.

All you require to do is,simply change updated support libraries to your current build tool version like this and rebuild the project.

compile 'com.android.support:appcompat-v7:22.2.1'
compile 'com.android.support:design:22.2.1'
compile 'com.android.support:cardview-v7:22.2.1'

> my current build tool version is 22.2.1

Solution 20 - Android

When i replace the images in project then i get this issue. Then i found that one of the image was having extension .PNG then i rename it to .png then my issue was resolved. Hope it helps you

Solution 21 - Android

I had this same problem, and it only went away after a removed the .gradle folder from my project's root.

So make sure you:

  1. Close the project in Android Studio
  2. Open your file explorer, find the project's root directory
  3. Completely remove the folder .gradle

I hope this helps. Good luck!

Solution 22 - Android

I was also getting this issue.

  • I generally face this issue when I import some sample or already existing module into my project.
  • I just added latest v7 and v4 to my project from maven in android studio and got it fixed
  • Removed duplicate dependencies from project like wise if your library project and application project are using v7 or v4 or any other library , they should be of same version. or try to have it only in your library project

Solution 23 - Android

I had the same problem. Even JPG files did not work. Put all your image files into mipmap and work. They work perfectly.

Solution 24 - Android

I ran to same problem today and try to clean and rebuild project.

I did not solve my problem. I got it solved with change the compileSdkVersion, buildToolsVersion, targetSdkVersion and com.android.support:appcompat-v7:23.0.1 values instead on my Gradle app file. Then I ran clean and rebuild the project afterwards.

Solution 25 - Android

For return value 3 "OutOfMemory exception" i added following in gradle android section

android {
............
dexOptions {
    incremental = true;
    preDexLibraries = false
    javaMaxHeapSize "4g" // 2g should be also OK
}
............
}

And for 2nd issue with return value 2, earlier i had following in gradle dependencies for JDK 7

compile 'com.android.support:appcompat-v7:+'
compile 'com.google.android.gms:play-services:7+'
compile 'com.facebook.android:facebook-android-sdk:+'
compile 'com.android.support:recyclerview-v7:+'
compile 'com.android.support:support-v4:+'

Then i updated my JDK to 8 and it started to give me error (probably for jdk 8 there were more than one libs available with 7+ ) while running the application. What fixed my issue is giving specific version instead of 7+. i.e.

compile 'com.android.support:appcompat-v7:23.1.0'
compile 'com.google.android.gms:play-services:8.1.0'
compile 'com.facebook.android:facebook-android-sdk:4.7.0'
compile 'com.android.support:recyclerview-v7:23.1.0'
compile 'com.android.support:support-v4:23.1.0'

Solution 26 - Android

In my case, I had to install "libz.so.1" library to make it work, on Ubuntu 15.04

sudo apt-get install lib32z1

Solution 27 - Android

Error:Execution failed for task com.android.ide.common.process.ProcessException: org.gradle.process.internal.ExecException:

finished with non-zero exit value 1 One reason for this error to occure is that the file path to a resource file is to long:

Error: File path too long on Windows, keep below 240 characters

Fix: Move your project folder closer to the root of your disk

Don't:// folder/folder/folder/folder/very_long_folder_name/MyProject...

Do://folder/short_name/MyProject

Another reason could be duplicated resources or name spaces

Example:

<style name="MyButton" parent="android:Widget.Button">
      <item name="android:textColor">@color/accent_color</item>
      <item name="android:textColor">#000000</item>
  </style>

Solution 28 - Android

In my case this error was caused by empty layout xml file.

I created the empty file but forgot to add any content to it. AndroidStudio gave this misleading error message, but when I executed the gradle build from command line I could see the real error like "Error parsing XML: no element found" and the file name.

Adding basic layout xml content fixed the error.

Solution 29 - Android

look the compileSdkVersion at android/biuld.gradle ,and compileSdkVersion in all other packages should be the same.

Solution 30 - Android

just for the record. I followed all clean/rebuild and update SDK-Tools here, but in the end it turned out disable Instant Run, to solve my issue.

Go to: Android Studio -> Preferences -> Build,ExecutionDeployment -> Instant Run

Solution 31 - Android

Make sure you choose to build a variant as 'Release' on Android Studio.

enter image description here

Solution 32 - Android

Please make sure your gradle build your compileSdkVersion has its sdk installed in your project. Then just reload your project everything should be fine.

Solution 33 - Android

Looks like it could be caused by different root causes. While in my case, it's caused by "Windows OS cannot handle the path which is too long", so the "aapt.exe" reported that error message:

http://start-coding.blogspot.com/2015/07/android-development-in-windows-using.html

Solution 34 - Android

Make sure that your min/targetSdkVersions are the same in build.gradle and manifest (if exist). Also check for buildToolsVersion in all your modules - it must be the same.

Solution 35 - Android

just solved this issues with moving the project to a shorter path. It can happen if you exceed the Windows max path length

Solution 36 - Android

Under Centos7 64 bit the issue is that some 32 bit libraries did not exist. To fix this I need to add:

yum install glibc.i686
yum install zlib.i686
yum install libstdc++.i686

Solution 37 - Android

For anyone who is trying to use the NDK for the first time, install the NDK via Android Studio's SDK Manager. After I did that the error went away.

Previously I had been following other tutorials/posts that just said to download the NDK yourself, but no one said where to put it. Letting Android Studio handle it fixed the error and allowed my app to launch.

Solution 38 - Android

its been a while but hope it helps

For me it was just something missing from @dimens which was used in xml file it was weird that android studio didn't mention it directly in error

Solution 39 - Android

build from command line with --debug (gradlew build --debug).

look for error near end.

Solution 40 - Android

I had the same problem when writing layout file, after I deleted these two lines:

android:layout_marginLeft="@dimen/activity_horizontal_margin"
android:layout_marginRight="@dimen/activity_horizontal_margin"

the errors were gone.

Solution 41 - Android

1)100% working solution is

step 1) go buid option in menubar step 2) clean build step 3) rebuild it

sucessfully get it guys enter image description here

Solution 42 - Android

Just Make The Changes in The main/AndroidManifest.xml file. check for the tags and the values supplied i did this and all errors were removed

Attributions

All content for this solution is sourced from the original question on Stackoverflow.

The content on this page is licensed under the Attribution-ShareAlike 4.0 International (CC BY-SA 4.0) license.

Content TypeOriginal AuthorOriginal Content on Stackoverflow
QuestionAnkur1994aView Question on Stackoverflow
Solution 1 - AndroidlaochivView Answer on Stackoverflow
Solution 2 - AndroidNucleic ElectronView Answer on Stackoverflow
Solution 3 - AndroidRaRaView Answer on Stackoverflow
Solution 4 - AndroidPranavView Answer on Stackoverflow
Solution 5 - Androidaj18View Answer on Stackoverflow
Solution 6 - AndroidvasquezView Answer on Stackoverflow
Solution 7 - AndroidJoe ZView Answer on Stackoverflow
Solution 8 - AndroidNeteroView Answer on Stackoverflow
Solution 9 - AndroidHiren PatelView Answer on Stackoverflow
Solution 10 - AndroidtaciosdView Answer on Stackoverflow
Solution 11 - Androidsyed shahView Answer on Stackoverflow
Solution 12 - Androiduser5242993View Answer on Stackoverflow
Solution 13 - AndroidChivornView Answer on Stackoverflow
Solution 14 - AndroidozanurkanView Answer on Stackoverflow
Solution 15 - AndroidmushcraftView Answer on Stackoverflow
Solution 16 - AndroidgyadavView Answer on Stackoverflow
Solution 17 - AndroidHamid BagherniaView Answer on Stackoverflow
Solution 18 - AndroidMichael JiangView Answer on Stackoverflow
Solution 19 - AndroidFatal ExceptionView Answer on Stackoverflow
Solution 20 - AndroidPatrickView Answer on Stackoverflow
Solution 21 - AndroidAlexandre BodiView Answer on Stackoverflow
Solution 22 - AndroidDeltaCap019View Answer on Stackoverflow
Solution 23 - AndroidSahithyaView Answer on Stackoverflow
Solution 24 - AndroidAnakinSkywalkerView Answer on Stackoverflow
Solution 25 - AndroidAdeemView Answer on Stackoverflow
Solution 26 - AndroidagustinaliagacView Answer on Stackoverflow
Solution 27 - Androiduser5792272View Answer on Stackoverflow
Solution 28 - AndroidJedi-PhilosopherView Answer on Stackoverflow
Solution 29 - AndroidGovanView Answer on Stackoverflow
Solution 30 - AndroidlongiView Answer on Stackoverflow
Solution 31 - AndroidAravinView Answer on Stackoverflow
Solution 32 - AndroidRalphkayView Answer on Stackoverflow
Solution 33 - Androidgan garyView Answer on Stackoverflow
Solution 34 - AndroidAlexanderView Answer on Stackoverflow
Solution 35 - AndroidMarshistahView Answer on Stackoverflow
Solution 36 - AndroidtheINtoyView Answer on Stackoverflow
Solution 37 - Androidbrutal11View Answer on Stackoverflow
Solution 38 - AndroidiDeveloperView Answer on Stackoverflow
Solution 39 - AndroidLassi KinnunenView Answer on Stackoverflow
Solution 40 - AndroidxmkidView Answer on Stackoverflow
Solution 41 - AndroidMuraliView Answer on Stackoverflow
Solution 42 - AndroidAbhishek BaghelView Answer on Stackoverflow