WAI
Status Update
No update yet.
Comments
as...@gmail.com
il...@google.com
va...@gmail.com
Thx, OnNavigationItemReselectedListener does it.
va...@gmail.com
But just curious, was there any reason to create a new instance of the fragment as a default behavior?
ar...@gmail.com
Well, I assume that bottom navigation should "cache" fragments. We can do that manually, but with Navigation library right now every time I go to another tab and return, it recreates the previous fragment.
il...@google.com
Navigation only stores the state of Fragments on the back stack. Multiple back stacks and supporting restoring a bottom tab in its previous position is being covered in https://issuetracker.google.com/issues/80029773
te...@gmail.com
This worked for me.
Description
Version used: 1.0.0-beta01
Devices/Android versions reproduced on: Android Pie, Pixel 2 XL
Clicking on the same menu item of BottomNavigationView creates a new fragment and destroys previously created fragment. Please consider this as a no-op and ignore these duplicate requests.
BottomNavigationView is set using NavigationUI.
NavigationUI.setupWithNavController( findViewById<BottomNavigationView>(R.id.bottomNavView),
findNavController(R.id.navHostFragment) )
Sample is available at