You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This kept happening for me on 1x snapshot and so while trying to come up with the minimal example, I have found that I've actually misguided you :(
I wasn't using backStack.newRoot(), but rather I was using backStack.singleTop().
But still, this singleTop call should result in a completely new hierarchy where even the root node is different from the previously active one, and so I believe it still should call onDestroy on inactive ones?
Here I've build a one-file sample which you can insert in some project, then make that activity a default one and run the app.
Steps to reproduce:
Click on buttons until you arrive to the "main screen"
@dimsuz I've just checked out your example and it look like you're using singleTop(Main) while backStack has active Login navTarget. It results in LoginNode subtree moving into STASHED, not DESTOYED state which is correct.
More info here
Similarly, can be reproduced following these steps:
Push two
Grandchild one
clickNavigate to child one
The text was updated successfully, but these errors were encountered: