Status Update
No update yet.
Comments
rp...@google.com
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?
vs...@google.com
xa...@google.com
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
vs...@google.com
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
er...@gmail.com
sounds reasonable to me, thanks
vs...@google.com
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!
er...@hellsoft.se
This is a common practice at several teams I worked in, so it's not unique to my current workplace.
vs...@google.com
Sounds good. Adding a setting is tracked in
sh...@google.com
sh...@google.com
an...@google.com
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 1
- Android Gradle Plugin 8.8.0-alpha01
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
####################################################
Please provide all of the following information, otherwise we may not be able to route your bug report.
####################################################
1. Describe the bug or issue that you're seeing.
When a fatal crash occurs, the logcat output includes the text "(Ask Gemini)" next to the first line of the exception. This should probably be a link or contain other information. One of my developers asked who Gemini was. :)
2. Attach log files from Android Studio
2A. In the IDE, select the Help..Collect Logs and Diagnostic Data menu option.
2B. Create a diagnostic report and save it to your local computer.
2C. Attach the report to this bug using the Add attachments button.
3. If you know what they are, write the steps to reproduce:
3A. Login to your Google account
3B. Enable Gemini integration
3C. Open logcat and run an app that has a Fatal Exception
Build: AI-241.18034.62.2411.12169540, 202408010925
AS: Koala | 2024.1.1 Patch 2
AI-241.18034.62.2411.12169540, JRE 17.0.11+0-17.0.11b1207.24-11852314x64 JetBrains s.r.o., OS Mac OS X(aarch64) v14.6.1, screens 3024.0x1964.0
Android Gradle Plugin: 8.5.2
Gradle: 8.7
Gradle JDK: JetBrains Runtime 17.0.11 - aarch64
NDK: from local.properties: (not specified), latest from SDK: (not found)
CMake: from local.properties: (not specified), latest from SDK: (not found), from PATH: 3.29.2
```