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).
jb...@google.com <jb...@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().
Description
When adding the stateless aosp/1859226 it used the
SavedStateViewModelFactory
constructor inAndroidViewModelFactory
under the hood, which meant that when using the statelessSavedStateViewModelFactory
and creating aViewModel
viaCreationExtras
, it required anApplication
to be set.Having an
Application
should not be a requirement for creating aViewModel
using theSavedStateViewModelFactory
or theAndroidViewModelFactory
. We should fix the behavior of theAndroidViewModelFactory
to rely on theNewInstanceFactory
when no application is available, just like theSavedStateViewModelFactory
used to.