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.
il...@google.com
Could you please describe how/where you changed your system to a manual setting?
Description
Component used: Fragment Version used: 1.4.0-alpha01
Developers can decide what type of penalties they would like Fragment StrictMode to output, from
penaltyLog()topenaltyDeath(). However, if developers have specifically enabled debug logging viaFragmentManager.enableDebugLogging(true)or via theadb shell setprop log.tag.FragmentManager VERBOSE(orDEBUG), we should always output every violation to logcat with theFragmentManager.TAGasLog.d(), no matter what policy is used.This is ensure that debug logging will inform those debugging Fragments of potential issues that may affect the behavior of Fragments.
The internal helper of
FragmentManager.isLoggingEnabled(Log.DEBUG)can be used to determine whether we should output these debug log violations. This output should happen before any FragmentStrictMode policy specific logging/listeners/death. IfpenaltyLog()is used and you're debug logging, both log messages should appear (they should be independent from one another).