IssueTracker

Component used: Fragment

Version used: 1.4.0-alpha01

The getFragment() method on FragmentContainerView is currently defined as:

fun <F : Fragment!> getFragment(): F?

Where the nullability of the returned fragment is not based on whether the generic passed to it is nullable or not.

It is expected that passing a non-null generic would result in a non-null fragment:

val mainFragment = binding.fragmentContainer.getFragment<MainFragment>()
// This currently fails since it thinks mainFragment is a MainFragment?
mainFragment.callMethod()

And similarly, passing in a nullable generic would result in a nullable fragment:

val optionalFragment = binding.fragmentContainer.getFragment<OptionalFragment?>()
// This should be correctly inferred as nullable
optionalFragment?.callMethod()

I suspect that this might require that this method be written in Kotlin to actually respect the nullability in generics.