Fixed
Status Update
Comments
ap...@google.com <ap...@google.com> #2
Using navigation version 2.6.0 and 2.7.1 the issue still persists.
After further investigation, the behaviour can be corrected by filtering on backstack entries where current state is at least started. In my opinion the name visibleEntries is misleading if it contains entries that are not actually visible or in transition.
jb...@google.com <jb...@google.com> #3
Note that as per the visibleEntries
documentationCREATED
state - those are the entries that are in the process of being removed (i.e., they are no longer in the back stack, but have not yet marked their transition as complete).
It is a bug that those entries aren't removed when their exit animation completes and that's what we'll be looking into.
Description
Component used: Activity Version used: 1.2.0-alpha07
If you register for a result with a
LifecycleOwner
and your activity goes through process death and restoration, once it is created again if there is already result a waiting to be returned to theLifecycleOwner
an observer is added to wait until theLifecycle
isSTARTED
. When the lifecycle owner is unregistered, the observer is never removed.We should keep track of any observers added to the
LifecycleOwner
and remove them if the callback for the lifecycle owner is ever unregistered.