Fixed
Status Update
No update yet.
Comments
au...@google.com
[Deleted User] <[Deleted User]>
[Comment deleted]
ca...@gmail.com
Also of note is the adb error when trying to install bad APK: INSTALL_FAILED_DEXOPT
mm...@gmail.com
load dex files over 5Gb. -> load dex files over 5Mb.
we...@gmail.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
[Deleted User] <[Deleted User]>
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.
[Deleted User] <[Deleted User]>
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?
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 (
un...@gmail.com
I still have this issue and it's driving me nuts
si...@gmail.com
same issue. To make it working again when running ap requires to delete text jump to another view and return.
<android.support.design.widget.TextInputLayout
android:id="@+id/username_wrapper"
android:layout_width="match_parent"
android:layout_height="wrap_content"
>
<android.support.design.widget.TextInputEditText
android:id="@+id/username"
android:layout_width="match_parent"
android:layout_height="wrap_content"
android:inputType="textEmailAddress"
android:text="dummy text"
android:hint="@string/username_hint"/>
</android.support.design.widget.TextInputLayout>
<android.support.design.widget.TextInputLayout
android:id="@+id/username_wrapper"
android:layout_width="match_parent"
android:layout_height="wrap_content"
>
<android.support.design.widget.TextInputEditText
android:id="@+id/username"
android:layout_width="match_parent"
android:layout_height="wrap_content"
android:inputType="textEmailAddress"
android:text="dummy text"
android:hint="@string/username_hint"/>
</android.support.design.widget.TextInputLayout>
[Deleted User] <[Deleted User]>
25.1.1 doesn't fix the bug. Come on guys. At least give us some update.
de...@gmail.com
I had the same issue, needed change back to 24.1.1 to make it works.
:/
:/
jf...@gmail.com
I have the same problem, changed to 25.0.1 for make it work again. I hope a new update soon fixes this ¯\_(ツ)_/¯
[Deleted User] <[Deleted User]>
Fixed with 25.2.0
dn...@google.com
Issue is fixed and released in 25.2.0 support library.
ha...@gmail.com
Just switched to 25.2.0 but still not working :-(
sr...@gmail.com
Did not get fixed with 25.2.0 as well.
la...@gmail.com
Found this issue fixed with version 25.2.0
ja...@gmail.com
Didn't fixed in 25.2.0
hi...@gmail.com
25.3.1 did fix my InputTextLayout issue.
dr...@gmail.com
Nope, didn't fixed in 25.3.1
ca...@gmail.com
It IS fixed in 25.3.1, confirmed in Xamarin Android
gr...@gmail.com
I also use 25.3.1 and can still reproduce the bug
mw...@gmail.com
I am using 26.1.0 and still get the same issue
Description
Version used: 25.1.0
Theme used: Theme.AppCompat.NoActionBar
Devices/Android versions reproduced on: 4.1.1 and 7.0
Hey guys, I was testing my app with the Support Library 25.1.0 and found this bug on the TextInputLayout. If the EditText or TextInputEditText inside the TextInputLayout sets text using android:text, the hint and text overlay (Like this:
*Steps to reproduce: *
1. Add a TextInputLayout from the Design library;
2. Add an EditText or TextInputEditText inside it with a hint set;
3. Run the app and notice everything works;
4. Set an android:text value attribute in the EditText
5. Run the app again and notice how the hint and the text overlay. The component doesn't fix the glitch even if the user type something.