Fixed
Status Update
Comments
aa...@google.com <aa...@google.com>
je...@google.com <je...@google.com>
cm...@google.com <cm...@google.com>
an...@google.com <an...@google.com> #3
[Comment deleted]
an...@google.com <an...@google.com> #4
Also of note is the adb error when trying to install bad APK: INSTALL_FAILED_DEXOPT
an...@google.com <an...@google.com> #5
load dex files over 5Gb. -> load dex files over 5Mb.
jo...@gmail.com <jo...@gmail.com> #6
Comment has been deleted.
ta...@gmail.com <ta...@gmail.com> #7
Comment has been deleted.
ta...@gmail.com <ta...@gmail.com> #8
Comment has been deleted.
pa...@gmail.com <pa...@gmail.com>
s0...@gmail.com <s0...@gmail.com> #9
The option is not documented in --help because it was designed for testing and we're not capable of documenting a reliable way to use it as a workaround of the linearalloc limit.
The linearalloc limit is reached when loading classes. At install time dexopt is loading all classes contained in the dex so it's facing the limit immediately. At execution the limit may be reached after some delay dependending of the usage you have of the packaged classes. If you face it at install time but not at execution, this means you never trigger the loading of some classes. In a real application those never loaded classes should have been shrinked away manually or by Proguard. The exception is when there are different groups of classes in the dex files used in separate process.
About multidex library supported versions I've merged recently a change to try to be clearerhttps://android-review.googlesource.com/#/c/108023/
The summary is that the library should work down to API 4 (Donut), but below ICS applications will probably be hit by the linearalloc limit
The linearalloc limit is reached when loading classes. At install time dexopt is loading all classes contained in the dex so it's facing the limit immediately. At execution the limit may be reached after some delay dependending of the usage you have of the packaged classes. If you face it at install time but not at execution, this means you never trigger the loading of some classes. In a real application those never loaded classes should have been shrinked away manually or by Proguard. The exception is when there are different groups of classes in the dex files used in separate process.
About multidex library supported versions I've merged recently a change to try to be clearer
The summary is that the library should work down to API 4 (Donut), but below ICS applications will probably be hit by the linearalloc limit
re...@gmail.com <re...@gmail.com> #10
for Android studio use:
dexOptions {
additionalParameters = ['--multi-dex', '--set-max-idx-number=40000']
}
dexOptions {
additionalParameters = ['--multi-dex', '--set-max-idx-number=40000']
}
ra...@gmail.com <ra...@gmail.com> #11
I still have this issue and it's driving me nuts
Description
When trying to use the new
com.android.settings
plugin insettings.gradle
, added in Android Gradle Plugin 8.0.0-alpha09, im getting an error not recognizingtargetSdk
method.In
settings.gradle
:Build log when sync-ing:
Gradle DSL method not found: 'targetSdk()'
Tried using up to the latest version (as of today
8.3.0-alpha18
) but still doesn't recognize. Haven't found any references to the lack of support for this.Are there any plans to add it? If i'm gonna move my module configuration to use this plugin, i need it to have all 3 versions, otherwise i will have 2 configurations in different places.
Studio Build: Version of Gradle Plugin: 8.2.0 Version of Gradle: gradle-8.5-all Version of Java: openjdk 17.0.7 2023-04-18 OS: macOs Ventura 13.4