OnCreateView called multiple times / Working with ActionBar and Fragments

by

When you call FragmentTransaction.replace(…), Android will effectively perform a sequence of FragmentTransaction.remove(…) (for all Fragments currently added to that container) and FragmentTransaction.add(…) (for your supplied Fragment). Removing a Fragment from the FragmentManager will cause the Fragment to be destroyed and its state will no longer be managed. Most noticeably, when you re-add the Fragment all of the views will have been reset. Note: since you are reusing the same Fragment instance, the Fragment will still keep the value any instance variables.

One solution to this problem would be to use FragmentTransaction.detach(Fragment) and FragmentTransaction.attach(Fragment) when switching. This will cause the Fragment views to be recreated (onDestroyView() & onCreateView() will be called), but the instance state bundle will be saved and given back to you between calls and so the view state can be maintained. This is the approach taken by FragmentPagerAdapter when it tries to switch between Fragments.

Alternatively, you could allow the Fragments to be destroyed, but maintain their saved state for them independently. This would use less memory, at the expense of a slower switching time. Methods of note would be FragmentManager.saveFragmentInstanceState(Fragment) and FragmentManager.setInitialSavedState(Fragment.SavedState), in conjuction with adding/removing. This is the approach taken by FragmentStatePagerAdapter.

You can have a look at the source for FragmentPagerAdapter and the source for FragmentStatePagerAdapter for implementation hints.

More Related Contents:

  1. Difference between extending LifecycleActivity,Activity,ActionbarActivity & AppCompactActivity?
  2. Coordinator Layout with Toolbar in Fragments or Activity
  3. onActivityResult is not being called in Fragment
  4. Communicating between a fragment and an activity – best practices
  5. OnActivityResult method is deprecated, what is the alternative?
  6. getActivity() returns null in Fragment function
  7. Dilemma: when to use Fragments vs Activities:
  8. Why fragments, and when to use fragments instead of activities?
  9. Switching between Android Navigation Drawer image and Up caret when using fragments
  10. Error while Running Android Application – Could not initialize OpenglES emulation, use ‘-gpu off’ to disable it
  11. Sharing data between fragments using new architecture component ViewModel
  12. Android Fragment lifecycle over orientation changes
  13. Android. Fragment getActivity() sometimes returns null
  14. Start an activity from a fragment
  15. Returning from an activity using navigateUpFromSameTask()
  16. Further understanding setRetainInstance(true)
  17. How to wrap the height of a ViewPager to the height of its current Fragment?
  18. One Activity and all other Fragments [closed]
  19. What are the differences between activity and fragment?
  20. converting activity into fragment
  21. How to get Toolbar from fragment?
  22. When a Fragment is replaced and put in the back stack (or removed) does it stay in memory?
  23. How to listen for preference changes within a PreferenceFragment?
  24. Calling startIntentSenderForResult from Fragment (Android Billing v3)
  25. How do you create Preference Activity and Preference Fragment on Android?
  26. android:configChanges=”orientation” does not work with fragments
  27. Navigation Drawer with backword compatibility android
  28. Data Sharing between Fragments and Activity in Android
  29. Retain Fragment state between Activities
  30. Android Fragment onCreateView vs. onActivityCreated

Leave a Comment