Fixed
Status Update
Comments
il...@google.com <il...@google.com>
ap...@google.com <ap...@google.com> #2
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 <jb...@google.com> #3
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 <an...@google.com> #4
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-rc05
When called on a view within a fragment added with a <fragment> tag in a layout, FragmentManager.findFragment(view) returns either the containing fragment's parent, or crashes as it can not find any parent fragment.
I've attached a sample project which crashes on startup due to the bug. Replacing the <fragment> tag with FragmentContainerView or a framelayout with a manual transaction avoids the crash