I don't think the average developer understands the distinction between method references and method definitions in this context (inside a DEX file). I know I don't.

@jvg, can you elaborate?

people who are looking at the bytecode in the dex to optimize their app through shrinking hopefully will learn the difference as string tables for method references between various dex files can account for quite a bit of disk space. but more importantly a definition is something you can analyze its code for where a reference you can't so the UI can be confusing without seeing the difference

How about something like this?

I think having defined members be directly under the class node while references are nested in a group makes more sense.

Also note that the method refs have a slightly different icon. There is no existing equivalent for field refs that I could find.

https://screenshot.googleplex.com/4yXVM9Rzh4wnkjM.png

sounds reasonable to me, thanks

Thank you for your patience while our engineering team worked to resolve this issue. A fix for this issue is now available in:

• Android Studio Ladybug Feature Drop | 2024.2.2 Canary 4
• Android Gradle Plugin 8.8.0-alpha04

We encourage you to try the latest update.

If you notice further issues or have questions, please file a new bug report.

Thank you for taking the time to submit feedback — we really appreciate it!

Hey @jpaupore, I tried to enable the scope enlarger for K2 IDE: https://kotlin.jetbrains.space/p/kotlin/reviews/1050/timeline, but as you see in the CR, Ilya suggested trying KaResolveExtensionProvider.

Could you please help us how we can use KaResolveExtensionProvider for the Android data binding completion?

Are there any updates?

We've identified the root cause and are working on a fix upstream in the Kotlin plugin.

We just submitted a commit to enable the scope enlarger for K2. We have to wait until the next IntelliJ merge to Android Studio. I will talk to JetBrains about cherry-picking the commit for the next release.

We are on discussion to land my commit for the next IntelliJ release, but I confirmed my commit fixes this issue on the upstream K2 IntelliJ with Android plugin: https://screencast.googleplex.com/cast/NTA1NTUwMzEwNDIxMjk5MnxjZDgzMGRiZS02Nw

The video shows the completion for a simple data binding class. I used the codelab example from https://developer.android.com/codelabs/android-databinding#0.

I confirmed my upstream commit fixing this issue is now available on studio-main after 242.1 merge. I removed ActivityMainBinding from https://github.com/android/databinding-samples/blob/0056c0bd6c85ecb3a0de98d2fec7f422ef0ec9fa/BasicSample/app/src/main/java/com/example/android/databinding/basicsample/ui/MainActivity.kt#L36 and tested the auto-completion. It works fine. I think the next Android Studio release will fix this issue.

@andymagee, Could you please follow up e.g., adding unit tests to studio-main code base and close this issue after the next Android Studio release? I will reassign this issue to you.

Agreed, the behavior is now correct as tested in the latest builds of Studio. I'll update our tests and close this issue.

Thank you for your patience while our engineering team worked to resolve this issue. A fix for this issue is now available in:

• Android Studio Ladybug Feature Drop | 2024.2.2 Canary 2
• Android Gradle Plugin 8.8.0-alpha02

We encourage you to try the latest update.

If you notice further issues or have questions, please file a new bug report.

Thank you for taking the time to submit feedback — we really appreciate it!