Fixed
Status Update
No update yet.
Comments
il...@google.com
I attach a project to reproduce the issue.
There are 2 buttons: one add a named fragment transaction (which you can remove with back) and the other navigate to another fragment using nav graph.
There are 2 buttons: one add a named fragment transaction (which you can remove with back) and the other navigate to another fragment using nav graph.
Description
It would be nice if navigation had an API that provided the currentBackStackEntry every time the destination changed.
Giving direct access to the backStackEntry would mean simplified interaction with components made available by the NavBackStackEntry like ViewModels, Lifecycles, SavedHandles, etc.