Status Update
No update yet.
Comments
sp...@google.com
aa...@google.com
aa...@google.com
an...@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?
be...@gmail.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
be...@gmail.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
be...@gmail.com
sounds reasonable to me, thanks
sa...@gmail.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!
Description
.aab files already include a proguard.map to perform deobfuscation, but this isn't picked up by the APK inspector.
Instead you have to separately
- Extract the .aab contents
- Rename the extracted proguard.map file -> mapping.txt, as this is the only supported mapping filename (
- Open this file via "Load proguard mappings"
Ideally, Studio would just automatically load the included proguard.map when opening an app bundle.
I understand that more detailed information is available if you have access to the original build output and the seeds.txt and usage.txt files, but for many use cases only the mapping is enough.