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!

Thanks. I'm not sure what's going on.

Is it possible for you to try reproducing in a current Meerkat canary from https://developer.android.com/studio/preview ? For me, those previews behave as I expected (the banner shows up in response to changes in the diff viewer). I'm not sure what's going on with Ladybug Feature Drop, but it would be good to eliminate one possible source of variation if possible.

Thanks, I will investigate why the fix seems to have disappeared from Ladybug Feature Drop.

The fixes for this issue are now also available in:

• Android Studio Meerkat Feature Drop | 2024.3.2 Canary 2
• Android Gradle Plugin 8.10.0-alpha02

We encourage you to try the latest update.

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

To update you on this:

I took a deeper look at the implementation of the change detector, and the banner displayer, and discovered a bit of a rats' nest. I've merged some fixes into our latest canary (as suggested by the above comment) and have also booked a meeting with owners to discuss ideas around redesigning / changing its implementation completely in order to make it more robust.

This bug might get more automated release notifications of the above kind as we make progress. Thanks once again.

Further fixes for this issue are now available in:

• Android Studio Meerkat Feature Drop | 2024.3.2 Canary 3
• Android Gradle Plugin 8.10.0-alpha03

We encourage you to try the latest update.

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