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.
ap...@google.com
Could you please describe how/where you changed your system to a manual setting?
jb...@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
There are no use cases when we should allow a fragment's Lifecycle to be moved to
DESTROYEDother than when the fragment is actually destroyed.Therefore, you should not be able to
setMaxLifecycle()toDESTROYEDthrough aFragmentTransaction, initialize aFragmentScenariowithDESTROYED, or move aFragmentScenarioto theDESTROYEDstate usingmoveToState().Doing any of these things should throw an error.