Status Update
Comments
ga...@google.com <ga...@google.com> #2
FWIW, the View Binding classes are generated correctly (and separate ones for the main
and wearable
modules are correct).
The only issue here is with them resolving correctly in Android Studio.
ga...@google.com <ga...@google.com> #3
Beautiful bug report, thank you. I'll try to take a look in the nearish future.
zs...@salesforce.com <zs...@salesforce.com> #4
Hey Ian, it looks like there is no v3.4.0-alpha04
tag. The most recent I see is v3.4.0-alpha03
.
ga...@google.com <ga...@google.com> #5
Yes, sorry. v3.4.0-alpha03
is the correct tag to look at.
zs...@salesforce.com <zs...@salesforce.com> #6
Ian, I know you're out until Monday. Maybe we can talk next week? This case seems really ambiguous, that you have two modules with the same package and same layout files. Can you walk me through how the framework resolves this?
ga...@google.com <ga...@google.com> #7
In this particular case, these modules are entirely independent application modules, so the Android framework isn't involved - as mentioned, the builds themselves work fine as they are two independent builds.
It is just the resolution issue in Studio that is a regression from 3.6.2, which I didn't have this problem on.
Description
There are two immediate solutions to this:
1. Do only one L8 compilation passing both the desugared library and the custom conversions as inputs.
2. Do a D8 merge of the L8 compilations such that no duplicates are assured.