dgzz
dgzz

Reputation: 2999

Execution failed app:processDebugResources Android Studio

I'm using bitbucket so I can work with other developer but it seems that we can't get it to work flawlessly. I got this error after pulling the changes from him:

Execution failed for task ':app:processDebugResources'.
> com.android.ide.common.internal.LoggedErrorException: Failed to run command:
    E:\Program Files (x86)\Android\android-sdk\build-tools\19.0.0\aapt.exe package -f --no-crunch -I E:\Program Files (x86)\Android\android-sdk\platforms\android-19\android.jar -M E:\Documents\smart-my-job1\app\build\manifests\debug\AndroidManifest.xml -S E:\Documents\smart-my-job1\app\build\res\all\debug -A E:\Documents\smart-my-job1\app\build\assets\debug -m -J E:\Documents\smart-my-job1\app\build\source\r\debug -F E:\Documents\smart-my-job1\app\build\libs\app-debug.ap_ --debug-mode --custom-package com.smartmyjob
Error Code:
    -1073741819

Upvotes: 137

Views: 532012

Answers (30)

Shapon Pal
Shapon Pal

Reputation: 1146

Updated October 2022 (React Native 70)

buildToolsVersion = "30.0.3"
minSdkVersion = 24
compileSdkVersion = 31
targetSdkVersion = 31
kotlinVersion = '1.6.21'

Updated source: https://developer.android.com/studio/releases/gradle-plugin#7-3-0

If not work, please check your code.

Tips: You can run your app in android studio the check the build log.

Upvotes: 1

Dan Alboteanu
Dan Alboteanu

Reputation: 10232

for me it was a missing Manifest that was to blame. I created a new module and forgot to add Manifest

Upvotes: 0

Ribaz
Ribaz

Reputation: 676

The problem in my case was in my activity.xml . I had forgotten to add the reference in the beginning of the xml file. For example, I had this code

   <com.huawei.hms.ads.banner.BannerView
            android:id="@+id/hw_banner_view"
            android:layout_width="match_parent"
            android:layout_height="wrap_content"
            android:layout_marginLeft="10dp"
            android:layout_marginRight="10dp"
            android:visibility="visible"
            hwads:adId="testw6vs28auh3" ------------------> THIS NEEDED REFERENCE
            hwads:bannerSize="BANNER_SIZE_360_57"/>

I fixed by adding this

<?xml version="1.0" encoding="utf-8"?>
<RelativeLayout 
    xmlns:android="http://schemas.android.com/apk/res/android"
    xmlns:hwads="http://schemas.android.com/apk/res-auto" --------> ADD THIS

Upvotes: 0

Pavankumar AN
Pavankumar AN

Reputation: 55

This error has a chance of triggering when the API version AVD which you selected is not the same as you specified in Project_folder>android>app>build.gradle as compileSdkVersion and targetSdkVersion.

Earlier my API version was 27 and now it is 30. I have changed the values of the above two parameters to 30 and my problem got solved.

Upvotes: 0

Bartosz546
Bartosz546

Reputation: 105

In my case, I needed to turn off Avast antivirus for a build time. Antivirus was blocking build when it tried to process this file:

platforms\android\app\build\intermediates\runtime_symbol_list\debug\R.txt

Upvotes: 0

Farshid
Farshid

Reputation: 5354

In my case, I changed the android section in build.gradle and the problem faded away:

android {
compileSdkVersion 28

lintOptions {
    disable 'InvalidPackage'
}

defaultConfig {
    // TODO: Specify your own unique Application ID (https://developer.android.com/studio/build/application-id.html).
    applicationId "app.ozel"
    minSdkVersion 16
    targetSdkVersion 28
    versionCode flutterVersionCode.toInteger()
    versionName flutterVersionName
    testInstrumentationRunner "androidx.test.runner.AndroidJUnitRunner"
}

buildTypes {
    release {
        // TODO: Add your own signing config for the release build.
        // Signing with the debug keys for now, so `flutter run --release` works.
        signingConfig signingConfigs.debug
    }
}

}

Upvotes: 0

koteswara D K
koteswara D K

Reputation: 628

it may help in the android studio 3.2.1 app build gradle it should be like

android {
    compileSdkVersion 27
    buildToolsVersion '28.0.3'
    defaultConfig {
        applicationId "com.sample.mvphelloworld"
        minSdkVersion 21
        targetSdkVersion 27
        versionCode 1
        versionName "1.0"
        testInstrumentationRunner "android.support.test.runner.AndroidJUnitRunner"
    }
    buildTypes {
        release {
            minifyEnabled false
            proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro'
        }
    }
}

dependencies {
       implementation fileTree(dir: 'libs', include: ['*.jar'])
       compile 'com.android.support:appcompat-v7:27.1.1'
       implementation 'com.android.support.constraint:constraint-layout:1.1.3'
       testImplementation 'junit:junit:4.12'
       androidTestImplementation 'com.android.support.test:runner:1.0.2'
       androidTestImplementation 'com.android.support.test.espresso:espresso- 
       core:3.0.2'
}

Gradle to 4.6
plugin version to 3.2.1

Upvotes: 2

EdgeDev
EdgeDev

Reputation: 2486

In my case i had two declaration of

<?xml version="1.0" encoding="utf-8"?>

in my vector drawable icon

all i had to do was delete one

Upvotes: 6

CoolMind
CoolMind

Reputation: 28809

In my case several red lines appeared like:

AGPBI: {"kind":"error","text":"error: resource drawable/start_gray_border (aka com.example:drawable/start_gray_border) not found.","sources":[{"file":"C:\\Users\\User\\AndroidStudioProjects\\example\\app\\src\\main\\res\\layout\\activity_start.xml","position":{"startLine":37}}],"original":"","tool":"AAPT"}

I tried gradlew build --stacktrace, rebuild, clean build, checked file names, checked if resources contained invisible symbols, LF, CRLF, changed libraries versions and so on. A problem was in new XML files:

<?xml version="1.0" encoding="utf-8"?><?xml version="1.0" encoding="utf-8"?>
<layer-list xmlns:android="http://schemas.android.com/apk/res/android">
...

Removed a duplicate tag. I understood where a problem is when reverting to previous commit in GIT. After that added several new files and saw what file raises error.

Upvotes: 0

kalpesh
kalpesh

Reputation: 1287

I have removed all folder inside \app\build\ folder and run again it works for me.

E:\AndroidData\mobile-app\AwesomeProject\android\app\build

Upvotes: 1

Md. Ibrahim
Md. Ibrahim

Reputation: 1289

In my Case Problem solved with Instant Run Disable in Android Studio 3.1.2 Android Instant Raun Disable

Upvotes: 3

dirkk0
dirkk0

Reputation: 2570

For me it was that I forgot to install the 32bit dependencies:

sudo apt-get install -y lib32gcc1 libc6-i386 lib32z1 lib32stdc++6
sudo apt-get install -y lib32ncurses5 lib32gomp1 lib32z1-dev lib32bz2-dev

Upvotes: 40

Haider
Haider

Reputation: 189

For me I had to run Android Studio in Admin mode.

Windows 10 x64

Upvotes: 0

Ajith M A
Ajith M A

Reputation: 5348

I stumbled upon this error while updating my Android studio to 3.0.1 from 2.3. After trying all the solutions above, i found that the issue was with the Build tools version. I was using an unsupported version of build tools. I changed mine as below and it worked.

buildToolsVersion '26.0.2'

As a rule of thumb always try to use the latest version of Build tools supported by your Gradle version. From version 3.0.0 of Gradle, you don't need to specify the build tools version as this is picked up automatically.

3.0.0 (October 2017) : Android plugin for Gradle 3.0.0

With this update, you no longer need to specify a version for the build tools—the plugin uses the minimum required version by default. So, you can now remove the android.buildToolsVersion property.

https://developer.android.com/studio/releases/gradle-plugin.html#3-0-0

Upvotes: 0

chenop
chenop

Reputation: 5143

Banged my head around this for 2 days.

TL;DR - Got this error since My app name contained '-'.

Turn out android does not allowed that. After running gradlew build --stacktrace inside android directory - got an error that implies that.

Upvotes: 2

audiebant
audiebant

Reputation: 199

aapt is 32 bit so will not execute on a 64 bit box until 32 bit architecture is enabled

dpkg --print-foreign-architectures  #  if prints nothing then below is fix

sudo dpkg --add-architecture i386  #  add a 32 bit architecture to box

sudo apt-get install -y lib32gcc1 libc6-i386 lib32z1 lib32stdc++6

sudo apt-get install -y lib32ncurses5 lib32gomp1 lib32z1-dev

it work for me.

Upvotes: 18

Radim Vaculik
Radim Vaculik

Reputation: 568

Run gradle with --stacktrace option to see more information, what's wrong.

Upvotes: 2

Nasif Md. Tanjim
Nasif Md. Tanjim

Reputation: 3972

Check if any SDK platform was partially installed. If it does, reinstall it.

Upvotes: 0

mbo
mbo

Reputation: 4701

There may be some errors in your layouts like android:id="@id/ instead of android:id="@+id/.... At least that was the cause for my exception.

Upvotes: 0

user2220771
user2220771

Reputation: 459

If it is not your build tools, check your strings, styles, attrs, ... XML files and ensure they are correct. For example a string with an empty name-attribute

<string name="">Test"</string>

or a previously undefined attr without a format specified (attrs.xml):

<declare-styleable name="MediaGridView">
    <attr name="allowVideo"/>
</declare-styleable>

Upvotes: 2

Akeshwar Jha
Akeshwar Jha

Reputation: 4576

In my case, I cleaned the project (Menubar -> Build -> Clean Project) and then did the build again. It worked.

Upvotes: 9

Ahmad Ayyaz
Ahmad Ayyaz

Reputation: 794

I solved it by changing build tools version 21.0.1 to 20.0.0

Upvotes: 1

Innovation Quotient
Innovation Quotient

Reputation: 1

For me it was an error with my resources, Just changed the resources of my project in resources folder and res folder(i.e. for android) and it worked fine.

Build Successful

Total Time: 1 min 10.034 secs

Upvotes: 0

Pramesh Bajracharya
Pramesh Bajracharya

Reputation: 2263

This worked for me just by restarting android studio 2 times :D. I'm using Android Studio 2.1.

Upvotes: 1

matzahtli
matzahtli

Reputation: 41

I had the same problem, and since this question was the first hit on google, I'll add my solution too. For me, it was a missing format attribute in an attr element in res/values/attrs.xml.

Upvotes: 1

Dhaval Jivani
Dhaval Jivani

Reputation: 9697

I had Same problem and soved by moved

ic_launcher.png files from drawable folder to mipmap folder.

Upvotes: 0

Vaios Stergiopoulos
Vaios Stergiopoulos

Reputation: 1

Had the same problem. I changed the file build.gradle inside the app folder from this: compileSdkVersion 23 buildToolsVersion "23.0.2"

defaultConfig {
    applicationId "com.vastsoftware.family.farmingarea"
    minSdkVersion 11
    targetSdkVersion 23
    versionCode 1
    versionName "1.0"

to this:

compileSdkVersion 23 buildToolsVersion "21.0.2"

defaultConfig {
    applicationId "com.vastsoftware.family.farmingarea"
    minSdkVersion 11
    targetSdkVersion 21
    versionCode 1
    versionName "1.0"

and worked perfectly! hope it works for you too!

Upvotes: 0

AinisSK
AinisSK

Reputation: 306

In my case I tried to change buildToolsVersion in gradle, but it didn't help me. My problem was fixed when I found drawable which called example.PNG. It should be example.png; There were no messages about wrong resource name, but after I renamed file, gradle built project fine.

Upvotes: 2

Chong Chern Dong
Chong Chern Dong

Reputation: 401

I encountered Execution failed app:processDebugResources Android Studio after upgrading SDK repository. I use Android Studio 1.5.1, target SDK version 23. I was using buildToolsVersion 21.0.1 previously, changing buildToolsVersion to 21.1.2 solved my problem.

You might want to how I find version 21.1.2 suitable. It was recommended by Android Studio after successfully upgraded my SDK.

enter image description here

After changing buildToolsVersion to 21.1.2 (refer to my version settings below), you need to synchronize your Gradle build mechanism.

apply plugin: 'com.android.application'

android {
    compileSdkVersion 23
    buildToolsVersion "21.1.2"

    defaultConfig {
        applicationId "mm.weboffice"
        minSdkVersion 14
        targetSdkVersion 23
        versionCode 1
        versionName "1.0"
    }
    buildTypes {
        release {
            minifyEnabled false
            proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro'
        }
    }
}

dependencies {
    compile fileTree(dir: 'libs', include: ['*.jar'])
    compile 'com.android.support:appcompat-v7:23.0.1'
    compile 'com.android.support:cardview-v7:23.0.1'
    compile 'com.android.support:recyclerview-v7:23.0.1'
    compile 'com.android.support:design:23.0.1'
    compile 'com.android.support:support-v4:23.0.1'
}

Android Studio will prompt you to sync Gradle or you can go to "menubar > File > Synchronize" to trigger synchronization manually. Android Studio will rebuild your project after the synchronization.

enter image description here

I know there are many issues with the SDK database and configuration, my proposed solution may not fix all problems. But if you encounter the similar error after upgrading SDK repository, I hope my post solve your hassle. Good luck!

Upvotes: 2

ron shenk
ron shenk

Reputation: 27

Getting this error, I did a build with --info (gradle --info build). It reported that it could not open libz.so.1, due to wrong ELFCLASS. It needs a 32 bit version of libz. I had to download the source, change the Makefile to gcc -m32, and install the 32 bit glibc development package (dnf install glibc-devel.i686). After making and installing this 32 bit library, I disabled the 64 bit one.

Then all went well.

Upvotes: 1

Related Questions