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).
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
an...@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
Version used: 1.2.0-rc03
Devices/Android versions reproduced on:
When you use a <fragment> tag and do a configuration change to a layout that does not contain the <fragment> tag, the Fragment is still recreated by FragmentManager, but stays in the INITIALIZING state.
If the FragmentManager is then destroyed (i.e., by the user hitting back, the parent fragment being removed, etc), the non-config state is not correctly cleared out. This can be seen by checking if any ViewModels are cleared or if any retained child fragments are destroyed.