Fixed
Status Update
No update yet.
Comments
il...@google.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.
il...@google.com
ap...@google.com
Great! Thanks a lot, I'll look for the live updates soon!
il...@google.com
We've fixed the ordering issues for STARTED, RESUMED, PAUSED, STOPPED, DESTROYED (and DESTROYED on the view LifecycleOwner).
CREATED is a bit of a trickier case in how we dispatch those events that will have to be addressed as part ofhttps://issuetracker.google.com/issues/127528777
CREATED is a bit of a trickier case in how we dispatch those events that will have to be addressed as part of
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.