Status Update
Comments
jo...@google.com <jo...@google.com>
tn...@google.com <tn...@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?
tn...@google.com <tn...@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
rv...@mozilla.com <rv...@mozilla.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
rv...@mozilla.com <rv...@mozilla.com> #5
sounds reasonable to me, thanks
tn...@google.com <tn...@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!
rv...@mozilla.com <rv...@mozilla.com> #8
Thanks for the quick fix! I'll verify it when alpha07 is released.
Regarding Context.kt, I did more digging into where the function gets called in our codebase and am confident now that the improved detection in 8.8 is doing the right thing in this case. I can confirm that lint still passes if I remove the @TargetApi annotation entirely as the function is only ever called when running on <Q.
tn...@google.com <tn...@google.com> #9
Great, thank you! (P.S. I think alpha07 was released yesterday so this will be in alpha08.)
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 8
- Android Gradle Plugin 8.8.0-alpha08
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!
rv...@mozilla.com <rv...@mozilla.com> #11
Verified fixed in alpha08!
Description
With the AGP 8.8.0 alpha builds, we're seeing new ObsoleteSdkInt warnings that seem spurious. Our project is built with minSdkVersion = 21, targetSdkVersion = 34, and compileSdkVersion = 35.
I'm not sure if it's the TargetApi annotation that's tripping things up, but my understanding is there's nothing preventing this code from running on older API levels and the code is valid as-written.