IssueTracker

Component used: Navigation
Version used: 1.0.0-alpha11

I'm seeing some strange behaviour when pressing back button and transistion back to a fragment from a fragment of the same id.
My app uses some generic fragment structures that are driven by args passed in, as such there are places like:

FragmentA -> FragmentB -> FragmentB -> FragmentC

However if the back button is pressed on the second instance of FragmentB, FragmentA is replaced in the navhost while the navgraph correctly displays in the toolbar. Forward navigation from this point however is missing from the navgraph and results in an IllegalStateException with the action 'not found' in the graph, unless the back button is pressed again (pushing the navgraph destination back to FragmentA)

Is this intended behaviour? If so is there a way to declare FragmentB as 'stackable'?