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().
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-rc01
Devices/Android versions reproduced on: all
If your Fragment was added with animations or transitions and you go to remove it via code such as
fragmentManager.commitNow {
remove(fragment)
}
Previously, you could guarantee that fragmentManager.findFragmentById() / findFragmentByTag() would return null.
However, it seems like the Fragment 1.2 changes where onDestroyView() (and hence, onDestroy() / onDetach()) are not called until the animation/transition completes means this is no longer the case.
FragmentManager's state should always be up to date after commitNow(), even if the Fragment itself has not concluded its drive to onDetach().