RecyclerView项内删除按钮点击致Activity重启，如何阻止该行为？

Hey there! Let's dig into why your MainActivity is restarting and switching back to the first bottom navigation item when you tap the delete button in your RecyclerView. I'll walk you through the most common causes and actionable fixes based on your setup (Firebase-backed data, bottom nav with 3 menus).

First: Check Your Delete Button Click Logic #

The most likely culprit is unintended code in your adapter's delete button listener that triggers an Activity restart or navigation switch. Let's break this down:

1. Remove Any Accidental Activity Restart Code #

Double-check your adapter's onBindViewHolder or ViewHolder click listener for code that explicitly restarts the MainActivity. For example, if you have something like this:

holder.deleteButton.setOnClickListener(v -> {
    // ❌ This will restart the Activity - delete this line!
    v.getContext().startActivity(new Intent(v.getContext(), MainActivity.class));
    
    // Your Firebase update code...
});

Delete any startActivity calls targeting your MainActivity here—you don't need to restart the app just to update a Firebase field and refresh the RecyclerView.

2. Update Firebase and RecyclerView Without Restarting #

Your delete logic should only update Firebase, then refresh the RecyclerView's dataset (not the entire Activity). Here's a corrected example:

@Override
public void onBindViewHolder(@NonNull YourViewHolder holder, int position) {
    YourDataModel item = mDataList.get(position);
    
    holder.deleteButton.setOnClickListener(v -> {
        // Update Firebase's "saved" field
        FirebaseFirestore.getInstance()
            .collection("your_collection")
            .document(item.getDocumentId())
            .update("saved", false)
            .addOnSuccessListener(aVoid -> {
                // ✅ Only refresh the RecyclerView, not the Activity
                mDataList.remove(position);
                notifyItemRemoved(position);
                // If using ListAdapter, use submitList instead:
                // submitList(new ArrayList<>(mDataList));
            })
            .addOnFailureListener(e -> {
                Toast.makeText(v.getContext(), "Delete failed: " + e.getMessage(), Toast.LENGTH_SHORT).show();
            });
    });
}

Second: Check Bottom Navigation Logic #

If your MainActivity uses a BottomNavigationView, make sure your delete operation isn't accidentally triggering a menu switch:

• Open your MainActivity code and look for bottomNavigationView.setSelectedItemId(R.id.first_menu)—ensure this line only runs when the user manually taps the first menu item, not in your Firebase success/failure callbacks.
• Verify your OnNavigationItemSelectedListener only switches fragments when the user taps a nav item, not when data changes. Example of correct nav logic:

BottomNavigationView bottomNav = findViewById(R.id.bottom_nav);
bottomNav.setOnNavigationItemSelectedListener(item -> {
    switch (item.getItemId()) {
        case R.id.first_menu:
            getSupportFragmentManager().beginTransaction()
                .replace(R.id.fragment_container, FirstFragment.class, null)
                .commit();
            return true;
        case R.id.third_menu:
            // Fragment containing your RecyclerView
            getSupportFragmentManager().beginTransaction()
                .replace(R.id.fragment_container, SavedItemsFragment.class, null)
                .commit();
            return true;
        // Handle other menus...
        default:
            return false;
    }
});
// Set default selected item ONCE when the Activity starts
bottomNav.setSelectedItemId(R.id.first_menu);

Third: Rule Out Firebase Listener Issues #

If you're using a SnapshotListener or LiveData to observe Firebase changes, make sure the callback doesn't trigger an Activity restart:

• Avoid calling recreate() or finish() followed by startActivity() in your Firebase data observer.
• The observer should only update your RecyclerView's adapter data (e.g., adapter.submitList(newData)), not touch the Activity lifecycle.

Quick Debug Tip #

If you're still stuck, add log statements in your delete button listener and Firebase callbacks to track exactly when the Activity restarts. Use:

Log.d("MainActivity", "Delete button tapped");
Log.d("MainActivity", "Firebase update success");

Then check Logcat to see if the restart happens immediately after tapping the button or after the Firebase callback—this will narrow down the issue.

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