Fragment显示Dialog时生命周期调用及返回后View为空问题咨询

Hey there, let's break down your problem step by step. First, let's clarify the lifecycle behavior when a Dialog is shown from a Fragment, then figure out why your View is null when returning, and finally fix it.

一、Dialog显示期间Fragment的生命周期变化 #

First off, let's get this straight: when you show a regular, non-fullscreen Dialog (like your DialogSearch), your Fragment won't trigger any destruction or recreation lifecycle methods. That means:

• Methods like onDestroyView(), onDestroy(), onDetach() won't be called
• You also won't see onCreateView() or onViewCreated() fire again unless something else forces a view recreation

The only exception here is if you're using a fullscreen Dialog (or a Dialog style that triggers an Activity configuration change)—in that rare case, your Fragment might go through a full destroy-recreate cycle: onPause() → onStop() → onDestroyView() → onDestroy() → onDetach(), then rebuild via onAttach() → onCreate() → onCreateView(). But this is not the default behavior for standard Dialogs.

二、Why your View is null when returning to the Fragment #

Looking at your code, the most likely culprit is that your Fragment's view got destroyed while the Dialog was showing, but you're still referencing the old view, textView, etc. Common scenarios for this:

• The system reclaimed your Activity (and thus the Fragment) while the Dialog was open (this happens when the app is in the background and low on memory)
• Some other operation (like a Fragment transaction) removed/replaced your Fragment while the Dialog was active, so when you close the Dialog, you're left with a Fragment instance that has no attached view
• You used the Activity's FragmentManager to show the Dialog, which decouples the Dialog from your Fragment's lifecycle—so the Dialog can stay open even if the Fragment is destroyed

三、Fixes for your code #

Here are concrete fixes you can apply to your MyFragment class:

1. Bind the Dialog to your Fragment's lifecycle #

Instead of using getActivity().getSupportFragmentManager(), use getChildFragmentManager()—this ties the Dialog directly to your Fragment, so it gets destroyed when the Fragment does, preventing orphaned Dialogs and state mismatches. Also, add a check to make sure the Fragment is still attached before showing the Dialog:

actionButton.setOnClickListener(new View.OnClickListener() {
    @Override
    public void onClick(View view) {
        // Verify the Fragment is still active and has a view
        if (isAdded() && getView() != null) {
            DialogSearch search = new DialogSearch();
            search.show(getChildFragmentManager(), "MyDialog");
        }
    }
});

2. Use onViewCreated() for view initialization (more standard practice) #

Move your view setup logic to onViewCreated() instead of onCreateView()—this ensures that every time your Fragment's view is created (including after recreation), your views are reinitialized properly:

@Override
public View onCreateView(final LayoutInflater inflater, @Nullable ViewGroup container, @Nullable Bundle savedInstanceState) {
    // Just inflate the layout here
    return inflater.inflate(R.layout.fragment_read, container, false);
}

@Override
public void onViewCreated(@NonNull View view, @Nullable Bundle savedInstanceState) {
    super.onViewCreated(view, savedInstanceState);
    // Initialize views here
    textView = view.findViewById(R.id.txtSaved);
    actionButton = view.findViewById(R.id.floatingActionButton);
    
    actionButton.setOnClickListener(new View.OnClickListener() {
        @Override
        public void onClick(View v) {
            if (isAdded()) {
                DialogSearch search = new DialogSearch();
                search.show(getChildFragmentManager(), "MyDialog");
            }
        }
    });
}

3. Clear view references in onDestroyView() #

This prevents memory leaks and makes it clear when your views are no longer valid:

@Override
public void onDestroyView() {
    super.onDestroyView();
    // Null out references to avoid memory leaks and null pointer issues
    view = null;
    textView = null;
    actionButton = null;
}

内容的提问来源于stack exchange，提问作者Amir2511