Fixed
Status Update
Comments
[Deleted User] <[Deleted User]> #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).
il...@google.com <il...@google.com>
[Deleted User] <[Deleted User]> #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().
il...@google.com <il...@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
Component used: Fragment
Version used: 1.3.0-alpha07
If you remove a detached fragment
FragmentManager
will callsetVisibleRemovingFragment
which in turns callscontainer.setTag(R.id.visible_removing_fragment_view_tag, f);
But since the fragment is detached
FragmentAnim
(which removes the tag) is never called and thus leaking the fragment until another fragment transaction that overwrites the tag is executed.