fix(android): nested frames were sometimes not recreated#9725
Merged
Conversation
This was referenced Jan 2, 2022
NathanWalker
pushed a commit
that referenced
this pull request
Feb 14, 2022
BREAKING CHANGE: AndroidFragmentCallbacks now requires onResume as well Migration steps: specify onResume on custom fragment implementations
NathanWalker
pushed a commit
that referenced
this pull request
Feb 18, 2022
BREAKING CHANGE: AndroidFragmentCallbacks now requires onResume as well Migration steps: specify onResume on custom fragment implementations
NathanWalker
pushed a commit
that referenced
this pull request
Mar 1, 2022
BREAKING CHANGE: AndroidFragmentCallbacks now requires onResume as well Migration steps: specify onResume on custom fragment implementations
5 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
PR Checklist
What is the current behavior?
Nested frames get into inconsistent states when destroyed and recreated.
What is the new behavior?
We attempt to manually recreate the frames when android doesn't magically do it for us.
BREAKING CHANGES:
AndroidFragmentCallbacks now requires
onResumeas wellMigration steps:
specify
onResumeon custom fragment implementations