A status column has been added to device groups to show whether an app is queued for deployment, installing, or successfully installed, and provides additional details on any deployment errors that may have occurred.
WiFi and boundary setup have been added as launchable apps to ArborXR’s custom Multi-App Launcher for Pico devices. This enables end users to access settings like WiFi and boundary setup while being restricted to the “whitelisted” apps available to them within the Multi-App Launcher.
Kiosk Mode has been improved on Oculus Quest and Quest 2 such that the “whitelisted” kiosk app will automatically re-launch if end-users accidentally quit it via Oculus’ universal menu.
Likewise, the Multi-App Launcher will re-launch anytime users quit one of the apps “whitelisted” for the launcher.
The source code of the Client App has been restructured so as to improve operation and certain functionality. Click here for additional information on notable bug fixes and improvements.
The source code of the Pairing App has been restructured so as to improve operation and certain functionality. Click here for additional information on notable bug fixes and improvements.
When adding content apps you can now specify compatibility with multiple device types. For example, if you add an app that is compatible with both Quest and Quest 2, by specifying both device types in the “Device Compatibility” input, this ensures your app will be available for deployment to both Quest and Quest 2 devices.
This product improvement allows you to go into the “Manage Organizations” page and set a default organization as well as change the order of your organizations.
Add release notes to each version of your content app and view other information such as the versionName, versionCode, and the filename of the APK and any corresponding expansion files, such as an OBB file.
With this improvement users can upload an OBB file alongside their APK. When users deploy a content app that contains an OBB onto a device, the OBB will automatically be deployed alongside the APK. Note that the APK and its associated OBB must be in the same zipped folder in order for ArborXR to process the upload.
This product improvement is relevant for users with multiple device types. If a user selects multiple devices, and if multiple device types are represented in their selection, users will be prompted to edit device settings (like Kiosk Mode) on a per device type basis. For example, users will manage device settings for Pico Neo 2 separately from managing device settings for Oculus Quest.