IssueTracker

[Comment deleted]

[Comment deleted]

Also of note is the adb error when trying to install bad APK: INSTALL_FAILED_DEXOPT

load dex files over 5Gb. -> load dex files over 5Mb.

Same here! Looking forward to a solution :)

Android Studio version: 0.8.12
buildToolsVersion 21.0.1
Gradle 1.11

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.

Thanks for your quick response.

It's nice to know about that command line option.  I do not see it in the output of 'dx --help', might be good to add that.

I'm not very familiar with the 'linearAlloc limit' issue outside of the context of the dexopt step.  My sample app is able to run once the lower idx value is set, although I do not actually call into any of the library code that is bundled with the app.  I assume it's undefined when/if the 'linearAlloc limit' will be hit in a large application on gb.

I'm a bit confused as to the platform compatibility of multidex given the 'linearAlloc limit' bug.  What specific versions of Android are supported?  The multidex code implies back to v4 (https://android.googlesource.com/platform/frameworks/multidex/+/master/library/src/android/support/multidex/MultiDex.java) but it would seem that ICS is the earliest supported platform.  Is this correct?

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 clearer https://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

for Android studio use:
dexOptions {
        additionalParameters = ['--multi-dex', '--set-max-idx-number=40000']
    }

I still have this issue and it's driving me nuts

#11 your SafeCoordinatorLayout is a lifesaver for the older API levels!

I submitted a pull request to fix this issue one month ago, but still no reaction from Google: https://github.com/material-components/material-components-android/pull/31

Can you please provide a reproduction usecase without the app's(application given in comment #6) additional layers of abstraction responsible for parceling state.

Can you please provide the information requested in comment #16 to investigate further.

I created a minimal sample project as reproduction usecase: https://github.com/cbeyls/CoordinatorLayoutStateRestoration
I also provided the fix as pull request and a workaround class for developers, I don't think I can do more than that.

Note that we're dropping support for <v14 in 26.0.0 so unlikely to release a fix.

Thanks for the investigation though Christophe

I was hoping for a final 25.x bugfix release for older devices before their support is dropped. CoordinatorLayout never worked properly on API <13 devices since it was introduced in 2015.

We no longer target support library for devices less than API 14. Since this bug is only reproducible for those devices, there is nothing we can do about it.
If you can create a minimal project that reproduces it on devices with API 14 and above, we can reopen the bug and fix it.