Flaky build failure in MergeResources task [206674992]

Fixed

Bug

Status Update

No update yet.

Description

ku...@gmail.com

created issue #1

Nov 16, 2021 11:23PM

On CI builds we are seeing the following build failure happen occasionally during an incremental build. For example we do a build, then apply a change from a git commit, and build again.

We have enabled the following two properties for making the mergeResources task relocatable which could be the reason from looking at the stacktrace:

android.experimental.enableSourceSetPathsMap=true
android.experimental.cacheCompileLibResources=true

The app module also uses custom res source set locations in case that is relevant:

android.sourceSets { main.res.srcDirs = [ 'src/main/res/foo', 'src/main/res/bar' ] }

Stacktrace:

Task :app:mergeReleaseResources
java.lang.IllegalArgumentException: Unable to locate resourceFile (/.../app/build/intermediates/merged-not-compiled-resources/release/interpolator/mtrl_fast_out_slow_in.xml) in source-sets.
	at com.android.ide.common.resources.RelativeResourceUtils.getRelativeSourceSetPath(RelativeResourceUtils.kt:46)
	at com.android.ide.common.resources.MergedResourceWriter.getSourceFilePath(MergedResourceWriter.java:333)
	at com.android.ide.common.resources.MergedResourceWriter.removeOutFile(MergedResourceWriter.java:755)
	at com.android.ide.common.resources.MergedResourceWriter.removeFileFromNotCompiledOutputDir(MergedResourceWriter.java:723)
	at com.android.ide.common.resources.MergedResourceWriter.removeOutFile(MergedResourceWriter.java:741)
	at com.android.ide.common.resources.MergedResourceWriter.removeItem(MergedResourceWriter.java:448)
	at com.android.ide.common.resources.MergedResourceWriter.removeItem(MergedResourceWriter.java:71)
	at com.android.ide.common.resources.DataMerger.mergeData(DataMerger.java:276)
	at com.android.ide.common.resources.ResourceMerger.mergeData(ResourceMerger.java:385)
	at com.android.build.gradle.tasks.MergeResources.doTaskAction(MergeResources.java:497)
	at com.android.build.gradle.internal.tasks.NewIncrementalTask$taskAction$$inlined$recordTaskAction$1.invoke(BaseTask.kt:66)
	at com.android.build.gradle.internal.tasks.Blocks.recordSpan(Blocks.java:51)
	at com.android.build.gradle.internal.tasks.NewIncrementalTask.taskAction(NewIncrementalTask.kt:45)

Version of Gradle Plugin: 7.0.0

Version of Gradle: Gradle 7.2

Version of Java: 11

OS: centOS

Comments

gh...@google.com <gh...@google.com> Nov 17, 2021 09:05PM

Assigned to an...@google.com.

je...@google.com <je...@google.com> Nov 22, 2021 05:54PM

Reassigned to cm...@google.com.

ku...@gmail.com <ku...@gmail.com> #2Feb 26, 2022 12:38AM

I also have the same issue so it seems to be a real problem.

ga...@google.com <ga...@google.com> #3Aug 23, 2022 11:32AM

Dup here:

http://code.google.com/p/android/issues/detail?id=27959&can=1&q=fixed%20position&colspec=ID%20Type%20Status%20Owner%20Summary%20Stars

Though it's a bit more detailed with the minimum necessary to reproduce.

Message last modified on Aug 23, 2022 11:34AM

inc_res.zip

847 KB

Download

lu...@google.com <lu...@google.com> Aug 23, 2022 11:35AM

Accepted by lu...@google.com.

lu...@google.com <lu...@google.com> #4Aug 23, 2022 01:58PM

why is this marked has Obsolete? this is still a bug that is happening and its difficult to fix.
for all who are looking for a solution use this:

http://stackoverflow.com/questions/16200972/android-css-positionfixed-after-a-device-rotate

lu...@google.com <lu...@google.com> #5Aug 23, 2022 02:37PM

The reason why this appeared to only impact release builds it that the MERGED_NOT_COMPILED_RES is often only only created when resource shrinking is enabled, so was less likely to appear for debug builds.

lu...@google.com <lu...@google.com> Aug 23, 2022 04:39PM

Marked as fixed.

pa...@gmail.com <pa...@gmail.com> #6Mar 7, 2023 03:40PM

What is the fix version on this? I'm still seeing it in 7.4.2 without any experimental flags while trying to run lint, on second time it works fine, but it's really annoying.

kh...@gmail.com <kh...@gmail.com> #7Apr 4, 2023 06:57AM

Comment has been deleted.

Message last modified on Apr 4, 2023 01:42PM

sa...@peilicke.de <sa...@peilicke.de> #8May 25, 2023 07:51AM

In which AGP version has this been fixed? The issue is indeed still present in 7.4.2

lu...@google.com <lu...@google.com> #9May 25, 2023 01:32PM

It appears the fix made it into 8.0, so unfortunately 7.4.2 is still affected.