launchFragmentInHiltContainer does not appear to work with the 1.2.0-beta02 of androidx.activity/androidx.fragment: "Cannot access 'EmptyFragmentActivity': it is internal in 'FragmentScenario'"

After updating androidx.activity:activity-ktx and androidx.fragment:fragment-ktx to 1.2.0-beta02 from 1.2.0-beta01, the launchFragmentInHiltContainer code example found here and recommended here does not appear to work.

Cannot access 'EmptyFragmentActivity': it is internal in 'FragmentScenario' e: /home/runner/work/libraries/test-config/src/debug/java/com/xxx/test_config/HiltExtensions.kt: (25, 42): Public-API inline function cannot access non-public-API 'public const final val THEME_EXTRAS_BUNDLE_KEY: String defined in androidx.fragment.app.testing.FragmentScenario.EmptyFragmentActivity.Companion' Task :libraries:test-config:compileDevDebugKotlin FAILED

[manuelvicnt]

I can replicate using fragment-ktx 1.3.0-beta2. As suspected, it’s because EmptyFragmentActivity is now internal.

If you don’t need to pass in your own theme, then remove themeResId from the parameters of the function and the .putExtra lines of the startActivityIntent.

If you need it, then use the fully qualified key that you can find in the implementation of EmptyFragmentActivity. i.e.

val startActivityIntent = Intent.makeMainActivity(
    ComponentName(
        ApplicationProvider.getApplicationContext(),
        HiltTestActivity::class.java
    )
).putExtra(
    "androidx.fragment.app.testing.FragmentScenario.EmptyFragmentActivity.THEME_EXTRAS_BUNDLE_KEY",
    themeResId
)

That’s a nasty workaround but that’s all we can do for now

[manuelvicnt]

The architecture-samples project use the stable version of androidx.fragment:fragment-ktx:1.2.0. As you’re using a lower version, I’d suggest modifying the launchFragmentInHiltContainer yourself. Remove the themeResId param (line 40) and the putExtra method that sets it (line 48).

Thanks!