Status Update
Comments
hu...@google.com <hu...@google.com>
js...@google.com <js...@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?
ey...@gmail.com <ey...@gmail.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
js...@google.com <js...@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
js...@google.com <js...@google.com>
an...@google.com <an...@google.com> #5
sounds reasonable to me, thanks
ey...@gmail.com <ey...@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!
js...@google.com <js...@google.com> #7
Thanks for the question; I missed the patch 1, but then realized that the patch 2 is due soon. I'll prepare the cherry-pick.
js...@google.com <js...@google.com> #8
^ Done. Will be in 8.7.2
an...@google.com <an...@google.com> #9
The fixes for this issue are now also available in:
- Android Studio Ladybug | 2024.2.1 Patch 2
- Android Gradle Plugin 8.7.2
We encourage you to try the latest update.
If you notice further issues or have questions, please file a new bug report.
Description
DESCRIBE THE ISSUE IN DETAIL:
After updating to 8.7.0 I am getting a false positive RestrictedApi error saying that I cannot call
NavOptionsBuilder.popUpTo
because it is restricted to the library scope.My call:
popUpTo
resolves to:which does not have a
RestrictTo
annotation. There is an overload that does though: