Meta Developers

The preferred way to test and debug your Browser content is to use Meta Quest Developer Hub, which has tools to setup your device, enable desktop casting, and more. Visit the MQDH main page for instructions on how to set up MQDH to connect your device.

USB Debugging on Meta Quest without MQDH

To configure your device for USB debugging:

Open the Meta Horizon mobile app.
Navigate to Menu > Devices and then select your device.
Go to Headset Settings > Developer Mode and then enable Developer Mode.
Use a USB-C cable to connect the headset to your computer, and then put on the headset.
Go to Settings > System > Developer, and then enable Enable custom settings and MTP Notification.
When asked to allow USB debugging, select Always allow from this computer.

After connecting, open up a command shell and type:

adb devices

If the device is connected properly, ADB will show the device id list such as:

List of devices attached
ce0551e7                device

ADB can’t be used if no device is detected. If your device is not listed, the most likely problem is that you do not have the correct USB driver. You can also try another USB cable and/or port.

Use ADB Reverse to View Local Pages on your Quest

Use adb reverse to see local pages from your PC on your device A common web development workflow is to set up a local HTTP server on your desktop pointing on a port of localhost. You can use adb reverse to make that page available on your device while it is connected to your desktop.

To do that, run the following command: adb reverse tcp:8080 tcp:8080

Replace the 8080 with the port number that your HTTP server is running on.

Enable Wi-Fi Debugging

Connecting to a device via USB is generally faster than using a TCP/IP connection, but a TCP/IP connection is sometimes indispensable.

To set up Wi-Fi debugging:

Complete the Enabling USB Debugging procedure above and then connect your device to your computer with a USB cable.
Install Android Platform Tools, if you have not already installed the adb tool.
Open a terminal or Windows command prompt window.
Locate the adb tool if it is not already in your path. On Windows, it is typically located in C:\Users\{user}\AppData\Local\Android\sdk\platform-tools. Then, use the following command to determine the IP address for the device:

adb shell ip route

The output should look something like this:

10.0.30.0/19 dev wlan0  proto kernel  scope link  src 10.0.32.101

The IP address of the device follows src. Using the IP address and port 5555, issue the following commands:

adb tcpip 5555
adb connect *<ipaddress>*:5555

For example:

> adb tcpip 5555
    restarting in TCP mode port: 5555
> adb connect 10.0.32.101:5555
    connected to 10.0.32.101:5555

The device can now be disconnected from the USB port. As long as adb devices shows only a single device, all ADB commands will be issued for the device via Wi-Fi.

To stop using the Wi-Fi connection, issue the following ADB command from the OS shell:

adb disconnect

Start a Remote Debugging Session with Chrome Developer Tools

After browsing to your web site on the device in Browser, you can debug it remotely using the Chrome Developer tools.

To start a remote debugging session:

On the device, browse to your site in Browser.
Launch Google Chrome.
Navigate to chrome://inspect/#devices.
Find your device, which will be followed by a set of Browser tabs currently open on the device.
Click inspect to start debugging a tab in Browser.

For more information about remote debugging with Chrome Developer Tools, see: Chrome DevTools - Remote Debugging.

Debugging WebXR Content

The information on this page is for debugging 2D and immersive WebXR experiences on Browser. For information about debugging strategies specifically for immersive WebXR experiences, see WebXR Workflow.

For more information about setting up your devices and debugging VR apps, see:

Did you find this page helpful?