Component used: Fragment

Version used: 1.3.0

Devices/Android versions reproduced on: Android Studio Emulator with Android 11

I found a bug that requires the use of the Fragment library from 1.3.0 and up (I still reproduce the bug in the version 1.4.0-alpha06), custom animations in FragmentTransactions and a RecyclerView (of androidx.recyclerview:recyclerview:1.2.1).

If a fragment over which the soft keyboard is shown (because an EditText is focused for example), is replaced with a new fragment that shows a RecyclerView, and custom animations are set in the FragmentTransaction, then the soft keyboard is not automatically dismissed and is displayed over the second fragment. If the second fragment does not show a RecyclerView, or custom animations are not set in the FragmentTransaction, then the soft keyboard is automatically dismissed.

It is a regression since the soft keyboard was dismissed correctly when using a version of the Fragment library below 1.3.0.

I suspect that the issue comes from the new fragment state manager since I could not reproduce the issue when disabling it with the method:

FragmentManager.enableNewStateManager(false)

I attached a screen recording of the issue captured on a Samsung Galaxy Tab s7, and a sample project.