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.
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
Component used: Navigation Version used: 2.5.0+ Devices/Android versions reproduced on: all
When using Navigation Compose, there are situations where the changing the destination can cause the Navigation graph to be reset (this happens any time a change is made to the graph that causes it to not be equal to the previously set graph).
Although it is not likely the intended behavior in most cases since it actually causes you to reset the entire back stack, it would be nice if Navigation at least did not crash.
Here is a sample app:https://github.com/kristof-taveirne/OnBoardingCompose