

If you don’t have those environment variables set, you can browse to the SDK and JDK folders in the settings window under the Android section. If these tools aren’t present then RenderDoc searches through PATH and other variables like ANDROID_HOME or ANDROID_SDK_ROOT to find the SDK. On Windows, these tools are shipped with the distributions and all that’s required is java - either in your PATH or via the JAVA_HOME environment variable. RenderDoc does its best to locate or provide necessary Android tools from the Android SDK. Either close it or disable adb integration in “Tools → Android → Enable ADB integration”.

If you have Android Studio open, it will interfere with RenderDoc’s debugging by attaching to the package itself. See here for instructions on how to configure that. Then, refresh the chrome://inspect page.RenderDoc assumes your device is already configured for debugging. On your device, open the app with the WebView you want to debug.Verify that WebView debugging is enabled for your app.# TroubleshootingĬan't see your WebViews on the chrome://inspect page? If your WebViews have titles set, the titles are listed as well. The gray graphics listed with the WebView represent its size and position relative to the device's screen. Use DevTools as you would for a remote browser tab. To start debugging, click inspect below the WebView you want to debug. The chrome://inspect page displays a list of debug-enabled WebViews on your device. To enable WebView debugging, call the static method setWebContentsDebuggingEnabled on the WebView class. WebView debugging must be enabled from within your application. Debugging WebViews is the same as debugging a web page through remote debugging.Access list of debug-enabled WebViews via chrome://inspect.Enable WebView debugging in your native Android app debug WebViews in Chrome DevTools.On Android 4.4 (KitKat) or later, use DevTools to debug WebView content in native Android applications. Debug WebViews in your native Android apps using Chrome Developer Tools.
