Fixed
Status Update
No update yet.
Comments
li...@gmail.com
this problem persists in the version 1.0.0-alpha04
se...@google.com
il...@google.com
This is actually an issue in FragmentManager, so I'll redirect this bug to that component to be fixed at that level and, once that fix is applied, it will apply to usages in Navigation as well.
ug...@gmail.com
Navigation component recently had a stable release, however this issue was not fixed and still persists in 2.0.0
bo...@gmail.com
Is there a current workaround for this issue?
il...@google.com
[Deleted User] <[Deleted User]>
is there any update on this issue?
ra...@gtempaccount.com
Still having this issue to this day. Any fixes for this problem ?
jo...@gmail.com
Any update? That is pretty discouraging given the issue was reported 1 year ago.
jb...@google.com
ap...@google.com
Project: platform/frameworks/support
Branch: androidx-master-dev
commit 9f9de42fa23c3da48bc71bc2d6ab7f0f20cdb532
Author: Jeremy Woods <jbwoods@google.com>
Date: Mon Aug 26 08:49:52 2019
Fix incorrect pop animation in multiple transactions
When a fragment is added by a pop and then removed in back to back
transactions, we should use a normal exit animation instead of a popExit
animation.
This change keeps track of the first Fragment being visibly removed
(remove, hide, or detach) in a set of FragmentTransactions. It passes
the animations of subsequent removing fragments to the one that will be
visible when the animation is executed. The Fragments are tracked by a
tag on their container.
Test: all tests pass, and tested in app
Bug: 111659726
Change-Id: I18eefc2fdb4fc4c27c467212cc2e68beb20ea00b
M fragment/fragment/src/main/java/androidx/fragment/app/FragmentManager.java
M fragment/fragment/src/main/res/values/ids.xml
https://android-review.googlesource.com/970127
https://goto.google.com/android-sha1/9f9de42fa23c3da48bc71bc2d6ab7f0f20cdb532
Branch: androidx-master-dev
commit 9f9de42fa23c3da48bc71bc2d6ab7f0f20cdb532
Author: Jeremy Woods <jbwoods@google.com>
Date: Mon Aug 26 08:49:52 2019
Fix incorrect pop animation in multiple transactions
When a fragment is added by a pop and then removed in back to back
transactions, we should use a normal exit animation instead of a popExit
animation.
This change keeps track of the first Fragment being visibly removed
(remove, hide, or detach) in a set of FragmentTransactions. It passes
the animations of subsequent removing fragments to the one that will be
visible when the animation is executed. The Fragments are tracked by a
tag on their container.
Test: all tests pass, and tested in app
Bug: 111659726
Change-Id: I18eefc2fdb4fc4c27c467212cc2e68beb20ea00b
M fragment/fragment/src/main/java/androidx/fragment/app/FragmentManager.java
M fragment/fragment/src/main/res/values/ids.xml
jb...@google.com
This has been fixed internally and will be available in the Fragment 1.2.0-alpha03 release.
Description
Version used: 1.0.0-alpha03
Devices/Android versions reproduced on: All
The attached sample project consists of three fragments: Step1, Step2, Step3
Step1 can navigate to two destinations (both are Step2 fragment).
Both Step2 destinations has an action to go to Step3. The destination with a problem action has popUpTo set to Step1.
All actions have the same transition animations set.
When tapping next on Step2 (on destination with navigation action with popUpTo=Step1) the Step2 fragment is being animated the wrong way.