Remote Debugging Android WebViews

[ma...@bootstraponline.com]

The device discovery logic for debugging Android KitKat webviews is not documented. Running cat /proc/net/unix will list webviews in this format: @webview_devtools_remote_159  The last number is a PID which can be used to look up the apk package:

`adb shell ps`.split("\r\n").reject { |l| ! l.include?(pid) }

I don't know how to identify the websocket address that's in use to send the appropriate debugging protocol messages. "chrome://inspect/#devices" works without issue so I'm not sure why device discovery isn't clearly explained somewhere. Any help with this is appreciated.

https://developers.google.com/chrome-developer-tools/docs/debugger-protocol
https://developers.google.com/chrome-developer-tools/docs/remote-debugging

https://github.com/mirrors/chromium/blob/master/chrome/browser/devtools/devtools_adb_bridge_browsertest.cc

https://gist.github.com/bootstraponline/8412352