Fixed
Status Update
No update yet.
Comments
il...@google.com
The first part of this was (inadvertently) fixed as part of https://android-review.googlesource.com/966056 where now STARTED and RESUMED are nested appropriately.
il...@google.com
ap...@google.com
Project: platform/frameworks/support
Branch: androidx-master-dev
commit 68cde48d6d96fcac7e97d336d7380c9d083a46b3
Author: Ian Lake <ilake@google.com>
Date: Fri May 24 14:48:35 2019
Properly nest downward Fragment Lifecycle calls
Ensure that child Fragments get the downward
Lifecycle calls before the parent Fragment does,
ensuring the proper nesting.
Test: new test, re-ran the test suite
BUG: 133497591
Change-Id: I0260c9a5b0c487dc091a79787fb0e084b5a10b56
M fragment/src/androidTest/java/androidx/fragment/app/FragmentArchLifecycleTest.kt
M fragment/src/main/java/androidx/fragment/app/Fragment.java
https://android-review.googlesource.com/970107
https://goto.google.com/android-sha1/68cde48d6d96fcac7e97d336d7380c9d083a46b3
Branch: androidx-master-dev
commit 68cde48d6d96fcac7e97d336d7380c9d083a46b3
Author: Ian Lake <ilake@google.com>
Date: Fri May 24 14:48:35 2019
Properly nest downward Fragment Lifecycle calls
Ensure that child Fragments get the downward
Lifecycle calls before the parent Fragment does,
ensuring the proper nesting.
Test: new test, re-ran the test suite
BUG: 133497591
Change-Id: I0260c9a5b0c487dc091a79787fb0e084b5a10b56
M fragment/src/androidTest/java/androidx/fragment/app/FragmentArchLifecycleTest.kt
M fragment/src/main/java/androidx/fragment/app/Fragment.java
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.