Fixed
Status Update
No update yet.
Comments
gh...@google.com
je...@google.com
st...@google.com
[Comment deleted]
da...@google.com
Also of note is the adb error when trying to install bad APK: INSTALL_FAILED_DEXOPT
jo...@google.com
load dex files over 5Gb. -> load dex files over 5Mb.
da...@google.com
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
jo...@google.com
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
AI-201.8743.12.41.7199119, JRE 1.8.0_242-release-1644-b3-6222593x64 JetBrains s.r.o, OS Linux(amd64) v5.11.0-18-generic, screens 5120x2880, 5120x2880
AS: 4.1.3; Kotlin plugin: 1.4.32-release-Studio4.1-1; Android Gradle Plugin: 4.1.3; Gradle: 6.5; NDK: from local.properties: (not specified), latest from SDK: (not found); LLDB: pinned revision 3.1 not found, latest from SDK: (package not found); CMake: from local.properties: (not specified), latest from SDK: 3.10.2, from PATH: 3.6.2
We are using prefab to package a native-only library in a submodule of our project that is then referenced as a dependency of our main application module. We have found that the first build works fine but subsequent builds don't because, even though any changes get compiled into new shared object files, those shared object files aren't being packaged into the AAR. Instead, the stale asset is used and the new changes aren't reflected in the build.
Currently, we are using a workaround where we automatically delete the build/intermediates/prefab_package directory in a Gradle preBuild step. This seems to fix the problem, but shouldn't be necessary.