Fixed
Status Update
No update yet.
Comments
jb...@google.com
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).
il...@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().
ni...@gmail.com
Comment has been deleted.
ni...@soprasteria.com
@
I think that is intended for Animator. If you set the currentPlayTime to 0 or the total duration the animator completes. We do some
Description
Component used: AndroidFragment
Version used:
Devices/Android versions reproduced on: Any (See attached image)
Reproduction :
Discussion We have no clue why it's triggered, anyway :
When we explore the source code of "Androidfragment", the usage of "commitNow" leads to the famous crash when application go to / come back from the background.
one of the explored solution today is to override this component and replace commitNow with the least unstable commitAllowingStateLoss.
Do you have any advice / opinion to this situation ?
Best Regards,
Nicolas V.