Fixed
Status Update
Comments
il...@google.com <il...@google.com>
to...@yahoo.com <to...@yahoo.com> #2
Yigit, do you have time to fix it?
reemission of the same liveData is racy
reemission of the same liveData is racy
ap...@google.com <ap...@google.com> #3
yea i'll take it.
jb...@google.com <jb...@google.com> #4
Thanks for the detailed analysis. This may not be an issue anymore since we've started using Main.immediate there but I' not sure; I'll try to create a test case.
Description
Component used: Fragment
Version used: 1.3.0-beta01
Devices/Android versions reproduced on: Pixel 2 API 29 emulator
Muzei's
main
module usesTRANSIT_FADE
to swap between fragments based on whether Muzei is your current wallpaper. This listener is set on aFlow
that 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)
inMuzeiApplication
in themain
moduleExpected behavior: Next screen (
TutorialFragment
) appearsActual behavior: New fragment does not appear, despite going to
RESUMED
stateAdditional information: If I attach the layout inspector, the fragment magically appears!
Removing the
TRANSIT_FADE
or using the old state manager causes everything to work as expected as well.