Status Update
Comments
ar...@google.com <ar...@google.com>
aa...@google.com <aa...@google.com>
ma...@gmail.com <ma...@gmail.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?
aa...@google.com <aa...@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
ma...@gmail.com <ma...@gmail.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
ma...@gmail.com <ma...@gmail.com> #5
sounds reasonable to me, thanks
ma...@gmail.com <ma...@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!
ma...@gmail.com <ma...@gmail.com> #7
aa...@google.com <aa...@google.com>
aa...@google.com <aa...@google.com> #8
I disabled the flag by default since it doesn't work well with the scroll state.
ma...@gmail.com <ma...@gmail.com> #9
an...@google.com <an...@google.com> #10
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!
ma...@gmail.com <ma...@gmail.com> #11
co...@protonmail.com <co...@protonmail.com> #12
lol
ma...@gmail.com <ma...@gmail.com> #14
2. These bugs have accumulated so many that they are starting to interfere with my work.
3. Google says I should test these bugs even more for free.
4. Google closes all bugs and doesn't fix them, saying they are fixed or they don't exist because they can't see them.
Google needs to work on its etiquette! They have a pig's ass attitude towards people who are trying to help them for free.
Description
Description has been deleted.