Obsolete
Status Update
No update yet.
Comments
jb...@google.com
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).
th...@outlook.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().
Description
Version used: 1.8.0-SNAPSHOT
I've written a test to showcase a bug I encounter in real world usage where sometimes when navigating back using the 'navigate up' back button, the animation is not played and the top fragment remains on top. It seems to happen in combination with a shared element transition and predictive back.
Navigating back from this undefined state triggers a memory leak.
The test is available in the sample project: