[Bug 323] New: slf4j not logging VERBOSE and DEBUG messages, no matter what is Logcat's loglevel
http://bugzilla.slf4j.org/show_bug.cgi?id=323 Priority: P5 Bug ID: 323 Assignee: slf4j-dev@qos.ch Summary: slf4j not logging VERBOSE and DEBUG messages, no matter what is Logcat's loglevel Severity: normal Classification: Unclassified OS: All Reporter: zalavaari@gmail.com Hardware: Other Status: NEW Version: 1.7.x Component: slf4j-android Product: SLF4J It seems on android platform the isLoggable() method is always returns false for VERBOSE and DEBUG (no matter what is the actal loglevel is), so it should not be called before calling Log.d and Log.v The only slf4j version I know of where the DEBUG & VERBOSE logs are working is 1.6.1-RC1 -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.slf4j.org/show_bug.cgi?id=323 Martin Vysny <vysny@baka.sk> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |vysny@baka.sk --- Comment #1 from Martin Vysny <vysny@baka.sk> --- The problem is that slf4j honors Android's Log.isLoggable() function, which seems correct, but unfortunately in Android it's not. The Log.isLoggable() by defaults returns false for debug logging. DEBUG can be configured only by gaining developer access to the phone. So, the application itself nor the user cannot enable debug level easily. This behavior is IMHO broken horribly and developers are simply not using that call: http://stackoverflow.com/questions/19984838/how-to-get-slf4j-android-to-hono... I myself have found a workaround by using the slf4j-android 1.6.1-RC1. So, I would vote for not calling Log.isLoggable() at least for Logger.debug(); I would however recommend to not Log.isLoggable() entirely. Thanks! -- You are receiving this mail because: You are the assignee for the bug.
participants (1)
-
bugzilla-daemon＠qos.ch