Skip to content
  • Sponsor NativeScript/NativeScript

  • Notifications You must be signed in to change notification settings
  • Fork 1.7k

fix(android): nested frames were sometimes not recreated #9725

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Dec 31, 2021

Conversation

edusperoni
Copy link
Contributor

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 onResume as well

Migration steps:
specify onResume on custom fragment implementations

PHP-Proxy

PHP-Proxy

Error accessing resource: 404 - Not Found

@cla-bot cla-bot bot added the cla: yes label Dec 31, 2021
@NathanWalker NathanWalker changed the base branch from master to release/8.2.0 December 31, 2021 16:36
@NathanWalker NathanWalker merged commit 72b01c2 into release/8.2.0 Dec 31, 2021
@NathanWalker NathanWalker deleted the fix/nested-frame-fragments branch December 31, 2021 16:39
@NathanWalker NathanWalker restored the fix/nested-frame-fragments branch January 26, 2022 17:15
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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants