Why do I want to avoid non-default constructors in fragments?

by

It seems like none of the answers actually answer “why use bundle for passing parameters rather than non default constructors”

The reason why you should be passing parameters through bundle is because when the system restores a fragment (e.g on config change), it will automatically restore your bundle.

The callbacks like onCreate or onCreateView should read the parameters from the bundle – this way you are guaranteed to restore the state of the fragment correctly to the same state the fragment was initialised with (note this state can be different from the onSaveInstanceState bundle that is passed to the onCreate/onCreateView)

The recommendation of using the static newInstance() method is just a recommendation. You can use a non default constructor but make sure you populate the initialisation parameters in the bundle inside the body of that constructor. And read those parameters in the onCreate() or onCreateView() methods.

More Related Contents:

  1. Retrieve a Fragment from a ViewPager
  2. Update ViewPager dynamically?
  3. Communicating between a fragment and an activity – best practices
  4. How do I get the currently displayed fragment?
  5. MapView in a Fragment (Honeycomb)
  6. Error while Running Android Application – Could not initialize OpenglES emulation, use ‘-gpu off’ to disable it
  7. How to handle Handler messages when activity/fragment is paused
  8. How to start Fragment from an Activity
  9. support FragmentPagerAdapter holds reference to old fragments
  10. Best practice for nested fragments in Android 4.0, 4.1 (
  11. How to add “Go Back” function in WebView inside Fragment?
  12. Android: Can you nest Fragments?
  13. Android.app Fragments vs. android.support.v4.app using ViewPager?
  14. What is the meaning of addToBackStack with null parameter?
  15. What are the differences between activity and fragment?
  16. Using onSaveInstanceState with fragments in backstack?
  17. How to pop fragment off backstack
  18. Start a fragment via Intent within a Fragment
  19. Difference between extending LifecycleActivity,Activity,ActionbarActivity & AppCompactActivity?
  20. Android: When is onCreateOptionsMenu called during Activity lifecycle?
  21. Performing action after fragment transaction animation is finished
  22. How do I open a new fragment from another fragment?
  23. Android 4.2: back stack behaviour with nested fragments
  24. SupportMapFragment does not support AndroidX Fragment
  25. Android Studio and android.support.v4.app.Fragment: cannot resolve symbol
  26. How to Handle backPress with Fragment
  27. How I can retrieve current fragment in NavHostFragment?
  28. Button Listener for button in fragment in android
  29. Disable multi finger touch in my app [duplicate]
  30. Activity vs Fragment Lifecycle [closed]

Leave a Comment