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'm updating to canary 6, and the line being flagged has changed, but I'm still seeing an identical location for the two incidents:

                        ?.or(android.R.attr.showWhenLocked or android.R.attr.turnScreenOn)
                             ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Might have to do with the line using both .or and infix or?

Thank you for continued reports. :)

Might have to do with the line using both .or and infix or?

It turns out that, in this case, operands of polyadic expression (super set of binary expression) need to use their own location, instead of the containing expression.

Also, thanks to this, found that the identical locations are used for if/else, which also assumed it's elvis operator, indicating ?: is never handled/tested. Will be fixed together.

Further fixes for this issue are now available in:

• Android Studio Ladybug Feature Drop | 2024.2.2 Canary 8
• Android Gradle Plugin 8.8.0-alpha08

We encourage you to try the latest update.

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

The fixes for this issue are now also available in:

• Android Studio Meerkat | 2024.3.1 Canary 3
• Android Gradle Plugin 8.9.0-alpha03

We encourage you to try the latest update.

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