Android WebView Fragment应用崩溃：NullPointerException问题求助

Hey there, let's break down why your app is crashing after adding Fragment navigation and fix it up step by step!

What's Causing the Crash? #

The NullPointerException points directly to this line:

((MainActivity) getActivity()).setUrl(url);

Here's the root issue: when you use fragmentTransaction.replace() to switch to a new Fragment, your original Saying Fragment gets detached from the Activity (its onDetach() lifecycle method runs). But if the WebView was still loading a page in the background, its onPageStarted callback will fire later—at that point, the Fragment isn't attached to any Activity anymore, so getActivity() returns null. Trying to call setUrl() on that null reference causes the crash.

Solutions to Fix the Crash #

1. Quick Fix: Add a Null Check

First, let's stop the crash immediately by verifying the Activity is valid before calling setUrl():

@Override
public void onPageStarted(WebView view, String url, Bitmap favicon) {
    super.onPageStarted(view, url, favicon);
    
    // Check if the Fragment is still attached to a valid MainActivity
    Activity currentActivity = getActivity();
    if (currentActivity != null && currentActivity instanceof MainActivity) {
        ((MainActivity) currentActivity).setUrl(url);
    }
    
    progressBar.setVisibility(View.VISIBLE);
}

This prevents the crash, but we should also address the root cause to avoid leftover callbacks.

2. Clean Up WebView in Fragment Lifecycle

Add code to your Saying Fragment's onDetach() method to disable WebView callbacks and stop ongoing loads:

@Override
public void onDetach() {
    super.onDetach();
    if (home_web != null) {
        // Clear the WebViewClient so no more callbacks fire
        home_web.setWebViewClient(null);
        // Stop any active page load
        home_web.stopLoading();
    }
}

This ensures that once the Fragment is removed, the WebView won't try to communicate with a non-existent Activity.

3. Robust Fix: Use an Interface (Best Practice)

As an Android beginner, it's a great habit to avoid hard-casting to your Activity class. Instead, use an interface to communicate between Fragment and Activity—this makes your code more flexible and less error-prone.

Step 1: Create an interface (you can put this inside your Fragment or a separate file):

public interface UrlUpdateListener {
    void setUrl(String url);
}

Step 2: Make your MainActivity implement this interface:

public class MainActivity extends AppCompatActivity 
    implements NavigationView.OnNavigationItemSelectedListener, 
               View.OnClickListener,
               UrlUpdateListener { // Add this interface
    
    // ... your existing code ...

    // Implement the interface method
    @Override
    public void setUrl(String url) {
        // Put your original setUrl logic here
    }
}

Step 3: Update your Saying Fragment to use the interface:

private UrlUpdateListener mUrlUpdateListener;

@Override
public void onAttach(@NonNull Context context) {
    super.onAttach(context);
    // Initialize the listener when the Fragment attaches to the Activity
    try {
        mUrlUpdateListener = (UrlUpdateListener) context;
    } catch (ClassCastException e) {
        throw new ClassCastException(context.toString() + " must implement UrlUpdateListener");
    }
}

@Override
public void onDetach() {
    super.onDetach();
    // Nullify the listener when the Fragment detaches
    mUrlUpdateListener = null;
}

// Update onPageStarted to use the listener
@Override
public void onPageStarted(WebView view, String url, Bitmap favicon) {
    super.onPageStarted(view, url, favicon);
    
    if (mUrlUpdateListener != null) {
        mUrlUpdateListener.setUrl(url);
    }
    
    progressBar.setVisibility(View.VISIBLE);
}

This approach decouples your Fragment from the specific Activity class, making your code more maintainable and less likely to break if you adjust your Activity structure later.

Why This Works #

When you switch Fragments with replace(), the old Fragment is detached, so onDetach() runs and sets mUrlUpdateListener to null. If the WebView tries to fire onPageStarted after that, the null check prevents the crash. Plus, using an interface avoids the risk of casting to the wrong Activity type.

内容的提问来源于stack exchange，提问作者Noor Ali Khan