Problems with Android Fragment back stack

by

Explanation: on what’s going on here?

If we keep in mind that .replace() is equal with .remove().add() that we know by the documentation:

Replace an existing fragment that was added to a container. This is essentially the same as calling remove(Fragment) for all currently added fragments that were added with the same containerViewId and then add(int, Fragment, String) with the same arguments given here.

then what’s happening is like this (I’m adding numbers to the frag to make it more clear):

// transaction.replace(R.id.detailFragment, frag1);
Transaction.remove(null).add(frag1)  // frag1 on view

// transaction.replace(R.id.detailFragment, frag2).addToBackStack(null);
Transaction.remove(frag1).add(frag2).addToBackStack(null)  // frag2 on view

// transaction.replace(R.id.detailFragment, frag3);
Transaction.remove(frag2).add(frag3)  // frag3 on view

(here all misleading stuff starts to happen)

Remember that .addToBackStack() is saving only transaction not the fragment as itself! So now we have frag3 on the layout:

< press back button >
// System pops the back stack and find the following saved back entry to be reversed:
// [Transaction.remove(frag1).add(frag2)]
// so the system makes that transaction backward!!!
// tries to remove frag2 (is not there, so it ignores) and re-add(frag1)
// make notice that system doesn't realise that there's a frag3 and does nothing with it
// so it still there attached to view
Transaction.remove(null).add(frag1) //frag1, frag3 on view (OVERLAPPING)

// transaction.replace(R.id.detailFragment, frag2).addToBackStack(null);
Transaction.remove(frag3).add(frag2).addToBackStack(null)  //frag2 on view

< press back button >
// system makes saved transaction backward
Transaction.remove(frag2).add(frag3) //frag3 on view

< press back button >
// no more entries in BackStack
< app exits >

Possible solution

Consider implementing FragmentManager.BackStackChangedListener to watch for changes in the back stack and apply your logic in onBackStackChanged() methode:

More Related Contents:

  1. How to resume existing Fragment from BackStack
  2. Programmatically go back to the previous fragment in the backstack
  3. How can I maintain fragment state when added to the back stack?
  4. Fragment onResume() & onPause() is not called on backstack
  5. Fragments onResume from back stack
  6. Android: Fragments backStack
  7. How to pop fragment off backstack
  8. Android – save/restore fragment state
  9. get the latest fragment in backstack
  10. Send data from activity to fragment in Android
  11. Best practice for instantiating a new Android Fragment
  12. ViewPager and fragments — what’s the right way to store fragment’s state?
  13. Dynamically changing the fragments inside a fragment tab host?
  14. How to send data from one Fragment to another Fragment?
  15. Fragment over another fragment issue
  16. Android ViewPager get the current View
  17. Fragment-Fragment communication in Android
  18. How to use Fragments in Android
  19. What is the benefit of using Fragments in Android, rather than Views?
  20. IllegalStateException: Can’t change container ID of Fragment
  21. using enableAutoManage() in fragment
  22. Fragment must be a public static class to be properly recreated from instance state
  23. android:configChanges=”orientation” does not work with fragments
  24. Google Maps Fragment returning null inside a fragment
  25. Why use Fragments? [duplicate]
  26. Trying to remove fragment from view gives me NullPointerException on mNextAnim
  27. Is there a method that works like start fragment for result?
  28. Replacing ViewPager with Fragment – Then Navigating Back
  29. FragmentActivity can not be tested via ActivityInstrumentationTestCase2
  30. Kotlin: open new Activity inside of a Fragment

Leave a Comment