Status Update
Comments
ta...@mercury.com <ta...@mercury.com> #2
1. Have you saw crash in real device or only in simulators?
2. Do you use dynamic feature for language ID?
cl...@google.com <cl...@google.com>
si...@google.com <si...@google.com> #3
Tested on Android 12 Emulator with custom executor, but cannot repro this issue.
ha...@google.com <ha...@google.com>
ap...@google.com <ap...@google.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.
ha...@google.com <ha...@google.com> #5
Hmm, I feel the crash might be something related to separate/secondary process.
I also changed compileSdk and targetSDK to 31 but still cannot repro this issue.
Description
On an LG G8 with Android 9, the standard keyboard does not show a decimal separator button (e.g. '.' in most locales) when used with a
TextField
set up withKeyboardType.Number
. This makes it impossible to input fractional values without using a differentKeyboardType
such asKeyboardType.Text
.Jetpack Compose release version: 1.1.0-beta03
Android Studio Build: #AI-211.7628.21.2111.7863044
Kotlin version: 1.5.31