IssueTracker

thanks for create this issue instance. It is more related to generated Binding Class in Data Binding is deemed to be Unresolved by KT Editor, when multiple base modules in the project has the same Data Binding classes.

The bar for cherry picking is too high, I'm afraid. If I understand things correctly...

1. The workaround is simple (just ignore it for now)
2. This isn't a regression, it's been present in older versions of Studio
3. (As far as our team can tell) this doesn't affect a large % of all Studio users

If these are true, then it's certain the request for a cherry pick will be rejected. After all, cherry picks are risky (landing so late) and require a bunch of resources (an additional test path with QA brought up to speed), so I've seen worse bugs rejected for cherry picks than something like this.

Let me know if I'm missing anything. I'm closing this bug down for process reasons, but please feel free to keep the conversation going and I'll respond.

I think it is fine to leave the status: Won't fix for this issue instance, since the fix is in 4.2 Canary 9 already.

1. The workaround is simple (just ignore it for now)
2. This isn't a regression, it's been present in older versions of Studio

not an objection for me as the issue reporter.

(As far as our team can tell) this doesn't affect a large % of all Studio users

I think it is really an edge case. As far as i can think of the scenarios to cause this happen would be:

1. Doing the Android Kotlin Codelabs, since it happens a lot to duplicate the base module as final and start for scaffolding learning
2. Working with the App solution across multiple android based devices, such as Wear OS, Android phone while the project has multiple base modules all having the same named layout files for features such as SettingsFragment.

When i was able to change the runtime of AS 4.0.1 to OpenJDK 11 with Choose Runtime Plugin. The issue seems to be resolved, but as far as i click on the reference to open the declarations the Android Studio 4.0.1 has crashed and restarted by itself. Such a behaviour doesn't seem to happen in AS 4.1 RC2.

Thanks for your update, but it's hard to confirm whether it is the same bug since 3 years have passed.

In comment #1:

The reporter said that this issue has been fixed in Android Studio 4.2 Canary 9

This makes me believe that you are hitting a different issue (different root cause with the same symptom).

Please file a new bug with us with as many details as possible and we can start/restart the investigation process.