Fixed
Status Update
No update yet.
Comments
il...@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.
il...@google.com
ap...@google.com
Could you please describe how/where you changed your system to a manual setting?
il...@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.1.0-alpha09
Devices/Android versions reproduced on:
When using nested fragments such as:
Parent
-- Child
I'd expect the Lifecycle changes of these fragments to be properly nested:
Parent CREATED
Child CREATED
Parent STARTED
Child STARTED
Parent RESUMED
Child RESUMED
---
Child PAUSED
Parent PAUSED
Child STOPPED
Parent STOPPED
Child DESTROYED
Parent DESTROYED
But I'm not seeing that - it seems like the opposite is the case - the child gets changed first on the way up and after on the way down, perfectly *not* nesting.