IssueTracker

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!

I've submitted a fix that I expect will fix this which will be available in the next canary (Ladybug Feature Drop 2024.2.2 Canary 2).

Note that I haven't been able to reproduce this locally, unfortunately, so the fix is speculative. I've been able to reproduce scenarios where resources are folded to ... instead of the actual resource value, but clicking (or Ctrl+clicking) on them always expands them. But the fix I've made actually now will start resolving the resource values correctly, so the appropriate values will be displayed. Since the reports we've received of this bug all involve the "missing" resource values that are replaced with ..., I'm hopeful this will make the problem a non-issue.

Please let us know if you run into this again on Ladybug Feature Drop 2024.2.2 Canary 2 or a later build.

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!