Issue with backstack and bottomnav in kotlin-CodePudding

The

Where I add HomeF in main container which includes all bottom nav tab, and all bottom nav tab will open in home container, and those fragment which are not part of bottom nav will open in main container. I generally add(not replace) all the fragments in main container and set add to back stack , so that if user goes from profile (home_container) to something in main container , while backstack we can pop the top fragment and user will be seeing profile.

CodePudding user response：

Now you are managing the back stack through the integerDeque array.

When you go to a new BottomNavigationView fragment; you added its id to the array if it doesn't already exist.

When you pop up the back stack; the fragment at the top is kicked off the array.

But since you pushed all those ids in the bottomNavigationView.setOnItemSelectedListener callback; then the integerDeque array only contains BottomNavigationView fragments ids.

And as the Edit_Profile fragment is not a part of BottomNavigationView fragments, then it won't be added/popped off the queue. Instead when you try to popup the back stack whenever the Edit_Profile fragment is shown; the normal behavior you manage in the onBackPressed() continues and the Profile_Fragment id will pop up from the queue making you return to the preceding fragment (Home_Fragment) in your mentioned example.

A little fix to this is to consider adding an id into the queue when you transact to Edit_Profile fragment so that this id is popped off the queue resulting in back to Profile_Fragment fragment.

You can do that with the fragment's id in order to make sure it's unique:

editProfileButton!!.setOnClickListener(View.OnClickListener { v: View? -> val edit_profile: Fragment = Edit_Profile() requireActivity().getSupportFragmentManager() .beginTransaction() .add(R.id.fragment_container, edit_profile,"TAG") .addToBackStack("TAG") .commit() (requireActivity() as MainActivity).integerDeque.push(id) // <<<< pushing id to the queue })

This should fix your problem.

Side tips:

Use setOnItemSelectedListener instead of setOnNavigationItemSelectedListener on the BNV as the latter is deprecated.

Return true instead of false from setOnItemSelectedListener callback as this should consume the event and mark the BNV as selected.

In Edit_Profile transaction replace the fragment instead of adding it with add as already the container is consumed; and this would make you avoid overlapping fragments in the container.

In onBackPressed(); you'd replace loadFragments(..) with bottomNavigationView.selectedItemId = integerDeque.peek(); this could be lighter to reuse the same fragment instead of redoing the transaction.