Fixed
Status Update
No update yet.
Comments
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).
jb...@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().
Description
Component used: Fragment Version used: 1.3.0-alpha06
Right now,
setMaxLifecycle()only supportsLifecycle.State.CREATEDor higher. It would be nice ifsetMaxLifecycle()could also supportLifecycle.State.INITIALIZINGonly for Fragments that have never moved aboveCREATED- i.e., only something that could be set alongside the Fragment being added to theFragmentManager.This would allow developers and libraries built on top of fragments to keep fragments only at the attached state without going through
onCreate().