Fixed
Status Update
No update yet.
Comments
js...@google.com
lp...@google.com
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?
nj...@google.com
Tested on Android 12 Emulator with custom executor, but cannot repro this issue.
ap...@google.com
-
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
It'd be nice if
DividersupportedDp.Hairline. In its current implementation, the divider becomes invisible ifDp.Hairlineis used.I'm currently working this around by manually calculating
1pxindp:I'd also like to call it out that it feels weird to have
Dp.Hairlineglobally available, only to realize that it's up to Composables to manually support it(?). From what I understand, onlyBorderStrokeandModifier.borderaccount for hairlines inv1.0.1.