NavHost and NavController in Android Kotlin - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ ui_behavior

intermediate

What happens when you call navigate() on NavController?

Given a NavController instance, what is the immediate effect of calling navController.navigate(R.id.destinationFragment) in an Android app?

Android Kotlin

navController.navigate(R.id.destinationFragment)

A The app closes the current activity and opens a new one.

B The app reloads the current fragment without changing the UI.

C The app navigates to the fragment with ID destinationFragment and adds it to the back stack.

D The app throws a runtime exception because navigate() requires a Bundle argument.

💡 Hint

Think about what navigation means in a single-activity app using fragments.

Calling navigate() on NavController changes the visible fragment to the specified destination and adds this transaction to the back stack, allowing the user to return.

❓ lifecycle

intermediate

When is NavHostFragment created in the activity lifecycle?

In an Android app using Navigation Component, at which point in the activity lifecycle is the NavHostFragment typically created and attached?

A During the activity's onCreate() when setContentView() inflates the layout containing NavHostFragment.

B Only after onStart() is called on the activity.

C After onResume() when the UI is fully visible.

D NavHostFragment is created before the activity's onCreate() method.

💡 Hint

Think about when views are created from XML layouts.

NavHostFragment is part of the activity's layout and is created when setContentView() inflates the layout during onCreate().

📝 Syntax

advanced

Identify the correct way to obtain NavController in a fragment

Which Kotlin code snippet correctly obtains the NavController inside a fragment?

A val navController = Navigation.findNavController(activity, R.id.nav_host_fragment)

B val navController = findNavController()

C val navController = NavHostFragment.findNavController(this)

D val navController = NavController(this)

💡 Hint

Remember the extension function available in fragments.

In a fragment, the extension function findNavController() is the recommended way to get the NavController instance.

🔧 Debug

advanced

Why does navigation crash with IllegalArgumentException?

You call navController.navigate(R.id.action_to_unknown) but the app crashes with IllegalArgumentException: navigation destination unknown. What is the most likely cause?

Android Kotlin

navController.navigate(R.id.action_to_unknown)

A The destination ID action_to_unknown is not defined in the navigation graph XML.

B The NavController instance is null at the time of navigation.

C The app is missing internet permission in the manifest.

D The fragment is not attached to the activity.

💡 Hint

Check your navigation graph XML for the destination ID.

The error means the navigation graph does not contain a destination with the given ID, so navigation cannot proceed.

🧠 Conceptual

expert

How does NavHostFragment manage back stack differently than FragmentManager?

What is a key difference in how NavHostFragment manages the back stack compared to directly using FragmentManager transactions?

A NavHostFragment requires explicit calls to popBackStack(), FragmentManager does not.

B NavHostFragment does not support back stack at all, unlike FragmentManager.

C FragmentManager automatically handles deep links, but NavHostFragment does not.

D NavHostFragment uses a centralized navigation graph to manage destinations and back stack, while FragmentManager requires manual transaction management.

💡 Hint

Think about the role of the navigation graph in Navigation Component.

NavHostFragment uses the navigation graph to define all possible destinations and manages the back stack automatically, simplifying navigation compared to manual FragmentManager transactions.