This method is deprecated.
This has been removed in favor of getParentFragmentManager() which
throws an IllegalStateException if the FragmentManager is null. Check if
isAdded() returns false to determine if the FragmentManager is
null.

This method is deprecated.
Instead of retaining the Fragment itself, use a non-retained Fragment and keep
retained state in a ViewModel attached to that Fragment. The ViewModel's constructor and
its onCleared() callback provide the signal for initial creation and final destruction of
the retained state.

This method is deprecated.
This has been renamed to getParentFragmentManager() to make it
clear that you are accessing the FragmentManager that contains this Fragment and not the
FragmentManager associated with child Fragments.

This method is deprecated.
Instead of retaining the Fragment itself, use a non-retained Fragment and keep
retained state in a ViewModel attached to that Fragment. The ViewModel's constructor and
its onCleared() callback provide the signal for initial creation and final destruction of
the retained state.

A default View can be returned by calling Fragment(int) in your
constructor. Otherwise, this method returns null.

It is recommended to only inflate the layout in this method and move
logic that operates on the returned View to onViewCreated(View, Bundle).

If you return a View from here, you will later be called in
onDestroyView() when the view is being released.

Parameters

inflater

LayoutInflater: The LayoutInflater object that can be used to inflate
any views in the fragment,

container

ViewGroup: If non-null, this is the parent view that the fragment's
UI should be attached to. The fragment should not add the view itself,
but this can be used to generate the LayoutParams of the view.

savedInstanceState

Bundle: If non-null, this fragment is being re-constructed
from a previous saved state as given here.