Fixed
Status Update
No update yet.
Comments
il...@google.com
ap...@google.com
Seems to be a DNS problem with systems that have 'obtain DNS server address automatically'. Changed my system to a manual setting and the browser etc now work. SDK 2.2 didn't seem to mind the auto setting though.
jb...@google.com
Could you please describe how/where you changed your system to a manual setting?
pa...@gmail.com
Based on its date, this issue was originally reported before Android 2.3. Because of the many changes that existed in Android 4.x compared to previous versions, it's very likely that this issue doesn't exist in recent versions of Android like 4.2.2 or newer. Because of the high likelihood that this issue is obsolete, it is getting closed automatically by a script, without a human looking at it in detail. If the issue still exists on a Nexus 4 or Nexus 7 running Android 4.2.2 and is not related to Google applications, please open a new report accordingly.
Description
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:
I attached a screen recording of the issue captured on a Samsung Galaxy Tab s7, and a sample project.