Fixed
Status Update
Comments
tf...@gmail.com <tf...@gmail.com> #2
Jeremy, is this still an issue? I think the problem was that you had two transitions targeting the same View for the same action (e.g. two Slide() transitions).
il...@google.com <il...@google.com>
ap...@google.com <ap...@google.com> #3
I have a similar issue with plain AnimatorSet:
set.start()
set.pause()
set.setCurrentPlayTime(100)
set.setCurrentPlayTime(0)
set.setCurrentPlayTime(100)
set.resume()
doesn't play animation in resume().
il...@google.com <il...@google.com>
ja...@gmail.com <ja...@gmail.com> #4
Should clarify that if I filter out setCurrentPlayTime(0)
(or replace it with setCurrentPlayTime(1)
) it works well.
Also even with setCurrentPlayTime(0)
, onAnimationEnd
is notified with correct delay (as if the animation has played).
il...@google.com <il...@google.com> #5
@
I think that is intended for Animator. If you set the currentPlayTime
to 0 or the total duration the animator completes. We do some
Description
Component used: Fragment
Version used: 1.3.0-alpha08
Devices/Android versions reproduced on: Pixel 4 / Android 10
Sample project:https://github.com/tfcporciuncula/broken-transition
Fragment blinking issue video:https://github.com/tfcporciuncula/broken-transition/blob/master/videos/red%20blink.mp4 (you might need to go frame by frame in the video to see the blinking)
Back issue video:https://github.com/tfcporciuncula/broken-transition/blob/master/videos/back%20regular.mp4 ( and here's a video with the regular behavior for this )
I have very simple slide transitions defined by myself ( exactly like these ones ) and I noticed they got a bit broken after I updated everything to the latest version. I decided to call
FragmentManager.enableNewStateManager(false)
to check if the issues were related to the new state manager, and indeed the issues were gone after that.The first issue I noticed was that the fragment I'm transitioning to blinks in the very beginning of the transition. I managed to reproduce it in the very simple example I'm linking here, but for some reason the issue seems to happen more frequently on my actual app and not that often in the sample, even though it still happen fairly often. It feels like it's a single frame blink, so it's a little hard to see but it's definitely noticeable when it happens.
There's a second issue I noticed while testing this with a super slow transition duration: when I tap back during the transition from the blue fragment to the red fragment, I end up in a blank screen. If I have the
enableNewStateManager(false)
call, it simply moves to the end of the transition and transitions back from the blue fragment to the red, certainly a better behavior.