Fixed
Status Update
No update yet.
Comments
ap...@google.com
Can you include a sample project that reproduces your issue?
Note that if you want to just return to your main graph (which I assume launched your login_nav_graph), you would want to leave out the app:destination="@id/main_nav_graph" line entirely as that will create a second instance of your main_nav_graph.
Description
Version used: 2.2.0-alpha03
To aid with debugging, it would be really helpful if we implemented toString() on NavDestination and its subclasses:
- NavDestination would print the idName if it exists and id otherwise, followed by the label
- NavGraph would call super.toString() and output the start destination (the ID if we don't have the start destination in the nodes)
- FragmentNavigator.Destination would also print the class name
- ActivityNavigator.Destination would also print the class name
This wouldn't output all of the information in each destination (that would be too much), but it would be enough to identify the destination in your graph