Fixed
Status Update
Comments
il...@google.com <il...@google.com>
ap...@google.com <ap...@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.
ta...@gmail.com <ta...@gmail.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-alpha05
FragmentFactory has the method
public Fragment instantiate(@NonNull ClassLoader classLoader, @NonNull String className, @Nullable Bundle args)
but that method doesn't call setArguments(). While the Javadoc specifically calls this out, it is still confusing. The stated use case of constructing a different Fragment based on the arguments doesn't make much sense since developers can all setArguments() at any point after the fact (so needing a separate class for different arguments breaks down).