Fixed
Status Update
Comments
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).
mg...@google.com <mg...@google.com>
il...@google.com <il...@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().
pr...@google.com <pr...@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
Currently, Lifecycle.eventFlow stops sending out new events when the
Lifecycle
reaches theDESTROYED
state. However, theFlow
never completes.Ideally, Lifecycle.eventFlow should complete when the
Lifecycle
isDESTROYED
. This would signal to consumers that they won't receive any new emissions and the flow is terminated.We found this issue while working on b/370577987 , which disallows moving from the
DESTROYED
state to any other state.