Status Update
Comments
kd...@google.com <kd...@google.com>
pa...@google.com <pa...@google.com>
an...@nrk.no <an...@nrk.no> #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?
pa...@google.com <pa...@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
sp...@google.com <sp...@google.com>
sp...@google.com <sp...@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...@nrk.no <an...@nrk.no> #5
sounds reasonable to me, thanks
an...@google.com <an...@google.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 bug or issue that you're seeing.
We have a project with multiple modules using here . This seems to build just fine when for instance building a regular APK, but linting fails.
apply plugin: 'com.android.library'
. One of these modules (calledanalytics
) needs to use an external AAR file. We have tried to set it up as describedFor instance when we run
lintDebug
we get this error:We don't need the modules to be built as AAR-files, in the end they'll just be part of the final app. But then we assume there's either something missing in the documentation, there is an error with the linting or that we are missing some setup.
A similar issue has been discussed on StackOverflow , but that's for modules that are going to be used as actual libraries in the end - and they are refering to an old method that I guess aren't recommended anymore?
Attach log files from Android Studio
As this most likely isn't an issue with Android Studio (I just weren't allowed to create the issue anywhere else) I don't think this is needed - but let me know if it is!
If you know what they are, write the steps to reproduce:
implementation files(...)
with an AAR-filelintDebug
task or something alike itAdditional information