Android开发：如何阻止返回键打开历史Fragment并直接退出应用？

Got it, let's sort out this back button behavior for you! You’re right that the FragmentManager’s back stack is the culprit here—every time you switch Fragments, if you’re adding them to the back stack, the system will pop the last one when you press back instead of exiting the app. Here’s how to fix this properly:

1. Stop Adding Fragments to the Back Stack #

The most direct fix is to remove any code that adds your Fragments to the back stack during navigation. When you perform a Fragment transaction (like replace()), calling addToBackStack() tells the system to keep that Fragment in the history. Just delete that line:

// Inside your BottomNavigationView's item selection listener
private void switchFragment(Fragment targetFragment) {
    FragmentTransaction transaction = getSupportFragmentManager().beginTransaction();
    transaction.replace(R.id.fragment_container, targetFragment);
    // REMOVE THIS LINE COMPLETELY: transaction.addToBackStack(null);
    transaction.commit();
}

With this change, switching between your three Fragments won’t leave any entries in the back stack. Pressing the system back button will now exit your MainActivity directly.

2. Override onBackPressed() as a Safety Net #

If you still see unwanted back stack behavior (maybe from older code or edge cases), you can force the app to exit by overriding the back button handler in your MainActivity:

@Override
public void onBackPressed() {
    // Close the entire app (works on Android 4.1/API 16+)
    finishAffinity();
    // If you only want to close MainActivity instead of the whole app, use:
    // finish();
}

finishAffinity() ensures all activities in your app’s task are closed, which is perfect if you want a full exit. Use finish() instead if you just want to close the current activity but keep the app running in the background.

3. Bonus: Reuse Fragments for Efficiency #

To make your BottomNavigation smoother and avoid recreating Fragments every time you switch, store Fragment instances in a map. This keeps your code clean and maintains the back stack behavior we want:

private HashMap<Integer, Fragment> fragmentMap = new HashMap<>();

@Override
protected void onCreate(Bundle savedInstanceState) {
    super.onCreate(savedInstanceState);
    setContentView(R.layout.activity_main);

    // Initialize your Fragments once
    fragmentMap.put(R.id.nav_home, new HomeFragment());
    fragmentMap.put(R.id.nav_profile, new ProfileFragment());
    fragmentMap.put(R.id.nav_settings, new SettingsFragment());

    // Set the initial Fragment
    switchFragment(fragmentMap.get(R.id.nav_home));

    // Set up BottomNavigation listener
    BottomNavigationView navView = findViewById(R.id.nav_view);
    navView.setOnItemSelectedListener(item -> {
        switchFragment(fragmentMap.get(item.getItemId()));
        return true;
    });
}

private void switchFragment(Fragment targetFragment) {
    FragmentTransaction transaction = getSupportFragmentManager().beginTransaction();
    transaction.replace(R.id.fragment_container, targetFragment);
    transaction.commit();
}

This way, you’re reusing existing Fragment instances instead of creating new ones, and since we’re not adding anything to the back stack, the back button will always exit the app.

That should resolve your issue entirely! Pressing the system back button will now exit your app instead of navigating through previous Fragments.

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