Fixed
Status Update
Comments
il...@google.com <il...@google.com> #2
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 <ap...@google.com> #3
Could you please describe how/where you changed your system to a manual setting?
il...@google.com <il...@google.com> #4
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
Not sure why you're doing this, but there's a back pressed listener being added to the dispatcher in the initializeChildFragmentManager method, which itself is only called in performOnCreateView. Why isn't the child fragment manager just instantiated when the fragment is first initialized? There are so many bugs around this. Anyway, this means any back pressed listener added in the Fragment's onCreate is essentially pointless since it will always be overridden by the fragment manager's one which pops the back stack. However, back pressed listeners added in onViewCreated work since they're after the FM's listener.