Using FragmentContainerView with Navigation component?

Question

After updating to Navigation 2.2.0-beta01 from the previous version, lint gives a warning about replacing the tag with FragmentContainerView<

Answer 1

The NavigationBasicSample has been updated to 2.2.0-alpha01 but is still using the fragment tag. The NavigationAdvancedSample shows the use of the FragmentContainerView, but the nav graph is inflated in the code (they have several different graphs) and the corresponding host fragment is added to the FragmentContainerView. So I'd say at this time we should ignore the warning if we want automatic inflation.

Answer 2

There is still a bug that will thrown an exception if you simply replace fragment for <androidx.fragment.app.FragmentContainerView>. The fix, as of now, as stated by many google enginners in this bug thread is to change your code in your activity:

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

Answer 3

Important! There are known issues with different versions of FragmentContainerView. See the changelog before using. Read through bug fixes and use a recent version of the library.

---

For now, you should also declare dependency on Fragment 1.2.0-beta02 as it includes a fix for this use case.

implementation "androidx.fragment:fragment:1.2.0-beta02"

Version 1.2.0-beta02

October 11, 2019

Bug fixes

Fixed an issue where Fragment's onInflate() did not receive proper attributes from FragmentContainerView, breaking cases such as NavHostFragment. (b/142421837)

Source: https://developer.android.com/jetpack/androidx/releases/fragment#1.2.0-beta02