Fixed
Status Update
No update yet.
Comments
al...@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
ap...@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().
jb...@google.com
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
ViewModelProviderKtexists in bothlifecycle-viewmodel-ktx:2.3.1, which gets pulled in transitively byappcompat, andlifecycle-viewmodelat head. If I updateappcompattolifecycle-viewmodelit's going to cause a classpath conflict for a lot of external clients.Dependency constraints should be used here, but Gradle has several bugs in dependency constraint resolution that prevent us from using it (seehttps://github.com/gradle/gradle/issues/19882 ).
Please use a different
JvmNamefor the class inlifecycle-viewmodelso that we can avoid the conflict without needing to blocklifecycle-viewmodelorappcompat's release on Gradle fixing their bugs.