[ https://issues.apache.org/jira/browse/CB-5487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13834510#comment-13834510 ]
Andrew Grieve commented on CB-5487: ----------------------------------- Instead of a <preference>, how about just linking it with the "debuggable" AndroidManifest parameter. This is shown in the example code from the linked page. {code} if(Build.VERSION.SDK_INT >= Build.VERSION_CODES.KITKAT) { if ( 0 != ( getApplcationInfo().flags &= ApplicationInfo.FLAG_DEBUGGABLE ) ) { WebView.setWebContentsDebuggingEnabled(true); } } {code} > Add preference to enable Remote Debugging for Android 4.4+ (KitKat) Chrome > based WebView > ---------------------------------------------------------------------------------------- > > Key: CB-5487 > URL: https://issues.apache.org/jira/browse/CB-5487 > Project: Apache Cordova > Issue Type: Bug > Components: Android > Affects Versions: 3.2.0 > Reporter: Michal Mocny > > You have to explicitly enable remote debugging for kitkat chrome-based > webview: > https://developers.google.com/chrome-developer-tools/docs/remote-debugging#debugging-webviews > As far as I am aware there are no performance implication to leaving this > flag on at all time (i.e. when releasing your app) -- however, the feature > was implemented as an opt-in so that users cannot inspect your webview based > application without your (the developer) explicit consent. I think cordova > should respect that decision and leave the preference off by default. > CB-3494 is related. -- This message was sent by Atlassian JIRA (v6.1#6144)