Status Update
Comments
js...@google.com <js...@google.com>
je...@google.com <je...@google.com>
bi...@google.com <bi...@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?
jf...@block.xyz <jf...@block.xyz> #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
bi...@google.com <bi...@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
an...@google.com <an...@google.com> #5
sounds reasonable to me, thanks
dg...@oreillyauto.com <dg...@oreillyauto.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
In Android Studio Ladybug Canary 09, when tests are run from the IDE, the injected
ijresolvers2.gradle
init script contains multiple instances ofProject.hasProperty
added byaddGradleAndroidTestListener.gradle
fromGradleAndroidProjectResolverExtension
.Project.hasProperty
is an isolated projects violation in most cases because if the project doesn't have the requested property, Gradle searches upward through parent projects to the root.