You can always find the available WebViews by visiting chrome://inspect/#devices in Google Chrome. No WebViews foundĮnsure that the device is connected and that the Android application is a debug build or WebView debugging is enabled. You can also specify it manually using the android-webview-debug.adbPath configuration parameter. Usually it should be on the PATH environment variable. Troubleshooting Failed to locate ADB executable.
This extension contributes the following settings:
connectTimeout: The time the extension will wait for the webview to be ready in milliseconds.application: The package name of the application to connect to.device: The serial of the device to use.If multiple possible instances are found the extension will ask you to choose one. It is possible to specify the device and/or the application to attach to. You can optionally specify a port to use for the debugging connection or let the extension automatically choose an unsued one. In case you want to use the old Debugger for Chrome extension you can set to false.Īll configuration options of the pwa-chrome: attach configuration of the vscode-js-debug extension are supported.
vscode/launch.json file in the root directory of your project. Right now the extension only supports attaching to an already running Google Chrome or WebView instance. Pick a launch config from the dropdown on the Debug pane in Code. When your launch config is set up, you can debug your project. This extension uses the vscode-js-debug extension under the hood. Debug your JavaScript code running in WebViews on any Android device from VS Code.Ī VS Code extension to debug your JavaScript code in the Google Chrome browser or other WebView targets on Android devices, that support the Chrome DevTools Protocol.
0 kommentar(er)
