This is a top priority for us right now, only superseded by fixing issues blocking the 1.0 release. Short term: provide a public sample that shows our recommended implementation of multiple back stacks with Navigation using the current APIs (i.e., a separate NavHostFragment and navigation graph for each bottom navigation item).With that in mind, we’ll be doing two things: Even more unfortunately, Fragments do not offer an API for a system built on top of it (such as Navigation) to access the saved instance state and non configuration instance state (i.e., ViewModels) needed to write our own multiple back stack implementation while still using a single FragmentManager. Fragments, the default NavHost+Navigator implementation provided out of the box, does not support multiple back stacks within a single FragmentManager. This means that, out of the box, we are limited to the APIs and behavior contained within.

One very conscious decision we made for Navigation 1.0.0 was to depend on the 28.0.0 Support Library. Besides, Navigation replace the fragment thus causing the state lost. The main reason for this problem is that Navigation does not support multiple back stacks within a single FragmentManager. Is the lost of state after navigate away ( findNavController().navigate) or using BottomNavigationView With Jetpack Navigation UI.įor example, you might scroll midway using on RecylerView on a fragment, then you navigate to another fragment and come back again, the RecyclerView will be back to the top again. Implementation 'androidx.navigation:navigation-ui-ktx:$nav_version' Implementation 'androidx.navigation:navigation-fragment-ktx:$nav_version'

Android studio fragment backstack