Block Remote Debugging

[tgrau...@ouya.tv]

Hello Chromium-Tools-Dev,

Remote-Debugging is an excellent feature during development of apps based on the Chromium source (trunk) for Android.
https://developers.google.com/chrome-developer-tools/docs/remote-debugging

However, if you make an app based on the chromium source, how do you go about disabling/blocking remote debugging?

I'm using the content-shell and my attempt at "WebView.setWebContentsDebuggingEnabled(false);" didn't work because I'm not dealing with a webview.

What is the best way to prevent the ADB extension from connecting to your application?

I didn't see a flag in src/content/renderers/web_preferences.cc for debugging/remote settings.

I appreciate your feedback.

Thanks,

Tim Graupmann

[Pavel Feldman]

Do you use WebView or are you using chromium source code to build your own app? If latter, modify your source code to not start the remote debugging server.

Pavel

--
You received this message because you are subscribed to the Google Groups "Google Chrome Developer Tools" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-chrome-develo...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-chrome-developer-tools/750a5003-506c-452d-ba59-9d48ae2a82f8%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Tim Graupmann]

Hi Pavel,

Thanks for the response.

I used the content-shell because the OUYA lacks the Google services to support the chrome-shell.

I ended up solving the issue by blocking the debugger and remote-debugger per the app requirement.

http://code.google.com/p/chromium/issues/detail?id=349558

I used the Chromium source to build a custom app and it works great. Of course I modified things like auto playing media which by default is suspended on mobile.

Thanks again,

Tim Graupmann | OUYA Android Developer | skype: tgraupmann_prey | phone: 425-422-8221

Need technical help? Sign-up for developer office hours and hangout with us!

--
You received this message because you are subscribed to a topic in the Google Groups "Google Chrome Developer Tools" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/google-chrome-developer-tools/Hca3Yj6uTew/unsubscribe.
To unsubscribe from this group and all its topics, send an email to google-chrome-develo...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-chrome-developer-tools/CAEX3KhbGtKSKb_p81Ejk4XW%3DWFjZ%3D7VWVVr3-SU0OjNE9W1sTg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Pavel Feldman]

I closed issue 349558 as WontFix because the app (embedder) needs to use content/ API for setting up the browser instance (much like content shell does). And that allows embedder to either content::DevToolsHttpHandler::Start the remote debugging or not do so.

Regards

Pavel

To view this discussion on the web visit https://groups.google.com/d/msgid/google-chrome-developer-tools/CAC36%3D%2BWp7OCBh3qRxL9Raqae-n2Tjm%2B%3Dnt%3DDXnTC9VPDd__p1g%40mail.gmail.com.