Fixed
Status Update
Comments
vm...@google.com <vm...@google.com>
je...@google.com <je...@google.com>
cm...@google.com <cm...@google.com> #2
[Comment deleted]
mi...@gmail.com <mi...@gmail.com> #3
[Comment deleted]
cm...@google.com <cm...@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.
an...@google.com <an...@google.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
an...@google.com <an...@google.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
####################################################
Please provide all of the following information, otherwise we may not be able to route your bug report.
####################################################
1. Describe the bug or issue that you're seeing.
In the new beta version of Android Studio it is not possible to create a new string value resource in the strings.xml of the submodule from another submodule. I have one strings.xml located in the common submodule, which is integrated by using "implementation project(path: ':common')" in build.gradle of the main module.
I use this since years, as I only want to have one strings.xml for all submodules to have only one file to translate and to use the same strings in all submodules.
In the last release versions it was possible to create a new string resource value in this common submodule with the main module, but in the new beta it is not possible anymore!
Please fix this!
Please also have a look to the screenshot I made.
For more information on how to get your bug routed quickly, see
Build: AI-242.20224.300.2421.12312915, 202409032002
AS: Ladybug | 2024.2.1 Beta 1
AI-242.20224.300.2421.12312915, JRE 21.0.3+-12282718-b509.11x64 JetBrains s.r.o., OS Windows 11(amd64) v10.0 , screens 1920x1080 (100%)
Android Gradle Plugin: 8.6.0
Gradle: 8.8
Gradle JDK: JetBrains Runtime 21.0.3
NDK: from local.properties: (not specified), latest from SDK: (not found)
CMake: from local.properties: (not specified), latest from SDK: (not found), from PATH: (not found)
```