Fixed
Status Update
No update yet.
Comments
il...@google.com
to...@yahoo.com
Hi Ed, Thank you so much for these suggestions. I've been reviewing them and merging them in. Hopefully it should be live. I've included a thank you note too in the article.
ap...@google.com
Great! Thanks a lot, I'll look for the live updates soon!
jb...@google.com
This has been fixed internally and will be available in the Fragment 1.3.0-beta02 release.
You can verify this by following the 6982024 and switching your fragment dependency to 1.3.0-SNAPSHOT.
Description
Component used: Fragment
Version used: 1.3.0-beta01
Devices/Android versions reproduced on: Pixel 2 API 29 emulator
Muzei's
mainmodule usesTRANSIT_FADEto swap between fragments based on whether Muzei is your current wallpaper. This listener is set on aFlowthat runs when the fragment is at leastSTARTED, meaning that callbacks end up normally being triggered as part of the move toSTARTED.Reproduction steps:
FragmentManager.enableNewStateManager(false)inMuzeiApplicationin themainmoduleExpected behavior: Next screen (
TutorialFragment) appearsActual behavior: New fragment does not appear, despite going to
RESUMEDstateAdditional information: If I attach the layout inspector, the fragment magically appears!
Removing the
TRANSIT_FADEor using the old state manager causes everything to work as expected as well.