Fixed
Status Update
No update yet.
Comments
ap...@google.com
We have tests that ensure that onCreateView() is not called multiple times. If you can create a sample project that reproduces your issue, that would be most helpful.
jb...@google.com
I can guarantee that onCreateView() is indeed being called twice, and there is an onDestroyView() in between. So there may be an issue with your tests.
Were you not able to reproduce the problem with a BottomNavigationView and a call to startPostponedTransition()?
Were you not able to reproduce the problem with a BottomNavigationView and a call to startPostponedTransition()?
Description
Component used: Activity Version used: 1.2.0-alpha07
If you register for a result with a
LifecycleOwnerand your activity goes through process death and restoration, once it is created again if there is already result a waiting to be returned to theLifecycleOwneran observer is added to wait until theLifecycleisSTARTED. When the lifecycle owner is unregistered, the observer is never removed.We should keep track of any observers added to the
LifecycleOwnerand remove them if the callback for the lifecycle owner is ever unregistered.