Fixed
Status Update
Comments
ap...@google.com <ap...@google.com> #2
Yigit, do you have time to fix it?
reemission of the same liveData is racy
reemission of the same liveData is racy
ju...@google.com <ju...@google.com> #4
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
The reason for this is that if a fragment on the back stack is destroyed while it is still created, we ensure the entry makes it to destroyed, but failed to clear some associated state. The state remains around and prevents us from popping the Nav back stack during system back.