Exception : AAPT2 error: check logs for details

Question

Task :processDebugResources Failed to execute aapt com.android.ide.common.process.ProcessException: Failed to execute aapt
    at com.android.builder.core.AndroidBuilder.processResources(AndroidBuilder.java:796)
    at com.android.build.gradle.tasks.ProcessAndroidResources.invokeAaptForSplit(ProcessAndroidResources.java:551)
    at com.android.build.gradle.tasks.ProcessAndroidResources.doFullTaskAction(ProcessAndroidResources.java:285)
    at com.android.build.gradle.internal.tasks.IncrementalTask.taskAction(IncrementalTask.java:109)
    at sun.reflect.GeneratedMethodAccessor200.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:497)
    at org.gradle.internal.reflect.JavaMethod.invoke(JavaMethod.java:73)
    at org.gradle.api.internal.project.taskfactory.DefaultTaskClassInfoStore$IncrementalTaskAction.doExecute(DefaultTaskClassInfoStore.java:173)
    at org.gradle.api.internal.project.taskfactory.DefaultTaskClassInfoStore$StandardTaskAction.execute(DefaultTaskClassInfoStore.java:134)
    at org.gradle.api.internal.project.taskfactory.DefaultTaskClassInfoStore$StandardTaskAction.execute(DefaultTaskClassInfoStore.java:121)
    at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter$1.run(ExecuteActionsTaskExecuter.java:122)
    at org.gradle.internal.progress.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:336)
    at org.gradle.internal.progress.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:328)
    at org.gradle.internal.progress.DefaultBuildOperationExecutor.execute(DefaultBuildOperationExecutor.java:197)
    at org.gradle.internal.progress.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:107)
    at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeAction(ExecuteActionsTaskExecuter.java:111)
    at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeActions(ExecuteActionsTaskExecuter.java:92)
    at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.execute(ExecuteActionsTaskExecuter.java:70)
    at org.gradle.api.internal.tasks.execution.SkipUpToDateTaskExecuter.execute(SkipUpToDateTaskExecuter.java:63)
    at org.gradle.api.internal.tasks.execution.ResolveTaskOutputCachingStateExecuter.execute(ResolveTaskOutputCachingStateExecuter.java:54)
    at org.gradle.api.internal.tasks.execution.ValidatingTaskExecuter.execute(ValidatingTaskExecuter.java:58)
    at org.gradle.api.internal.tasks.execution.SkipEmptySourceFilesTaskExecuter.execute(SkipEmptySourceFilesTaskExecuter.java:88)
    at org.gradle.api.internal.tasks.execution.ResolveTaskArtifactStateTaskExecuter.execute(ResolveTaskArtifactStateTaskExecuter.java:52)
    at org.gradle.api.internal.tasks.execution.SkipTaskWithNoActionsExecuter.execute(SkipTaskWithNoActionsExecuter.java:52)
    at org.gradle.api.internal.tasks.execution.SkipOnlyIfTaskExecuter.execute(SkipOnlyIfTaskExecuter.java:54)
    at org.gradle.api.internal.tasks.execution.ExecuteAtMostOnceTaskExecuter.execute(ExecuteAtMostOnceTaskExecuter.java:43)
    at org.gradle.api.internal.tasks.execution.CatchExceptionTaskExecuter.execute(CatchExceptionTaskExecuter.java:34)
    at org.gradle.execution.taskgraph.DefaultTaskGraphExecuter$EventFiringTaskWorker$1.run(DefaultTaskGraphExecuter.java:248)
    at org.gradle.internal.progress.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:336)
    at org.gradle.internal.progress.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:328)
    at org.gradle.internal.progress.DefaultBuildOperationExecutor.execute(DefaultBuildOperationExecutor.java:197)
    at org.gradle.internal.progress.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:107)
    at org.gradle.execution.taskgraph.DefaultTaskGraphExecuter$EventFiringTaskWorker.execute(DefaultTaskGraphExecuter.java:241)
    at org.gradle.execution.taskgraph.DefaultTaskGraphExecuter$EventFiringTaskWorker.execute(DefaultTaskGraphExecuter.java:230)
    at org.gradle.execution.taskgraph.DefaultTaskPlanExecutor$TaskExecutorWorker.processTask(DefaultTaskPlanExecutor.java:124)
    at org.gradle.execution.taskgraph.DefaultTaskPlanExecutor$TaskExecutorWorker.access$200(DefaultTaskPlanExecutor.java:80)
    at org.gradle.execution.taskgraph.DefaultTaskPlanExecutor$TaskExecutorWorker$1.execute(DefaultTaskPlanExecutor.java:105)
    at org.gradle.execution.taskgraph.DefaultTaskPlanExecutor$TaskExecutorWorker$1.execute(DefaultTaskPlanExecutor.java:99)
    at org.gradle.execution.taskgraph.DefaultTaskExecutionPlan.execute(DefaultTaskExecutionPlan.java:625)
    at org.gradle.execution.taskgraph.DefaultTaskExecutionPlan.executeWithTask(DefaultTaskExecutionPlan.java:580)
    at org.gradle.execution.taskgraph.DefaultTaskPlanExecutor$TaskExecutorWorker.run(DefaultTaskPlanExecutor.java:99)
    at org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:63)
    at org.gradle.internal.concurrent.ManagedExecutorImpl$1.run(ManagedExecutorImpl.java:46)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
    at org.gradle.internal.concurrent.ThreadFactoryImpl$ManagedThreadRunnable.run(ThreadFactoryImpl.java:55)
    at java.lang.Thread.run(Thread.java:745) Caused by: java.util.concurrent.ExecutionException: java.util.concurrent.ExecutionException: com.android.tools.aapt2.Aapt2Exception: AAPT2 error: check logs for details
    at com.google.common.util.concurrent.AbstractFuture.getDoneValue(AbstractFuture.java:503)
    at com.google.common.util.concurrent.AbstractFuture.get(AbstractFuture.java:482)
    at com.google.common.util.concurrent.AbstractFuture$TrustedFuture.get(AbstractFuture.java:79)
    at com.android.builder.core.AndroidBuilder.processResources(AndroidBuilder.java:794)
    ... 47 more Caused by: java.util.concurrent.ExecutionException: com.android.tools.aapt2.Aapt2Exception: AAPT2 error: check logs for details
    at com.google.common.util.concurrent.AbstractFuture.getDoneValue(AbstractFuture.java:503)
    at com.google.common.util.concurrent.AbstractFuture.get(AbstractFuture.java:462)
    at com.google.common.util.concurrent.AbstractFuture$TrustedFuture.get(AbstractFuture.java:79)
    at com.android.builder.internal.aapt.v2.QueueableAapt2.lambda$makeValidatedPackage$1(QueueableAapt2.java:179)
    at com.android.builder.internal.aapt.v2.QueueableAapt2$$Lambda$489/579799618.run(Unknown Source)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
    ... 1 more Caused by: com.android.tools.aapt2.Aapt2Exception: AAPT2 error: check logs for details
    at com.android.builder.png.AaptProcess$NotifierProcessOutput.handleOutput(AaptProcess.java:454)
    at com.android.builder.png.AaptProcess$NotifierProcessOutput.err(AaptProcess.java:411)
    at com.android.builder.png.AaptProcess$ProcessOutputFacade.err(AaptProcess.java:332)
    at com.android.utils.GrabProcessOutput$1.run(GrabProcessOutput.java:104)

Where will the AAPT2 logs be saved? While migrating to gradle-plugin-3.0.0, I am getting this exception.

The errors should be just above the stacktrace. If you're running from Android Studio you can find the full log in the Gradle Log window. — Izabela Orlowska, Dec 04 '17 at 13:16
https://stackoverflow.com/a/47941174/8818381 ***Akhilesh Awasthi*** answer was correct for me. I've examine my xml file and find out that in one of TextView I've set `android:layout_height="20"` without `'dp'`. Don't know why, but in *Android Studio 3.1 Canary 6* if you edit in Designer tool your UI units didn't add in xml. This may be bug of Canary version. Try to carefully examine all elements in your recently edited xmls — Andrew Son, Dec 27 '17 at 12:43

score 172 · Accepted Answer · edited Nov 19 '19 at 12:59

172

I ran into this very issue today morning and found the solution for it too. This issue is created when you have messed up one of your .xml files. I'll suggest you go through them one by one and look for recent changes made. It might be caused by a silly mistake.

In my case, I accidentally hardcoded a color string as #FFFFF(Bad practice, I know). As you can see it had 5 F instead of 6. It didn't show any warning but was the root of the same issue as encountered by you.

Edit 1: Another thing you can do is to run assembleDebug in your gradle console. It will find the specific line for you.

Edit 2: Adding an image for reference to run assembleDebug.

edited Nov 19 '19 at 12:59

Georgios

3,317
24
38

answered Dec 22 '17 at 11:59

Akhilesh Awasthi

2,603
4
18
30

1

Thank you so much, i almost get crazy with this silly bug. In my case was style="@style/?android:attr/progressBarStyle" The editor added the (@style/) before the style. – Jorge Vieira Jan 05 '18 at 23:51
That's just terrifying - I have a huge project I need to run. I mean HUGE - not less than 200 xmls and the resolution seems to be checking files by hand... Jeez! :( – AlexeyGorovoy Feb 07 '18 at 13:39
2

The solution suggested in the EDIT helped me to find the issue, thanks. – ocramot Apr 23 '18 at 09:09
1

How to do assembleDebug in Gradle console – Srini Jun 04 '18 at 06:51
@Srini I have added an image in answer for reference. Hope it helps. – Akhilesh Awasthi Jun 04 '18 at 06:57
3

mate, you're a gem for adding that image. I wish all developers had your communication skills – bharal Aug 17 '18 at 20:56
1

When I updated to Android Studio 3.2, I've had this error "> Error: java.util.concurrent.ExecutionException: com.android.builder.internal.aapt.v2.Aapt2Exception: AAPT2 error: check logs for details" When I executed the assembleDebug command, an error was displayed because Crashlytics was not updated. Thanks for the tip ! – MickaCapi Sep 25 '18 at 14:43
1

**-gradlew assembleDebug** was a golden tip. thanks sir – DNA.h Oct 24 '18 at 13:04
1

great! assembleDebug show which xml file and line has problem. – Saeed Arianmanesh Nov 03 '18 at 12:46
1

Thank you for mentioning assembleDebug task! Spent almost whole day dealing with this bug. – AnteGemini Nov 06 '18 at 16:16
1

Bless you sir. There was way i could have found this by searching one by one – Syed Muhammad Oan Nov 10 '18 at 09:32
1

In my case, it was the PNG image files which I had edited externally using Gimp. These images were being used as state indicators on a toggle button. – Hashim Akhtar Nov 23 '18 at 19:39
1

saved the day hats off problem was in my xml – Java Nerd Jan 02 '19 at 13:17
1

greate and best answer thambs up – Muhammad Ashfaq Feb 20 '19 at 11:56
1

I also felt it was one of my bad xml commits that caused this error, after I reverted the commit the error was gone. – MG Developer May 20 '19 at 01:44
1

I had the same error thank you a lot. I was so scared that I did something wrong but you are a life saver – Kwnstantinos Nikoloutsos May 31 '19 at 13:25

Prince Dholakiya · Answer 2 · 2020-06-07T05:21:02.203

AAPT2 Error solution.

If your Android studio has been updated.

Maybe, you would face an error in the studio like "AAPT 2 error: check the log for details"

This error will occur when you have done something wrong in your .xml file such as incorrect value, content not found, etc.

But, At that time you will not have the error specification there. Because the new version of Android Studio does not give you a specific error. It gives like AAPT2 error.

If you want to know where the actual error is then

Follow step.

Look at the panel which is at the right of your Android studio Check out the "Gradle" tab and click on it.

You will see the "app" option. Click on it.

In the app options you will see [Tasks -> build] click on it.

Then you will get options list and see "assembleDebug" double click on it.

Keep the patience and See build tab at the bottom panel of Android studios, you will get an exact error there what you made a mistake in which file and which position.

Thank you dude..actually I has been looking for this quick solution from so many days — venu46, Aug 23 '19 at 06:17

score 12 · Answer 3 · answered May 10 '18 at 17:46

12

The error might be cause by non-ASCII symbols in gradle path. E.g. cyrillic symbols of the user folder. So, the problem is solved just by switching to another directory with ASCII-only path.

answered May 10 '18 at 17:46

Dmitry Nevzorov

435
6
14

How did you find that? This is ridiculous. – Sergio Jun 17 '19 at 16:49
@Sergio just because I faced the problem: as many cyrillic-reading users I had a Windows user named in cyrillic alphabet. A default gradle folder was placed inside a user folder, so, an error occured. – Dmitry Nevzorov Jun 18 '19 at 11:48
1

I have a user folder with accented vowels in Portuguese, and I was getting this AAPT error. Bould never tell it was about gradle folder. – Sergio Jun 18 '19 at 19:30

score 8 · Answer 4 · answered Sep 05 '18 at 15:52

8

Just add this line as per your compileSdkVersion

buildToolsVersion "27.0.3"

answered Sep 05 '18 at 15:52

Mayur Sojitra

656
6
15

score 5 · Answer 5 · answered Apr 25 '18 at 13:23

5

I fixed the ERROR with three steps
1. I checked for the problem SOURCE
2. Provided the correct string/text, because it was the CAUSE
3. I cleaned the project, you ll see it under BUILD.

answered Apr 25 '18 at 13:23

Bukunmi

1,718
12
10

score 4 · Answer 6 · answered Apr 10 '18 at 23:27

4

You have a problem with a png file maybe, look here :

1 more Caused by: com.android.tools.aapt2.Aapt2Exception: AAPT2 error: check logs for details at com.android.builder.png.AaptProcess$NotifierProcessOutput.handleOutput(AaptProcess.java:454)

It can be corrupted image or jpeg image with png extension

answered Apr 10 '18 at 23:27

nasser

193
6

1

this actually save me. I had used an image generator that made some 9 patch images and copied those into place. that cause this similar error that had absolutely no other indication that it was an image causing the issue. and assembleDebug provided no other indication of error. – AtomRiot Apr 18 '18 at 05:09

score 3 · Answer 7 · edited Apr 06 '18 at 12:07

3

Check the latest edited XML file. It is the main Villian I had once such error, I then checked the last xml file, ther was a line like android:layout_marginTop="." I changed it to android:layout_marginTop="16dp". That fixed the bug!

edited Apr 06 '18 at 12:07

ColdFire

6,116
6
32
50

answered Mar 16 '18 at 11:37

Mohith7548

896
2
10
19

mohammed nathar · Answer 8 · 2018-05-04T06:23:05.337

I faced similar problem. Akilesh awasthi's answer helped me fix it. My problem was a little different. I was using places_ic_search icon from com.google.android.gms:play-services-location The latest version com.google.android.gms:play-services-location:15.0.0 does not provide the icon places_ic_search. Because of this there was a problem in the layout.xml files.That led to build failure AAPT2 error: check logs for details as the message. Android studio should be showing cannot find drawable places_ic_search as the message instead.

I ended up using a lower version of com.google.android.gms:play-services-location temporarily. Hope this helps someone in future.

score 3 · Answer 9 · answered Aug 17 '18 at 07:26

I made a stupid mistake. In my case, I made the project path too deep. Like this: C:\Users\Administrator\Desktop\Intsig_Android_BCRSDK_AndAS_V1.11.18_20180719\Intsig_Android_BCRScanSDK_AndAS_V1.10.1.20180711\project\as\AS_BcrScanCallerSvn2

Please migrate the project to the correct workspace. Hope this helps someone in future.

score 3 · Answer 10 · answered Jan 15 '19 at 19:28

If you are getting this error only when you are generating signed Apk . Then the problem might be in one or more of the imported media file format. I have used an image directly from net to studio and was not able to generate sign apk, then found the error .

from Gradle >assembleRelease then got the error in console. see the error log in console image.

score 3 · Answer 11 · answered Feb 11 '19 at 09:48

3

Ensure if no image in drawable folder is corrupted.

answered Feb 11 '19 at 09:48

bikram

3,748
29
39

score 2 · Answer 12 · answered Jan 30 '19 at 07:02

2

I tried every possible solution to fix this frustrating error and only below worked for me. In your build.gradle add this:

android {
    aaptOptions.cruncherEnabled = false
    aaptOptions.useNewCruncher = false  }

answered Jan 30 '19 at 07:02

Andrain

659
1
13
36

score 1 · Answer 13 · answered Jul 31 '18 at 11:30

1

Just in case above solution did not work. In my case , Bitdefender Antivirus was Preventing AAPT2 from making change on certain file.

answered Jul 31 '18 at 11:30

solidfox

573
1
6
20

score 1 · Answer 14 · edited Sep 21 '18 at 13:02

1

For me, I got this error while working on some Udacity projects. I fixed it by adding the following code to the top-level build.gradle file.

allprojects {
    String osName = System.getProperty("os.name").toLowerCase()
    if (osName.contains("windows")) {
        buildDir = "C:/tmp/${rootProject.name}/${project.name}"
    }
    repositories {
        jcenter()
        google()
    }
}

edited Sep 21 '18 at 13:02

Gert Kommer

1,089
2
23
44

answered Sep 21 '18 at 11:54

Beast77

150
1
15

score 1 · Answer 15 · answered Dec 05 '18 at 20:33

If you are seeking a way to get to the heart of the issue. Android studio contains a feature within the edit configurations panel that simplifies this possible. By clicking on the "app" tag (It is typically to the left of the top run button)

You will open the option to edit configurations. From there create an instance of the gradle option to yourself.

The core features are actually the gradle project as well as the task. Connect the task to your debug initiative.

When you run your app through this setting, Android will spit out detailed errors(That we all wish would appear more often) and these errros will point directly a what needs to be resolved.

score 1 · Answer 16 · answered Aug 01 '19 at 23:45

I had this error and no meaningful message to tell me what was wrong. I finally removed this line from gradle.properties and got a meaningful error message.

android.enableAapt2=false

In my case somebody on the team had changed a .jpg extension to a .png and the file header didn't match the extension. Fun.

score 0 · Answer 17 · answered Aug 23 '19 at 21:41

0

style="?android:attr/android:progressBarStyleSmall"

to

style="?android:attr/progressBarStyleSmall"

answered Aug 23 '19 at 21:41

tricknology

933
1
14
26

score 0 · Answer 18 · answered Sep 11 '19 at 07:34

0

I was also getting same error because of using & character directly in layout xml. So, please be careful about using html entities in your project.

answered Sep 11 '19 at 07:34

Avijit

995
10
20

score 0 · Answer 19 · answered Dec 22 '19 at 12:08

0

someone might get some help from my case I just put a hard coded color hex value without # like this by mistake android:textColor="FFA500" almost made me mad to findout. #FFA500 this solved my issue

answered Dec 22 '19 at 12:08

Mithu

581
5
25

score 0 · Answer 20 · answered Jan 31 '20 at 23:27

Seeing your logs :

at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) ... 1 more Caused by: com.android.tools.aapt2.Aapt2Exception: AAPT2 error: check logs for details at com.android.builder.png.AaptProcess$NotifierProcessOutput.handleOutput(AaptProcess.java:454) at com.android.builder.png.AaptProcess$NotifierProcessOutput.err(AaptProcess.java:411) at com.android.builder.png.AaptProcess$ProcessOutputFacade.err(AaptProcess.java:332) at com.android.utils.GrabProcessOutput$1.run(GrabProcessOutput.java:104)

I feel some PNG files are corrupted and were not parsed. Sometimes the images have an extension but are not real PNG.

You can check if the images in your project are real PNGs with the below command :

find . -type f -name "*.png" | xargs -L 1 -I{} file  -I {} | grep -v 'image/png; charset=binary$'

After getting the list use this site to convert them to PNG. Then check your build again.

score 0 · Answer 21 · answered May 10 '21 at 21:05

this problem mostly about related xml typo mistakes, for me i just changed

       <EditText
        android:layout_width="match_parent"
        android:layout_height="40dp"
        android:hint="@string/str_search"
        android:background="@android:color/transparent"
        android:paddingLeft="10dp"/>

android:background="null"

to

android:background="@android:color/transparent"

score -1 · Answer 22 · answered Feb 05 '18 at 09:09

-1

possible issue related to this can be with your XML files. I have faced this when I deleted my unnecery xml files.

For remedy from this error in gradle.properties of the module, add this below line:

android.enableAapt2=false

after adding this line, restart the gradle.

and do once clean, rebuild your project.

answered Feb 05 '18 at 09:09

amit pandya

1,174
11
20

3

`android.enableAapt2=false` is deprecated, and will be removed by the end of 2018, so this doesn't solve the problem, is just a temporary workaround. – Henrique César Madeira Apr 03 '18 at 15:23

score -1 · Answer 23 · answered Oct 12 '18 at 18:36

This resolved the issue for me... Build|Clean project Refactor|Remove unused resources I am still a beginner at this so I cannot explain why this might have worked. It was an arbitrary choice on my part; it was simple, did not require detailed changes and I just thought it might help :)

yaoyue1019 · Answer 24 · 2018-05-02T13:00:44.483

-3

some symbols should be transferred like '%'

<string name="test" formatted="false">95%</string>

edited May 02 '18 at 13:00

answered May 02 '18 at 09:52

yaoyue1019

177
4

Exception : AAPT2 error: check logs for details

24 Answers24

AAPT2 Error solution.

Follow step.

Linked