Android Navigation Component：进入StartupFragment后多次按返回键才关闭应用的问题求助

Hey there! Let's break down why you're stuck pressing the back button 7 times to close the app and fix this for good.

What's Causing the Issue? #

1. Unmanaged Back-Press Callback堆积
   In your BoardingFragment and StartupFragment, you're adding back-press callbacks to the activity's dispatcher without tying them to the fragment's lifecycle. This means even after those fragments are popped from the nav stack and destroyed, their callbacks stick around. Every time you navigate to a new fragment, you add another callback—so pressing back triggers all of them one by one, hence the 7 presses.

2. Ambiguous Nav Stack Cleanup
   While your popUpTo settings should clear the stack, targeting the entire navigation graph (@id/splash_nav_graph) is less precise than targeting the current fragment. This can lead to unexpected stack behavior, even if it looks correct on the surface.

Fixes to Implement #

1. Bind Back-Press Callbacks to Fragment Lifecycle

Update the back-press code in both BoardingFragment and StartupFragment to include viewLifecycleOwner. This ensures callbacks get automatically removed when the fragment is destroyed, preventing accumulation:

// In BoardingFragment
activity?.onBackPressedDispatcher?.addCallback(viewLifecycleOwner) {
    if (binding.uspPager.currentItem != 0) {
        binding.uspPager.currentItem--
    } else {
        // Directly finish the activity for immediate app closure
        activity?.finish()
    }
}

// In StartupFragment
activity?.onBackPressedDispatcher?.addCallback(viewLifecycleOwner) {
    if (binding.uspPager.currentItem != 0) {
        binding.uspPager.currentItem--
    } else {
        activity?.finish()
    }
}

Using activity?.finish() instead of onBackPressed() removes reliance on nav stack behavior and directly achieves your goal of closing the app when the Pager is at index 0.

2. Refine Nav Stack Cleanup

Make your popUpTo settings more precise by targeting the current fragment instead of the entire navigation graph. This ensures the stack only ever holds the active fragment:

<!-- Splash → Language action -->
<action
    android:id="@+id/splash_to_lang_action"
    app:destination="@id/language_fragment"
    app:popUpTo="@id/splash_fragment"
    app:popUpToInclusive="true"/>

<!-- Language → Boarding action -->
<action
    android:id="@+id/lang_to_boarding_action"
    app:destination="@id/boarding_fragment"
    app:popUpTo="@id/language_fragment"
    app:popUpToInclusive="true"/>

<!-- Boarding → Startup action -->
<action
    android:id="@+id/boarding_to_startup_action"
    app:destination="@id/startup_fragment"
    app:popUpTo="@id/boarding_fragment"
    app:popUpToInclusive="true"/>

What to Expect After Fixes #

• Your nav stack will only contain the active fragment at every step
• Pressing back on a non-0 Pager index will decrement the page as expected
• Pressing back when the Pager is at index 0 will close the app in one tap

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