Oculus Go Development

On 6/23/20 Oculus announced plans to sunset Oculus Go. Information about dates and alternatives can be found in the Oculus Go introduction.

Oculus Quest Development

All Oculus Quest developers MUST PASS the concept review prior to gaining publishing access to the Quest Store and additional resources. Submit a concept document for review as early in your Quest application development cycle as possible. For additional information and context, please see Submitting Your App to the Oculus Quest Store.

Debug Your Browser Content

You can use the Chrome Developer Tools to debug and inspect your site in Oculus Browser. You can debug remotely either over USB or with a TCP/IP connection over Wi-Fi.

As a prerequisite, you must install the Android Platform Tools and appropriate device drivers to use ADB.

Enable USB Debugging on Oculus Go and Quest

To configure your device for USB debugging:

Open the Oculus companion app on your phone.
Select your Oculus device in Settings.
Tap on More Settings
Tap on Developer Mode, and use the toggle to turn it on.
To connect a device via USB, plug the device into a PC with a compatible USB cable. 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.

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 Oculus 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 Oculus Browser.
Launch Google Chrome.
Navigate to chrome://inspect/#devices.
Find your device, which will be followed by a set of Oculus browser tabs currently open on the device.
Click inspect under to the Oculus Browser tab you wish to debug.

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

For more information about setting up your devices and debugging VR apps, see the following topics.