When to use FragmentManager::putFragment and getFragment

by

The basic answer:

These are only useful when implementing onSaveInstanceState() and restoring that state in onCreate(). If you are not implementing onSaveInstanceState(), you can forget about these methods and pretend like they don’t exist.

The problem they are solving: if you want to save a reference to a fragment in your “saved instance state,” you can’t just put an object reference in there. First because well you can’t put plain object in a Bundle. 🙂 And the reason for this is that the point of that saved state is for it to be copied out of your process, so if your process needs to be killed, it can later be copied back in to a new process for you to re-initialize your activity/fragment from. A raw object is only meaningful in the context of the process it is running in, so it isn’t possible to correctly copy the reference to such an object out of your current process and in to another.

So what putFragment()/getFragment() do is place a piece of data in the given Bundle that can identify that fragment across to a new instance of your activity/fragment in another process. Exactly what this representation is, is not defined, but in the current implementation it is the internal integer identifier for that fragment, which will be used later when the FragmentManager needs to re-create that fragment from a previously saved state… it is re-created with that same identifier, so when you then call getFragment() it can retrieve the integer, and use that to determine the correct Fragment object to return to the caller that corresponds to the one that was previously saved.

More Related Contents:

  1. How to pass values between Fragments
  2. How to implement a ViewPager with different Fragments / Layouts
  3. OnActivityResult method is deprecated, what is the alternative?
  4. Basic communication between two fragments
  5. getActivity() returns null in Fragment function
  6. Error inflating class fragment
  7. Receive result from DialogFragment
  8. Sharing data between fragments using new architecture component ViewModel
  9. Fragment is not being replaced but put on top of the previous one
  10. Android: Fragments backStack
  11. reusing fragments in a fragmentpageradapter
  12. Alternatives to PreferenceFragment with android-support-v4
  13. I get the error “Unreachable statement” return in android
  14. When a Fragment is replaced and put in the back stack (or removed) does it stay in memory?
  15. How to listen for preference changes within a PreferenceFragment?
  16. In Fragment on back button pressed Activity is blank
  17. How do you create Preference Activity and Preference Fragment on Android?
  18. refresh fragment UI from fragmentActivity
  19. Android – save/restore fragment state
  20. Coordinator Layout with Toolbar in Fragments or Activity
  21. findFragmentById always returns null
  22. How to replace the activity’s fragment from the fragment itself?
  23. isValidFragment Android API 19
  24. What’s the difference between detaching a Fragment and removing it?
  25. Is it possible to access the current Fragment being viewed by a ViewPager?
  26. How I can retrieve current fragment in NavHostFragment?
  27. Button Listener for button in fragment in android
  28. Disable multi finger touch in my app [duplicate]
  29. Android replace fragment still displays some of the replaced fragment
  30. Activity vs Fragment Lifecycle [closed]

Leave a Comment