Nested navigation graphs in Android Kotlin - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ navigation

intermediate

Identify the start destination in nested navigation graphs

Given the nested navigation graph below, which fragment will be shown first when the app starts?

Android Kotlin

val navGraph = navController.navInflater.inflate(R.navigation.main_nav_graph).apply {
  startDestination = R.id.home_nav_graph
}

val homeNavGraph = navController.navInflater.inflate(R.navigation.home_nav_graph).apply {
  startDestination = R.id.dashboardFragment
}

val settingsNavGraph = navController.navInflater.inflate(R.navigation.settings_nav_graph).apply {
  startDestination = R.id.settingsFragment
}

A main_nav_graph

B settingsFragment

C home_nav_graph

D dashboardFragment

💡 Hint

The start destination of the main graph points to a nested graph, which itself has a start destination fragment.

The main navigation graph's start destination is the home_nav_graph nested graph. Inside home_nav_graph, the start destination is dashboardFragment, so that fragment is shown first.

❓ ui_behavior

intermediate

Effect of nested graph on back button behavior

In an app with nested navigation graphs, what happens when the user presses the back button on a fragment inside a nested graph?

A The app navigates back within the nested graph until its start destination, then back to the parent graph.

B The back button is disabled inside nested graphs.

C The app skips the nested graph and goes directly to the main graph's start destination.

D The app immediately exits regardless of navigation stack.

💡 Hint

Think about how navigation stacks work with nested graphs.

The back button navigates back through the nested graph's stack first. Once at the nested graph's start destination, pressing back moves to the parent graph's previous destination or exits if none.

❓ lifecycle

advanced

Lifecycle impact of nested navigation graphs on fragments

When navigating from a fragment in one nested graph to a fragment in another nested graph, what happens to the lifecycle of the first fragment?

A The first fragment's onPause and onStop are called, but it remains in memory until popped from back stack.

B The first fragment is immediately destroyed and removed from memory.

C The first fragment remains fully active and visible behind the new fragment.

D The first fragment's lifecycle methods are not called until the app is closed.

💡 Hint

Consider how fragment lifecycle works with navigation and back stack.

Navigating away triggers onPause and onStop for the first fragment, but it stays in memory on the back stack until popped or replaced.

📝 Syntax

advanced

Correct Kotlin code to navigate between nested graphs

Which Kotlin code snippet correctly navigates from a fragment in one nested graph to a fragment in another nested graph using Navigation Component?

Android Kotlin

navController.navigate(R.id.action_currentGraphFragment_to_targetGraphFragment)

A navController.navigate("targetGraphFragment")

B navController.navigate(R.id.action_currentGraphFragment_to_targetGraphFragment)

C navController.navigate(R.id.targetGraphFragment)

D navController.navigate(R.navigation.targetGraphFragment)

💡 Hint

Use the generated action ID for navigation between fragments.

Navigation between fragments in nested graphs requires using the action ID defined in the navigation XML, not just the destination ID or string.

🔧 Debug

expert

Diagnose navigation crash due to nested graph misconfiguration

An app crashes with IllegalArgumentException: Navigation destination R.id.profileFragment is unknown to this NavController. The profileFragment is inside a nested graph. What is the most likely cause?

A The profileFragment ID is duplicated in multiple graphs causing conflict.

B The NavController was not initialized before navigation call.

C The nested graph containing profileFragment is not included or linked in the main navigation graph.

D The profileFragment class is missing from the project source code.

💡 Hint

Check if all nested graphs are properly referenced in the main graph.

If a nested graph is not included in the main graph, its destinations are unknown to the NavController, causing this crash.

Practice

1.

What is the main purpose of using nested navigation graphs in Android apps?

easy

A. To group related screens for better organization and easier navigation

B. To increase app size by duplicating navigation code

C. To disable navigation between screens

D. To replace fragments with activities

Solution

1. Step 1: Understand navigation graph purpose

   Navigation graphs define how screens connect and transition in an app.

2. Step 2: Role of nested graphs

   Nested graphs group related screens to keep navigation organized and maintainable.

3. Final Answer:

   To group related screens for better organization and easier navigation -> Option A

4. Quick Check:

   Nested graphs = group related screens [OK]

Hint: Nested graphs organize related screens inside main graph [OK]

Common Mistakes:

• Thinking nested graphs duplicate code
• Believing nested graphs disable navigation
• Confusing nested graphs with replacing fragments

2.

Which XML tag is used to include a nested navigation graph inside a main navigation graph?

easy

A. <graph>

B. <navigation>

C. <fragment>

D. <include>

Solution

1. Step 1: Identify tag for including nested graphs

   The <include> tag is used to insert one XML layout or graph inside another.

2. Step 2: Confirm usage in navigation graphs

   To add a nested navigation graph inside the main graph, <include> is the correct tag.

3. Final Answer:

   <include> -> Option D

4. Quick Check:

   Include tag adds nested graph [OK]

Hint: Use <include> tag to add nested graphs in XML [OK]

Common Mistakes:

• Using <graph> instead of <include>
• Confusing <fragment> with <include>
• Mistaking <navigation> as include tag

3.

Given this main navigation graph XML snippet:

<navigation xmlns:android=\"http://schemas.android.com/apk/res/android\"
    android:id=\"@+id/main_graph\"
    app:startDestination=\"@id/homeFragment\">
    <include app:graph=\"@navigation/profile_graph\" />
    <fragment android:id=\"@+id/homeFragment\" android:name=\"com.example.HomeFragment\" />
</navigation>

What happens when the app starts?

medium

A. The app starts at HomeFragment as the start destination

B. The app starts at the first fragment inside profile_graph

C. The app crashes due to missing start destination in profile_graph

D. The app shows a blank screen

Solution

1. Step 1: Check startDestination in main graph

   The main graph's startDestination is set to homeFragment explicitly.

2. Step 2: Effect of including profile_graph

   Including profile_graph adds its screens but does not change main graph's startDestination.

3. Final Answer:

   The app starts at HomeFragment as the start destination -> Option A

4. Quick Check:

   Start destination in main graph controls start [OK]

Hint: Start destination in main graph controls app start [OK]

Common Mistakes:

• Assuming nested graph startDestination overrides main
• Thinking app crashes without startDestination in nested graph
• Believing included graphs start automatically

4.

What is wrong with this nested navigation graph XML snippet?

<navigation xmlns:android=\"http://schemas.android.com/apk/res/android\"
    android:id=\"@+id/profile_graph\">
    <fragment android:id=\"@+id/profileFragment\" android:name=\"com.example.ProfileFragment\" />
</navigation>

When included in main graph, navigation to profileFragment fails. Why?

medium

A. Fragment ID is invalid with plus sign

B. Missing startDestination attribute in profile_graph

C. Fragment name is incorrect format

D. Navigation tag is missing namespace

Solution

1. Step 1: Check required attributes in navigation graph

   Every navigation graph must have a startDestination attribute to define entry point.

2. Step 2: Identify missing startDestination

   The profile_graph lacks startDestination, so navigation fails when included.

3. Final Answer:

   Missing <code>startDestination</code> attribute in profile_graph -> Option B

4. Quick Check:

   startDestination required in nested graphs [OK]

Hint: Always set startDestination in nested graphs [OK]

Common Mistakes:

• Thinking plus sign in ID causes error
• Assuming fragment name format is wrong
• Ignoring missing startDestination attribute

5.

You want to create a nested navigation graph for a settings section with two fragments: SettingsListFragment and SettingsDetailFragment. Which is the correct way to define the nested graph XML?

<navigation xmlns:android=\"http://schemas.android.com/apk/res/android\"
    android:id=\"@+id/settings_graph\"
    app:startDestination=\"@id/settingsListFragment\">
    <fragment android:id=\"@+id/settingsListFragment\" android:name=\"com.example.SettingsListFragment\" />
    <fragment android:id=\"@+id/settingsDetailFragment\" android:name=\"com.example.SettingsDetailFragment\" />
</navigation>

How should you include this nested graph inside the main navigation graph?

hard

A. Copy all fragments from settings_graph directly into main graph

B. Add <fragment android:id=\"@+id/settings_graph\" /> inside main graph

C. Use <include app:graph=\"@navigation/settings_graph\" /> inside main graph

D. Use <navigation app:graph=\"@navigation/settings_graph\" /> inside main graph

Solution

1. Step 1: Define nested graph with startDestination and fragments

   The settings_graph XML correctly defines startDestination and fragments.

2. Step 2: Include nested graph in main graph

   Use <include app:graph=\"@navigation/settings_graph\" /> to add nested graph inside main graph.

3. Final Answer:

   Use <include app:graph=\"@navigation/settings_graph\" /> inside main graph -> Option C

4. Quick Check:

   Include tag adds nested graph correctly [OK]

Hint: Include nested graph with [OK]

Common Mistakes:

• Using fragment tag instead of include
• Copying fragments instead of nesting
• Using navigation tag incorrectly inside main graph