fix(android): prevent error during tear down #5947
Merged
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.
It's a bit of a blind fix since I can't reproduce this issue. The scenario should be with racing between navigation and the activity destroy/recreate (with the native back button or don't keep activities and restore). The idea is to tear down the native UI in current/navigating entries while still caching the new entry, so that the app continues from the same entry once the activity is recreated.
Examining the latest changes here shows that the bool flags were moved to the end of the block. The current entry flag was moved without the guard.
Fixes #5614