Status Update
No update yet.
Comments
le...@google.com
1. Have you saw crash in real device or only in simulators?
2. Do you use dynamic feature for language ID?
di...@googlemail.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.
di...@googlemail.com
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
Jetpack Compose component(s) used: foundation, material, livedata
Android Studio Build:
Kotlin version: 1.9.10
Steps to Reproduce or Code Sample to Reproduce:
val snappingLayout = remember(state) { SnapLayoutInfoProvider(state, positionInLayout = SnapPositionInLayout.CenterToCenter) }
val flingBehavior = remeberSnapFlingBehavior(snappingLayout)
LazyRow(state = state, flingBehavior = flingBehavior, contentPadding = PaddingValues(start = 100.dp, end = 200.dp))
with item that has 100.dp and 49.dp width
The layoutSize inside of positionInLayout should not subtract contentpadding from mainAxisViewPortSize?
In my usecase, the items are not centered to the container.
If it is not including content padding. It is not clear, what and how to calc the positionInLayout.