IssueTracker

Component used: Fragment
Version used: 1.2.0-beta02
Devices/Android versions reproduced on: all

When the NavHostFragment is inflated using FragmentContainerView, if you attempt to use findNavController in the onCreate() of the Activity, the nav controller cannot be found. This is because when the fragment is inflated in the constructor of FragmentContainerView, the fragmentManager is in the INITIALIZING state, and therefore the added fragment only goes up to initializing. For the nav controller to be properly set, the fragment view needs to be created and onViewCreated() needs to be dispatched, which does not happen until the ACTIVITY_CREATED state.

We should either force the fragment to create a view right after being added to the FragmentManager, or find a way to wait for the FragmentManager to reach a higher state before allowing the Navigation onCreate to be called.

The following options can be used as viable work arounds:

1. Retrieve the navController directly from the NavHostFragment.

val navHostFragment = supportFragmentManager.findFragmentById(R.id.my_nav_host_fragment) as NavHostFragment
val navController = navHostFragment.navController

2. Post the call to the findNavController method on a handler and execute all actions that need it after that post is complete.
3. Continue to use the fragment tag (<fragment>) to inflate the NavHostFragment