Verified
Status Update
No update yet.
Comments
no...@google.com
mo...@google.com
ap...@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?
ap...@google.com
Tested on Android 12 Emulator with custom executor, but cannot repro this issue.
je...@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
Description:
Android MotionEvents reports the pressure being applied to the screen by a finger, stylus or other pointer device.
There appears to be no way to get touch pressure in Jetpack Compose without resorting to
pointerInteropFilter, which the documentation recommends we don't use and which in any case appears to break when inside a LazyItem scope. (pointerInteropFiltergets very janky, and drops around 90 per cent of events when in something like a LazyColumn.)It would be nice if
androidx.compose.ui.input.pointerorandroidx.compose.ui.input.pointer.pointerevent(or indeed anywhere you liked!) contained pressure properties or methods.Use Case:
Any Jetpack Compose drawing or handwriting app could make use of touch pressure. I imagine games could also benefit from it?