Android NavController shows last fragment before a different fragment requested from another activity is shown

Question

SettingsLandingActivity holds multiple fragments and handles the transition in between them using NavController. When user enters the activity, it shows SettingsLandingFragment, as it is the default fragment.

Then user clicks on GeneralSettings shortcut, so it triggers an intent for GeneralSettingsFragment, it again uses the following code to switch to GeneralSettingsFragment. So, GeneralSettingsFragment is resumed and SettingLandingFragment gets onViewDestroyed.

Then user directly switches to another activity, GeneralSettingsFragment gets onPause. Then user clicks on Settings button, then the sequence of events is-

GeneralSettingsFragment gets onStart.

SettingsLandingActivity gets onNewIntent

SettingLandingFragment gets onViewCreate, onStart and OnResume

As GeneralSettingsFragment gets onStart, that fragment appears for a short moment as a flicker, then SettingsLandingFragment is shown. The expectation is to show SettingLandingFragment without any showing previous screen. It is also a requirement to always switch to SettingsLandingFragment when Settings button is clicked.

The following method is called from onNewIntent of activity to handle navigations and the parameter clearBackStack is passed as TRUE. How to avoid the flicker of previous fragment when a different fragment is requested from different activity? Kindly help me to solve this issue.

    private void navigateToFragments(int actionNavigate,
                                 boolean clearBackStack,
                                 Bundle bundle) {
    
    NavHostFragment navHostFragment = (NavHostFragment) getSupportFragmentManager()
            .findFragmentById(R.id.nav_host_fragment);
    if (navHostFragment != null) {
        navController = navHostFragment.getNavController();
        NavOptions navOptions;
        if (clearBackStack) {
            navOptions = new NavOptions.Builder()
                    .setPopUpTo(navController.getGraph().getId(), true).build();
            Logger.d(TAG, "Pop and clearing the all back stack");
        } else {
            navOptions = new NavOptions.Builder()
                    .setPopUpTo(actionNavigate, true).build();
            Logger.d(TAG, "Pop and clearing the all " +
                    "intervening destinations up to current navigate destination.");
        }
        Logger.d(TAG, " Navigate to a destination from the current navigation graph");
        navController.navigate(actionNavigate, bundle, navOptions);
    } else {
        Logger.e(TAG, "NavHostFragment is null");
    }
}

Delek · Accepted Answer · 2025-07-12 06:47:42Z

0

You've tried navigating through the stack of elements. When the navigation graph is created, each fragment has a specific element item.

Kotlin example

val nv: NavigationView = (context as SidebarActivity).findViewById(R.id.nav_view)
val item = nv.menu.getItem(3) //Item of fragment target
val navController = (context as SidebarActivity).findNavController(R.id.nav_host)
onNavDestinationSelected(item, navController)

answered Jul 12 at 6:47

Delek

531 silver badge8 bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

Dev_Cob Jul 15 at 13:25

is it possible to set the navgraph start destination programmatically from activity class, so that the one we set in activity class is created, not the one set in nav graph layout.

Collectives™ on Stack Overflow

Android NavController shows last fragment before a different fragment requested from another activity is shown

1 Answer 1

1 Comment

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

1 Comment

Your Answer

Sign up or log in

Post as a guest

Related