返回键点击后回退2个Activity而非1个的问题求助

Hey there, let's figure out why your back button is jumping two steps instead of one! When you press back, your stack goes from 3 activities (let's say A → B → C) straight to just A—skipping B entirely. Here are the most likely causes to check, even without seeing your onBackPressed() code:

Common Causes & Fixes #

1. Accidental double calls in your onBackPressed() override #

This is the most frequent culprit. If your code looks something like this, it'll trigger two back actions at once:

@Override
public void onBackPressed() {
    super.onBackPressed(); // Finishes current activity (C)
    super.onBackPressed(); // Accidentally finishes the previous one (B) too!
}

Fix: Remove the duplicate super.onBackPressed() call, or make sure you only call it once after any custom logic.

2. Using activity finish methods that close multiple screens #

If your onBackPressed() uses methods like finishAffinity() or finishAndRemoveTask(), these can wipe out more than just the current activity:

• finishAffinity() closes all activities in the same task stack that share the same affinity as the current one.
• finishAndRemoveTask() removes the entire task from the system.
  Fix: Replace these with a single super.onBackPressed() or finish() if you only want to close the current activity.

3. Wrong intent flags when launching the current activity #

If you launched activity C from B with flags like Intent.FLAG_ACTIVITY_CLEAR_TOP or Intent.FLAG_ACTIVITY_REORDER_TO_FRONT, this can alter the stack in unexpected ways. For example, misusing FLAG_ACTIVITY_CLEAR_TOP might accidentally clear B when launching C, even though it seemed like the stack had 3 activities.
Fix: Check the Intent used to start C and remove any unnecessary flags that modify stack behavior.

4. Incorrect launch mode for the middle activity (B) #

If activity B has a launch mode like singleTask set in AndroidManifest.xml, it can cause odd stack behavior when navigating back. While singleTask typically affects launch behavior, it's worth ruling out if the stack is being modified behind the scenes.
Fix: Verify android:launchMode for all three activities; the default (standard) is usually safe unless you have a specific reason to change it.

Debugging Steps #

If none of the above fix it, use these tools to dig deeper:

• Run adb shell dumpsys activity activities in your terminal before and after pressing back. This will show you the exact state of the task stack, so you can see which activity is being removed unexpectedly.
• Add log statements to onBackPressed() and onDestroy() in all three activities. This will let you track which activities are being finished when you press back.

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