Status Update
Comments
di...@google.com <di...@google.com> #2
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?
jl...@google.com <jl...@google.com>
js...@google.com <js...@google.com> #3
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
js...@google.com <js...@google.com>
js...@google.com <js...@google.com>
an...@google.com <an...@google.com> #4
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
nu...@traderepublic.com <nu...@traderepublic.com> #5
nu...@gmail.com <nu...@gmail.com> #6
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!
Description
DESCRIBE THE ISSUE IN DETAIL: AbstractAnnotationDetector is used in DeprecatedAnnotationDetector rule. After AGP 8.6.0 and Lint 31.6.0,
visitAnnotationUsage
started checking wrong function/constructor.I cannot verify this situation in Unit Test. Repo has the setup to reproduce.
STEPS TO REPRODUCE:
Version of Gradle Plugin: 8.6.x, 8.7.0 Version of Gradle: 8.10.2 Version of Java: 21 OS: Mac OS, Ubuntu