Fixed
Status Update
Comments
al...@google.com <al...@google.com>
se...@google.com <se...@google.com> #2
A couple of questions:
1. Have you saw crash in real device or only in simulators?
2. Do you use dynamic feature for language ID?
1. Have you saw crash in real device or only in simulators?
2. Do you use dynamic feature for language ID?
se...@google.com <se...@google.com>
ap...@google.com <ap...@google.com> #3
Tested on Android 12 Emulator with custom executor, but cannot repro this issue.
se...@google.com <se...@google.com>
sa...@gmail.com <sa...@gmail.com> #4
-
Second crash in the description is from a real device. Experienced it myself on two different Xiaomi phones, plus lots of crashes from users in the Google Play console.
-
Dynamic features are not used in the application.
As a wild guess, I have downgraded build tools from 31.0.0 to 30.0.3, compileSdk from 31 to 30, and moved all work with Language ID to the service in a separate process (just to be sure that crash can kill secondary process instead of main). This combination is in beta for 2 days by now and I don't see any SIGSEGV crashes.
Description
Hello,
I updated this library
to this
And there is a bug that started to appear in my code. The bug is:
This is my code
The problematic line is textField.editText?.setKeyListener(null) but I do it on purpose since I read on the stackOverflow that keaybord wont' show up after clicking. I want to use it as a read only, and when clicked to open dialog with options to choose from, therefore no keyborad. The stack overflow =https://stackoverflow.com/questions/60710536/android-using-materialdatepicker-and-textinputlayout
So probably I'm not the only one using it this way.
My xml behind this code:
I believe it has something to do with some emoji or something, which I do not want to use.
Thank you