Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Merged
NathanWalker merged 1 commit intorelease/8.2.0fromfix/nested-frame-fragments
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 requiresonResume as well

Migration steps:
specifyonResume on custom fragment implementations

@cla-botcla-botbot added the cla: yes labelDec 31, 2021
@NathanWalkerNathanWalker changed the base branch frommaster torelease/8.2.0December 31, 2021 16:36
@NathanWalkerNathanWalker merged commit72b01c2 intorelease/8.2.0Dec 31, 2021
@NathanWalkerNathanWalker deleted the fix/nested-frame-fragments branchDecember 31, 2021 16:39
@NathanWalkerNathanWalker restored the fix/nested-frame-fragments branchJanuary 26, 2022 17:15
NathanWalker pushed a commit that referenced this pull requestFeb 14, 2022
BREAKING CHANGE:AndroidFragmentCallbacks now requires onResume as wellMigration steps:specify onResume on custom fragment implementations
NathanWalker pushed a commit that referenced this pull requestFeb 18, 2022
BREAKING CHANGE:AndroidFragmentCallbacks now requires onResume as wellMigration steps:specify onResume on custom fragment implementations
NathanWalker pushed a commit that referenced this pull requestMar 1, 2022
BREAKING CHANGE:AndroidFragmentCallbacks now requires onResume as wellMigration steps:specify onResume on custom fragment implementations
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

2 participants
@edusperoni@NathanWalker

[8]ページ先頭

©2009-2025 Movatter.jp