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?
jb...@google.com
Tested on Android 12 Emulator with custom executor, but cannot repro this issue.
ju...@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
The reason for this is that if a fragment on the back stack is destroyed while it is still created, we ensure the entry makes it to destroyed, but failed to clear some associated state. The state remains around and prevents us from popping the Nav back stack during system back.