DEV Community


Posted on • Originally published at Medium on

Debug Expo/React Native WebView

The “core” logic of my React Native app involves using WebViews because I need to access the HTML5 canvas. Whilst developing this code there are bound to be errors and issues with the WebView code. Figuring out how to debug code within the WebView isn’t so obvious.

Figure 1: Chrome Inspect for the WebView

Option 1: Chrome Inspect

  • Start your Expo/React Native app*
  • Open and chrome and then go to the following URL, chrome://inspect
  • Then click on the “inspect” button, click the top link to open the latest WebView, you should see something similar to Figure 2
  • You should see something similar to Figure 1. Now you explore the WebView like a normal web page

Figure 2: List of WebViews

Option 2: React Native Debugger

Alternatively you can access this page using the React Native Debugger page in chrome.

  • Start your Expo/React Native app*
  • Go to your React Native debugger on chrome, in my case since I’m using Expo my URL is
  • Go to the three dots button (next to close button) > More tools > Remote devices
  • At the bottom you’ll see another panel open up
  • You should be able to see your Android device in the list
  • Hit the Inspect button the first item (this will be the latest)
  • Now you explore the WebView like a normal web page


So to the closest way to debug the WebView I have found is to use console.log statements that will appear in the DevTools console. In the normal React Native debugger console you won’t be able to see any console.log statements from the WebView. You can only view them by exploring DevTools for Remote devices. As far as I can tell you cannot use breakpoints in WebViews but still this is better than nothing.

Figure 3: Open DevTools for Remote devices


*Make sure to do this on the same machine/host that is running the emulator. For example, a Genymotion VM is running on my Windows machine but I can still see it’s WebViews on the chrome inspect URL. This can be seen in Figure 3.

Figure 4: Genymotion VM and Chrome on a Windows host machine.


Top comments (0)