Fixed
Status Update
No update yet.
Comments
il...@google.com
ap...@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).
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
There are no use cases when we should allow a fragment's Lifecycle to be moved to
DESTROYEDother than when the fragment is actually destroyed.Therefore, you should not be able to
setMaxLifecycle()toDESTROYEDthrough aFragmentTransaction, initialize aFragmentScenariowithDESTROYED, or move aFragmentScenarioto theDESTROYEDstate usingmoveToState().Doing any of these things should throw an error.