Status Update
Comments
il...@google.com <il...@google.com>
ap...@google.com <ap...@google.com> #2
1. Have you saw crash in real device or only in simulators?
2. Do you use dynamic feature for language ID?
jb...@google.com <jb...@google.com> #3
Tested on Android 12 Emulator with custom executor, but cannot repro this issue.
[Deleted User] <[Deleted User]> #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.
il...@google.com <il...@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
Component used: Navigation Version used: 2.4.0-beta02 Devices/Android versions reproduced on: multiple versions
When using
fromSavedStateHandle
to create the NavArgs class, it succeeds on first passes, but it fails when it tries to restore the data from the saved state (after process-death) if it has anyParcelable[]
objects, as it doesn't cast them properly.To reproduce this, please use the attached project, and enable "don't keep activities" from the developer options, if you open the app, then navigate to another app, and comes back, the app will crash with the following stacktrace:
The generated
fromSavedStateHandle
from the attached project has this:while
fromBundle
handles the casting properly: