You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 1, 2023. It is now read-only.
I did a dirty hack to get logging functionality (i used Timber by Jake Wharton).
It appears that extending Console was a problem. I can only assume that the classname is being used to hookup the class and methods to chrome's handles. I recommend perhaps using a class annotation to allow for multiple handlers for each of chromes handles.
Here is a little hack example in case anyone else runs into this: StethoTree
There is a pretty straight forward way to make this work using ChromePeerManager and hacking Stetho itself just a little bit (patches welcome grin). Specifically, something like:
We wanted to encapsulate this for you, allowing for CLog itself to guess ConsolePeerManager.getInstnace() by default as well so that callers could just invoke:
Is there an example or some functionality to do with redirecting logging to the chrome console instead of to logcat or wherever?
If not, lets get something like this implemented?
The text was updated successfully, but these errors were encountered: