Status Update
No update yet.
Comments
il...@google.com
jb...@google.com
cl...@google.com
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.
cl...@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.
pr...@google.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
Component used:
androidx.navigation.composeVersion used:
2.6.0Devices/Android versions reproduced on: Emulator (Resizable, API 33), but seen of many devices in the wild.
Summary
When using the
dialogextension method to add a navigation destination. If the content inside has aViewModelthat uses theSavedStateHandle. When the app is sent to the background, killed by the system, and then restored, theSavedStateHandleis empty.In addition the use of a
rememberSaveablein the content of thedialogdoesn't restore its value after process death either.Sample Project
A demo project
Screen recording
Screen recording is attached, in which "Don't Keep Activities" is turned on to simulate the process death.