We’re excited to roll out the latest update to Oculus Developer Hub (ODH). In this release, we’ve focused on a few features that have been widely requested by the developer community. We also made fixes that improve the reliability of commonly used features within ODH.
Here are some of the highlights:
Custom ADB Path
One of the most requested features we’ve heard is for the ability to view device logs within ODH. This gives developers the ability to understand what’s going on within their apps and on Oculus headsets in general. This capability is now fully supported in ODH.
You can filter logs by priority as well as text or regex filtering. Log output can also be downloaded to a text file. All of this is available in a separate window so you can continue using ODH while capturing log output.
ODH has had the ability to display your app information on the Home screen since version 1.0. However, if you are a member of multiple developer organizations, ODH would only show apps for one of your orgs. With this update, you can now switch between any of your orgs with Org Manager and view their apps.
This is a significant improvement for any developer that works within multiple orgs and will serve as the foundation for future org and app capabilities within ODH.
Many of the useful headset capabilities offered by ODH are made possible by integration with Android Debug Bridge or “ADB”. This is a tool that allows you to control and retrieve information from Android devices. ODH automatically comes bundled with ADB to ensure that it’s available when running ODH. This can sometimes conflict with a version of ADB that may already be running on your system. To accomodate this use-case, ODH now allows you to configure an ADB path within Settings. This will be the ADB instance that ODH uses for interactions with Oculus headsets.
Casting is one of the most-used features in ODH. One issue developers reported was that casting would fail when attempting to cast from a headset that was signed-in with a different account than ODH. This is not currently a supported use-case. ODH will now show a warning when this happens. In addition, when casting finishes, your proximity toggle setting will now be respected if it was disabled prior to casting. We also made improvements under the hood to improve general reliability and reduce errors.