Status Update
Comments
an...@jetbrains.com <an...@jetbrains.com>
ar...@google.com <ar...@google.com>
pe...@google.com <pe...@google.com>
du...@google.com <du...@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?
an...@jetbrains.com <an...@jetbrains.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
du...@google.com <du...@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...@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
Android Plugin 4.0, 4.1 in 2020.2, 2020.3, 2021.1. Earlier versions also affected.
Reported here:https://youtrack.jetbrains.com/issue/IDEA-244008 . See also IDEA-198719 and all its duplicates for different scenarios.
Steps
zip
file to the projectExpected
ZIP file is opened
Actual
Android plugin intercepts the open action, tries to open zip file and fails with the exception
Pre-discussed with @Yuriy Solodkyy. On one hand, there is no clean way to identify that Android SDK is not configured (because there are no dependencies
android.apkanalyzer>android.core
, and introducing them does not look right, so classesIdeSdks
andAndroidSdks
are not available in theApkEditorProvider
). On the other hand,ApkViewPanel
should not even try to invokeProjectSystemUtil.getProjectSystem(myProject)
for non-android project.It would also be nice if SDK management was moved out of
android.core
, so other IDEs (like Rider) could use it easily. At JB we have team capacity to implement this.