Status Update
Comments
ba...@gmail.com <ba...@gmail.com> #2
1. Have you saw crash in real device or only in simulators?
2. Do you use dynamic feature for language ID?
sg...@google.com <sg...@google.com>
ap...@google.com <ap...@google.com> #3
Tested on Android 12 Emulator with custom executor, but cannot repro this issue.
na...@google.com <na...@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.
pr...@google.com <pr...@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
Jetpack Compose version: compose.material3 1.3.0-alpha06
Material Library Version (M2, M3 or Both?): M3
Material Compose component used: compose.material3
Android Studio Build: Android Studio Jellyfish | 2023.3.1
Kotlin version: 1.9.23
The below sample code uses a button to switch between two
DateRangePickerState
s used by aDateRangePicker
. The states differ only by theirselectableDates
parameter where one state only allows previous dates to be selected, the other only allows future dates.Expected behavior is that the UI instantly updates according to the selectable dates when the button state parameter is changed (i.e. the button is pressed in the example).
Actual behavior is that only those months display the selectable dates correctly that are freshly scrolled into view. The dates of the months currently visible are only updated when scrolled out of view and back again into view.