Fixed
Status Update
No update yet.
Comments
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?
an...@google.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
Version used: 1.2.0-rc01
Devices/Android versions reproduced on: all
If your Fragment was added with animations or transitions and you go to remove it via code such as
fragmentManager.commitNow {
remove(fragment)
}
Previously, you could guarantee that fragmentManager.findFragmentById() / findFragmentByTag() would return null.
However, it seems like the Fragment 1.2 changes where onDestroyView() (and hence, onDestroy() / onDetach()) are not called until the animation/transition completes means this is no longer the case.
FragmentManager's state should always be up to date after commitNow(), even if the Fragment itself has not concluded its drive to onDetach().