Fixed
Status Update
No update yet.
Comments
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?
il...@google.com
Tested on Android 12 Emulator with custom executor, but cannot repro this issue.
na...@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
Currently, when using
SavedStateHandleAPIs such asget(key): T,getLiveData(key): MutableLiveData, andgetStateFlow(key): StateFlowsimultaneously with a matchingkey, theSavedStateHandlesynchronizes the value between them.However, synchronizing between a
MutableStateFlowand aMutableLiveDatawould be very challenging, and now thatSavedStateHandleis Multiplatform,MutableLiveDatais not available in Kotlin Multiplatform.For this reason, we have decided to:
getMutableStateFlow(key): MutableStateFlow.getMutableStateFlow(key): MutableStateFlowand agetLiveData(key): MutableLiveDatamutually exclusive.Therefore, once a
keyis used by one of the two methods, attempting to get the other with the same key will result in an exception.Please note that
getStateFlow(key): StateFlowwill remain unchanged and is not mutually exclusive withgetLiveData(key): MutableLiveDatato maintain backward compatibility.These changes will also address the following feature requests: