Fixed
Status Update
No update yet.
Comments
il...@google.com
Yigit, do you have time to fix it?
reemission of the same liveData is racy
reemission of the same liveData is racy
il...@google.com
ap...@google.com
yea i'll take it.
il...@google.com
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
Version used: 1.1.0-alpha09
Devices/Android versions reproduced on:
When using nested fragments such as:
Parent
-- Child
I'd expect the Lifecycle changes of these fragments to be properly nested:
Parent CREATED
Child CREATED
Parent STARTED
Child STARTED
Parent RESUMED
Child RESUMED
---
Child PAUSED
Parent PAUSED
Child STOPPED
Parent STOPPED
Child DESTROYED
Parent DESTROYED
But I'm not seeing that - it seems like the opposite is the case - the child gets changed first on the way up and after on the way down, perfectly *not* nesting.