Fixed
Status Update
Comments
sp...@google.com <sp...@google.com>
aa...@google.com <aa...@google.com>
aa...@google.com <aa...@google.com>
an...@google.com <an...@google.com> #2
[Comment deleted]
be...@gmail.com <be...@gmail.com> #3
[Comment deleted]
be...@gmail.com <be...@gmail.com> #4
Also of note is the adb error when trying to install bad APK: INSTALL_FAILED_DEXOPT
be...@gmail.com <be...@gmail.com> #5
load dex files over 5Gb. -> load dex files over 5Mb.
sa...@gmail.com <sa...@gmail.com> #6
Same here! Looking forward to a solution :)
Android Studio version: 0.8.12
buildToolsVersion 21.0.1
Gradle 1.11
Android Studio version: 0.8.12
buildToolsVersion 21.0.1
Gradle 1.11
sa...@gmail.com <sa...@gmail.com> #7
There is already an option in dx allowing to force generation of smaller dex files:
--set-max-idx-number=<value>
Unfortunately changing the default is not a solution since the linearAlloc limit can be reached at very different levels depending on the classes hierarchy and other criteria.
In addition for most applications, moving to multidex will only help to workaround the linearalloc limit for the installation. But the application will still crash against the same limit at execution. The only working use case where I know multidex can help with linearalloc is when the apk does not contains one application but distinct pieces running in separate process.
--set-max-idx-number=<value>
Unfortunately changing the default is not a solution since the linearAlloc limit can be reached at very different levels depending on the classes hierarchy and other criteria.
In addition for most applications, moving to multidex will only help to workaround the linearalloc limit for the installation. But the application will still crash against the same limit at execution. The only working use case where I know multidex can help with linearalloc is when the apk does not contains one application but distinct pieces running in separate process.
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.