Fixed
Status Update
Comments
mo...@google.com <mo...@google.com>
va...@google.com <va...@google.com> #3
+1
va...@google.com <va...@google.com> #4
+1
jb...@google.com <jb...@google.com> #5
+1
jb...@google.com <jb...@google.com> #6
+1
ap...@google.com <ap...@google.com> #7
+1
mo...@google.com <mo...@google.com>
mo...@google.com <mo...@google.com> #10
+1
pr...@google.com <pr...@google.com> #12
+1
Description
Component used: Transition Version used: 1.5.0-alpha02 Devices/Android versions reproduced on: API 34
If you do a gesture back in Fragments using transitions and cancel the gesture multiple times, after the first cancel, starting the gesture will result in the transition on the exiting view failing to run.
I believe the cause of this is that the this
beginDelayedTransition()
called by with a 0 duration called by Fragment never triggersonAnimatedEnd()
callback inVisibility
. That results in the visibility failing to be added removed from the overlay and so the subsequent transitions on the view do not run.Here are logs synced with the calls from Fragment and Visibility. I would expect there to be an
onAnimationEnd reversed=false
log before theonTransitionEnd
in Visibility.The can be reproduced by patching in aosp/2748867 and doing the following in the navigation-integration app :