incorporate safe fallback destination to fix null destination causing UI flickering #1728
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #1675
When navigating to a destination lower in the hierarchy, the currentBackStackEntry temporarily becomes null due to the incremental update of the back stack by the NavController. This transient state causes UI elements, such as the Top Bar, to be removed and re-added, leading to a noticeable flicker.
A previousDestination fallback mechanism has been introduced. This approach ensures the UI maintains its state by retaining the last known valid destination when currentBackStackEntry is null. The following changes were made:
NiA-currentDestination-null-bug.mp4