Skip to content

Conversation

@KevinBlock-GC
Copy link

This PR adds the option to suppress navigation events that happen because the fragment manager is in a saved state. This only happens when the activity has been destroyed and re-created.

I took this approach since in some cases, the app is in the background when it crashes. It also doesn't seem to mess with navigation that I can tell. It's a toggle so we can feature tag it!

Also, this is what the Android FragmentNavigator checks for as well!

Before

Screen.Recording.2025-02-26.at.2.14.07.PM.mov

After

Screen.Recording.2025-02-26.at.2.51.58.PM.mov

Copy link

@jameshynes jameshynes left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks great! It's a good sign that the Android navigator is performing the same check as well.

@KevinBlock-GC KevinBlock-GC merged commit 403dcd1 into develop Feb 26, 2025
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

3 participants