Overriding resources with resValue in build.gradle leads to Error: Duplicate resources [37005589]

Fixed

Feature Request

[AOSP] Version-Studio-2.1

Migrated-Tools-Gradle

Status Update

No update yet.

Description

ie...@gmail.com

created issue #1

Sep 26, 2014 03:27PM

Gradle version: 2.1
Android gradle plugin version: 0.13.1
OS: MacOS

STEPS TO REPRODUCE:
1. Add a string to res/values/strings.xml
e.g. <string name="app_name">SimpleTest</string>

2. Add a product flavor which overrides this string:
productFlavors {
INT {
resValue "string", "app_name", "SimpleTest INT"
}
}

3. Execute:
gradle assembleINTDebug

EXPECTED RESULTS:

Build succeeds and the app is named "SimpleTest INT"

OBSERVED RESULTS:

Build fails with error:

:SimpleTest:mergeINTDebugResources FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':SimpleTest:mergeINTDebugResources'.
> /Users/xyz/AndroidStudioProjects/SimpleTest/SimpleTest/build/generated/res/generated/INT/debug/values/generated.xml: Error: Duplicate resources: /Users/xyz/AndroidStudioProjects/SimpleTest/SimpleTest/build/generated/res/generated/INT/debug/values/generated.xml:string/app_name, /Users/xyz/AndroidStudioProjects/SimpleTest/SimpleTest/src/main/res/values/strings.xml:string/app_name

ADDITIONAL INFORMATION:
When I add a resource file via a sourceSet for this build flavor instead of using resValue, I can successfully override the app_name.
I think setting a resource with resValue should behave the same as when using a sourceSet.

Comments

xa...@android.com <xa...@android.com> #2Sep 26, 2014 05:41PM

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

[Deleted User] <[Deleted User]> #3Jan 19, 2015 02:22PM

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.

je...@google.com <je...@google.com> Mar 27, 2015 05:10AM

Assigned to ch...@google.com.

hu...@gmail.com <hu...@gmail.com> #4Jan 10, 2017 07:11AM

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"

cu...@gmail.com <cu...@gmail.com> #5Apr 15, 2017 10:08AM

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

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

ch...@google.com <ch...@google.com> Feb 9, 2018 02:05AM

Reassigned to je...@google.com.

jo...@google.com <jo...@google.com> Sep 26, 2019 10:52PM

Reassigned to xa...@google.com.

xa...@google.com <xa...@google.com> Sep 30, 2021 11:24PM

Status: New

hu...@google.com <hu...@google.com> #6Sep 28, 2022 11:46AM

Assigned to an...@google.com.

+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

je...@google.com <je...@google.com> Oct 3, 2022 11:10PM

Reassigned to hm...@google.com.

hm...@google.com <hm...@google.com> #7Oct 10, 2022 09:32AM

Marked as fixed.

Note that I've been able to make it work by:

Adding <action android:name="com.google.android.gms.wearable.BIND_LISTENER" /> in the intent filter
Removing <data android:scheme="wear" android:host="*" />

But I feel like this is not something we should do