Fixed
Status Update
No update yet.
Comments
ka...@gmail.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
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
Component used: Fragment Version used: 1.3.3 Devices/Android versions reproduced on: Emulator Android 10
Currently there is a crash trying to get parcelable from result after process restoration.
Setup:
MainActivity,FirstFragmentandSecondFragment.FirstFragmenttoSecondFragment.FirstFragmentcallsgetParentFragmentManager().setFragmentResultListener()inonViewCreated()and listens for result.getParentFragmentManager().setResult()on submit button click. Submit button does only that and doesn't navigate back toFirstFragment.BundleviaputParcelable(). We send backExampleClasswhich implementsParcelableusing@kotlinx.parcelize.Parcelize.Steps to reproduce:
SecondFragment.FirstFragmentreceives result inFragmentResultListener#onFragmentResultand callsresult.getParcelable().android.os.BadParcelableExceptionThere two ways to avoid crash:
result.setClassLoader(context.classLoader)beforeresult.getParcelable().Is this something that should be fixed on Fragment or platform side?
What is the preferred workaround for the app developers in the meantime?