Status Update
Comments
sg...@google.com <sg...@google.com> #2
1. Have you saw crash in real device or only in simulators?
2. Do you use dynamic feature for language ID?
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: BoM 2023.06.01, Material3 1.2.0-alpha03
Jetpack Compose component used: Material3
Steps to Reproduce or Code Sample to Reproduce:
where
startDate
(Long
) andendDate
(Long
) are a part of state and can change when date picker is open.startDate
andendDate
change their values in the background (in my case it's ViewModel that reloads the data and the new state is emitted) so that the new instance ofdateValidator
is created.This also happens for compose-material3 1.2.0-alpha03 and
SelectableDates
interface: