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

Thanks for the report. I will route this to the appropriate internal team and update this when I hear back from them.

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

One more detail, Data Layer event calls from the watch to the phone (running Android 13) do work on if the listener is in an Activity or Fragment.

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

Also, I'm seeing this message in the Logcat:

"2022-06-12 18:47:15.156 1841-4562/? W/PackageManager: Intent does not match component's intent filter: Intent { act=com.google.android.gms.wearable.BIND_LISTENER"

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

Experiencing the same issues, please see my other report for any useful logs:

https://issuetracker.google.com/issues/235673375

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

+1, can confirm it doesn't work on Android 13:=

2022-07-15 11:26:15.023   589-5347  PackageManager          pid-589                              W  Intent does not match component's intent filter: Intent { act=com.google.android.gms.wearable.BIND_LISTENER cmp=xxx/xxx.WatchMessageReceiver }
2022-07-15 11:26:15.023   589-5347  PackageManager          pid-589                              W  Access blocked: ComponentInfo{xxx/xxx.WatchMessageReceiver}
2022-07-15 11:26:15.023   589-5347  ActivityManager         pid-589                              W  Unable to start service Intent { act=com.google.android.gms.wearable.BIND_LISTENER cmp=xxx/xxx.WatchMessageReceiver } U=0: not found

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

I'm really afraid Android 13 might get released as-is, breaking WearOS app communication 😨😨

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

If you're not targeting API 33 you're not affected by the bug. So it's a big bug, and yes we of course expected more from Google, but you can always target the api level later when it's fixed.

But I agree this is kind of desperating that more than 1.5 month after the first report nothing has changed.