RecyclerView点击跳转创建Intent时，因Context空指针引发崩溃求助

Hey there! That crash you’re seeing—Attempt to invoke virtual method 'java.lang.String android.content.Context.getPackageName()' on a null object reference—is a super common pitfall when working with RecyclerView click listeners and Intents. Let’s break down exactly what’s happening and how to fix it.

Why This Happens #

The error tells us the Context you’re using to create your Intent is null. Intents need a valid Context to launch another Activity, so if that Context is missing, the app crashes immediately.

Common Causes & Fixes #

1. Your Adapter’s Context Isn’t Properly Initialized

Many developers forget to pass or store a valid Context in their RecyclerView Adapter. If you’re trying to use a Context that was never set, it’ll be null.

Fix:
Pass a Context to your Adapter’s constructor and store it as a member variable:

public class VenueAdapter extends RecyclerView.Adapter<VenueAdapter.VenueViewHolder> {
    private final Context mContext;
    private final List<Venue> mVenueList;

    // Constructor that accepts Context and your data list
    public VenueAdapter(Context context, List<Venue> venueList) {
        mContext = context;
        mVenueList = venueList;
    }

    // ... ViewHolder and other methods ...
}

Then, when creating the Adapter in your Activity/Fragment, pass the correct Context:

• In an Activity: new VenueAdapter(this, venueList)
• In a Fragment: new VenueAdapter(getActivity(), venueList) (make sure to call this after the Fragment is attached to the Activity, like in onViewCreated)

2. You’re Using an Invalid Context in the Click Listener

If you’re fetching the Context directly from the item view (e.g., itemView.getContext()), there’s a small chance it could be null if the view isn’t fully attached to the window yet.

Fix:
Either use the Adapter’s stored Context, or add a null check before using the view’s Context:

@Override
public void onBindViewHolder(@NonNull VenueViewHolder holder, int position) {
    Venue currentVenue = mVenueList.get(position);

    // Set up your image and other views here...

    // Set click listener for the item
    holder.itemView.setOnClickListener(v -> {
        // Option 1: Use the Adapter's stored Context (safer)
        Intent detailIntent = new Intent(mContext, VenueDetailActivity.class);
        // Pass venue data to the detail Activity
        detailIntent.putExtra("VENUE_ID", currentVenue.getId());
        detailIntent.putExtra("VENUE_NAME", currentVenue.getName());
        mContext.startActivity(detailIntent);

        // Option 2: Use view's Context with a null check
        /*
        Context viewContext = v.getContext();
        if (viewContext != null) {
            Intent detailIntent = new Intent(viewContext, VenueDetailActivity.class);
            detailIntent.putExtra("VENUE_DATA", currentVenue);
            viewContext.startActivity(detailIntent);
        }
        */
    });
}

3. You Accidentally Used a Null Context from a Fragment

If you’re working in a Fragment, calling getActivity() too early (like in onCreate before the Fragment is attached) will return null.

Fix:
Wait until the Fragment is attached to the Activity to initialize your Adapter. Do this in onViewCreated instead of onCreate:

@Override
public void onViewCreated(@NonNull View view, @Nullable Bundle savedInstanceState) {
    super.onViewCreated(view, savedInstanceState);
    RecyclerView recyclerView = view.findViewById(R.id.venue_recycler);
    // Initialize your list and Adapter here
    List<Venue> venueList = getVenueData();
    VenueAdapter adapter = new VenueAdapter(getActivity(), venueList);
    recyclerView.setAdapter(adapter);
    // ... set LayoutManager etc.
}

Quick Debugging Tip #

If you’re still stuck, add a log statement right before creating the Intent to check if your Context is null:

Log.d("VenueAdapter", "Context is null? " + (mContext == null));

This will confirm whether the issue is indeed a missing Context, or something else sneaking in.

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