Fixed
Status Update
No update yet.
Comments
il...@google.com
to...@yahoo.com
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).
ap...@google.com
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().
jb...@google.com
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).
Description
Component used: Fragment
Version used: 1.3.0-beta01
Devices/Android versions reproduced on: Pixel 2 API 29 emulator
Muzei's
mainmodule usesTRANSIT_FADEto swap between fragments based on whether Muzei is your current wallpaper. This listener is set on aFlowthat runs when the fragment is at leastSTARTED, meaning that callbacks end up normally being triggered as part of the move toSTARTED.Reproduction steps:
FragmentManager.enableNewStateManager(false)inMuzeiApplicationin themainmoduleExpected behavior: Next screen (
TutorialFragment) appearsActual behavior: New fragment does not appear, despite going to
RESUMEDstateAdditional information: If I attach the layout inspector, the fragment magically appears!
Removing the
TRANSIT_FADEor using the old state manager causes everything to work as expected as well.