Android Studio新手：Fragment中RecyclerView调用setLayoutManager触发空指针异常

Hey there! Let's sort out that frustrating NullPointerException you're facing when trying to set up a RecyclerView in your Fragment. The error message tells us exactly what's wrong: you're calling setLayoutManager() on a null RecyclerView instance—meaning your app can't find the RecyclerView in your layout when it tries to configure it. Here's how to fix it step by step:

1. Double-check your RecyclerView's ID in the layout XML #

First, make sure your fragment's layout file has a RecyclerView with a correctly defined ID. Typos here are super common! For example:

<!-- Correct example -->
<android.support.v7.widget.RecyclerView
    android:id="@+id/recycler_view"
    android:layout_width="match_parent"
    android:layout_height="match_parent" />

Verify that the ID you use in your Java code matches exactly what's in the XML (capitalization, spelling, all of it).

2. Get the RecyclerView instance correctly in your Fragment #

This is the most frequent culprit. In Fragments, you can't use findViewById() directly in onCreate()—you need to use the inflated view from onCreateView() or onViewCreated() to locate your RecyclerView.

Here's the right way to do it in onCreateView():

@Override
public View onCreateView(LayoutInflater inflater, ViewGroup container, Bundle savedInstanceState) {
    // Inflate your fragment's layout first
    View rootView = inflater.inflate(R.layout.your_fragment_layout, container, false);
    
    // Find the RecyclerView using the inflated root view
    RecyclerView recyclerView = rootView.findViewById(R.id.recycler_view);
    
    // Now you can safely set the LayoutManager
    recyclerView.setLayoutManager(new LinearLayoutManager(getContext()));
    
    // Don't forget to set your adapter next!
    // recyclerView.setAdapter(yourAdapter);
    
    return rootView;
}

Or if you prefer using onViewCreated():

@Override
public void onViewCreated(@NonNull View view, @Nullable Bundle savedInstanceState) {
    super.onViewCreated(view, savedInstanceState);
    
    RecyclerView recyclerView = view.findViewById(R.id.recycler_view);
    recyclerView.setLayoutManager(new LinearLayoutManager(getContext()));
    // Set adapter here too
}

Why this works? The Fragment's view hierarchy isn't fully created until onCreateView() returns, so calling findViewById() before that will always return null.

3. Confirm your RecyclerView dependency is added #

Since you're using the support library version of RecyclerView, make sure your app-level build.gradle file includes the correct dependency:

implementation 'com.android.support:recyclerview-v7:28.0.0'

Adjust the version number to match the rest of your support library dependencies (if you're using AndroidX, you'd use androidx.recyclerview:recyclerview:1.x.x instead, but stick with the support version since that's what your code uses).

4. If you're using ViewBinding, use it properly #

If you've enabled ViewBinding in your project, avoid mixing it with findViewById()—use the binding object to access your RecyclerView instead:

private YourFragmentLayoutBinding binding;

@Override
public View onCreateView(LayoutInflater inflater, ViewGroup container, Bundle savedInstanceState) {
    binding = YourFragmentLayoutBinding.inflate(inflater, container, false);
    return binding.getRoot();
}

@Override
public void onViewCreated(@NonNull View view, @Nullable Bundle savedInstanceState) {
    super.onViewCreated(view, savedInstanceState);
    
    // Access RecyclerView directly via binding
    binding.recyclerView.setLayoutManager(new LinearLayoutManager(getContext()));
}

@Override
public void onDestroyView() {
    super.onDestroyView();
    binding = null; // Prevent memory leaks
}

Most of the time, fixing the way you retrieve the RecyclerView instance (step 2) will resolve the null pointer. Give these steps a try, and let me know if you run into any other issues!

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