Fixed
Status Update
No update yet.
Comments
il...@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).
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().
Description
Version used: Both 1.3.5 and 1.4.0-alpha04 with new state manager enabled. + Transition lib 1.4.1
Devices/Android versions reproduced on: Pixel 3 API 28 emulator
The code here seems to cause the issue:
In the error scenario, the fragmentView is set to GONE, but is also included in the exitingViews list so is immediately set back to VISIBLE:
fragmentView.setVisibility(View.GONE);
final int numViews = exitingViews.size();
for (int i = 0; i < numViews; i++) {
exitingViews.get(i).setVisibility(View.VISIBLE);
}
I have attached a screen recording and a test app project. To see the issue, just launch the app and click hide. It will only work once, so if you want to reproduce again you'll have to back out and launch again.