fix(android): check is disposed fragment is in the FragmentManager #8201
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.
Same as #8166 but based on release branch.
PR Checklist
What is the current behavior?
Fragment is always removed from the fragment manager in the
Frame.disposeCurrentFragment()method. Different versions of androidX behave differently if you try to remove a fragment from a fragment manager.What is the new behavior?
Added a check if the current fragment is actually contained in the fragment manager returned by the
_getFragmentManager()Fixes #8037