Fixed
Status Update
No update yet.
Comments
il...@google.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).
il...@google.com
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().
il...@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-alpha06
When using
setReorderingAllowed(true)(such as when using the Navigation Architecture Component), doing areplace()will cause the new fragment to go throughonCreateView(),onViewCreated()and potentially up throughonStart()andonResume()before the previous fragment is stopped.This means that any values that are set on a shared view model (i.e., when
Ideally, the previous fragment should be stopped (but specifically not have its view destroyed) prior to the new fragment moving up through lifecycle methods.