Improved Quest 2D app support, including support for native Meta apps like the browser.

Ignore home button presses when device is set to in-house launch method.

Captive Portal may not be rerouted to the login page.

PICO devices were unable to stream to a TV via display cable when configured to ArborXR Home or Kiosk Mode.

VIVE Focus 3 devices on the latest OS sometimes did not boot into ArborXR Home.

On HTC VIVE Focus 3 and HTC XR Elite, accepting screen recording permission did not redirect users back to the previous foreground application.

Quest OS updates can now be set to automatically update, postpone by 30 days or reverted back to default behavior.

Installation of Root CA Certificates.

Immediately update kiosk mode apps when an update is available instead of only updating after a power cycle.

Meta Quest devices on OS v62 would not consistently auto-launch desired apps when boundary was disabled.

When failing to install SCEP certificate configuration, the retry transaction would sometimes get duplicated.

Lock task mode apps would not downgrade.

Session analytics data includes required nested group information.

Meta Quest devices on OS v62 would get stuck in boundary setup.

Meta Quest devices on firmware v60 would experience difficulty opening the default OS keyboard. This behavior has been improved.

Some apps launched via ArborXR Home on Meta Quest devices with firmware v60 would sometimes fail to load.

PICO devices running PUI 5+ that require SSO login sometimes opened to the Quick Access menu instead of ArborXR Home.

Users can now configure PICO Neo 3 Pro (4.8.15+) or PICO 4 Enterprise (5.4.0+) devices to automatically power on when charging.

Users can now configure PICO Neo 3 Pro (4.8.15+) or PICO 4 Enterprise (5.4.0+) devices to keep Wi-Fi on while the device is in sleep mode.

The hand-tracking pinch gesture was not detected on Quest devices with version 60+.

When a device has SSO enabled while configured to Kiosk mode, if ArborXR Home is exited the device will now remain in device home instead of showing the SSO login page.

When a device has SSO enabled while configured to Kiosk mode, after SSO login users will now be taken to the Kiosk app instead of the Quick Access menu.

Protect against the possibility the PICO Device key is missing at startup, used for OS updates.

If connection is lost during device pairing, we will retry once.

Content updates now treat apps in lock task mode the same as kiosk apps.

PICO OS updates would not occur when updates were set to Automatic and the Headset Experiences set to default.

Enabling/disabling the boundary via the Web Portal did not apply correctly on PICO devices running OS 5.x.

Improvements to PICO Firmware management reporting and retry behavior.

ArborXR Home or Kiosk app was not auto-launching on Quest devices with disabled boundary.

On HTC Vive Focus 3 and HTC XR Elite, accepting screen casting permission would not redirect users back to the previous foreground application.

Attempting to set the PICO Neo 3 Pro Eye eye tracking refresh rate would fail, causing other settings to fail to apply. This function now fails silently while we seek PUI v5+ handling advice from PICO.

Reduced some logging.

Added firmware version when pairing with the backend to ensure the device gets valid content.

When OS updates were managed by ArborXR, PICO's OTA update notifications were not disabled on PICO Neo 3 Pro devices running PUI 4.x.

Files will no longer be downloaded, if the destination is inaccessible.

Quest devices set to Passthrough mode would not always auto-launch Arbor Home or the Kiosk app.

On Quest v57, granting OBB permissions dialog would open incorrect menu.

Captive Portal may not be rerouted to the login page.

SCEP Wi-Fi configuration could cause disruption to Wi-Fi connection.

Permissions error when updating existing enterprise Wi-Fi configuration on device.

On PICO Neo 3 Pro Eye devices running PUI 4.8.19, users were unable to exit from Arbor Home to the Pico stock home.

PICO devices running PUI 5.8.x were unable to launch the Bluetooth shortcut.

VRX devices could be placed in a black screen after waking from sleep while in ArborXR Home.

Home button detection would fail on Quest devices running firmware v60.

Casting and Bluetooth shortcuts would not launch on Quest 3 devices.

Kiosk Mode for Magic Leap 2, RealWear, Vuzix, and Android tablets.

Enable or disable Auto-IPD for PICO 4 Enterprise.

On PICO devices, when OS is managed by ArborXR, only the "Accept System Updates" setting will be toggled. The "Accept App Updates" setting will be unchanged.

Support for Meta Quest 3.

Support for DPVR P2, P1 Pro, and P1 Pro 4K Ultra.

Magic Leap 2 OS management (version 1.2.0 and higher).

PICO devices running PUI 5.x and higher would fail to exit ArborXR Home via the settings menu.

On PICO devices running PUI 5.x, using the Arbor Home pause menu or home button to resume apps would instead cause apps to restart.

While in Kiosk Mode with an unmanaged app while managed apps were installed, users would be stuck in a pause menu.

Location permission granting activity can now display while set to Kiosk mode.

When installing managed files, the web portal status may not reflect the actual status of the installation.

Added back the check to see if Remote View permission was rejected by the user to show as error in Portal.

Meta Quest devices already provisioned to the platform prior to the v57 firmware upgrade, may need to grant permissions related to WiFi scanning via the Arbor Home app.

When Wolvic browser (v1.3.4 and higher) is installed, WebXR content will be launched in its kiosk mode on supported devices.

Upon a Meta Quest reboot, the Arbor Home app would sometimes prematurely launch causing a black screen. The initial boundary state is now correctly identified and handled - this includes scenarios where the user as disabled boundary in the Meta developer settings. Additionally some core system packages were added to our built-in allowed apps.

Pico devices running PUI 5.x and higher can now reliably exit ArborXR Home which will now trigger a reboot.

HTC VIVE XR Elite support

While set to the "ArborXR Home" headset experience, any application installed to the device will be allowed to run, even if that app is not marked as visible in the headset experience configuration. Previously we would prevent any unlisted app from running.

Magic Leap 2 devices will now report the Lumin OS version to the web portal instead of the build number.

If Pico's screen casting app was added as an unmanaged app, after starting a stream and pressing the home button, the "Go To Home" option via the Arbor Home pause menu would terminate the stream.

Added support to download app updates silently and automatically install application without interrupting foreground application.

Fixed
After being reconnected to the internet, the device may query or report to backend API more frequently than expected.

The Pico browser would not launch for captive portal on newer firmware.

Reduced the amount of queries required for app/files/videos web portal changes.

Ethernet connection support.

Lenovo VRX support

PICO devices will provide their device-key to the backend so the corresponding firmware can be used when firmware updates are configured.

When no custom banner was used within the 3D environment option, the device would sometimes default to the 360 image.

Screen recording fix to devices that require user permission. Users are now always prompted for permission when recording or remote viewing the device.

Moved creation of ScreenRecordings directory out of initialization to prevent potential permission issues while enrolling.

Various compatibility issues for PICO devices running PUI 5.7 and onwards.

The home app can now be configured to use ArborXR Lounge, our new 3D VR environment for ArborXR Home, with the option to specify a skybox and default or customized banner.

Improved foreground detection on Pico devices running PUI v5.x, resolving various bugs, including the inability to open the ArborXR quick access menu.

Pico devices running PUI v5.6.0 or later can now correctly resume apps following a home button press. Devices running earlier version of PUI v5.x will continue to restart the paused app, rather than resume. This is due to a recent firmware change that allows us to entirely prevent the "Exit" dialog offered by the Pico OS.

Pico firmware management settings update more frequently.

Firmware management for PICO devices running v4.8.19 or higher.

Reduced bandwidth usage via APK patched upgrades.

Potential error completing duplicate remote view start request.

When trying to start remote view and the feature is not enabled on the device, we were not communicating that error to the user.

The destination path for files can now be configured on a per group basis via the web portal.

Improved video quality of PICO devices running PUI 5.

Improved video quality for API 29 and lower devices when recording the device screen.

Supported device models (not including Quest) now allow remote viewing initiated via the web portal.

Captive Portal not launching on Pico Neo 3 devices on firmware 4.8.19.

The home button opens the quick access menu in ArborXR Home on PN3 devices running v5.x firmware.

A number of supported devices can now access the screen recording feature via the home app.

Home button detection now correctly matches PUI v5.x default button mapping when controllers are disconnected.

Reboots on the HTC Vive Focus 3 could potentially cause an Arbor Home restart loop.

Under specific circumstances, using the External SDK may cause the app to crash on startup.

Reduced home app crash detection frequency, preventing potential multiple attempts to handle.

Failed HTC Vive Focus 3 batch configuration attempts logging included sensitive data.

Support for granting OBB permissions via in-VR UI flow.

Wi-Fi Certificates were not always deleted properly when no longer assigned to the device.

On Meta Quest devices, double-tap passthrough would return users to Arbor Home instead of the current application.

If the currently running app was reinstalled, the current Headset Experience setting wasn't enforced, allowing the user to escape to disallowed apps.

Reduced the potential for "Application Not Responding" messages on Meta Quest devices.

Additional IO operations were running when querying for new video details.

Kiosk Mode applications that have the public SDK integrated may trigger a client crash.

On Meta Quest devices, on rare occasions the user may be left in a black screen following a reboot.

If a user paused an app and logged out of SSO while set to Arbor Home, after SSO login they were taken back to the paused app instead of the content menu.

Some Meta Quest apps would crash when transitioning between them using the home button.

Reduced the potential for "Application Not Responding" messages on Meta Quest devices.

On Meta Quest devices running v51+, the system menu to Restart or Power Off would not appear if the device is configured to ArborXR Home or Kiosk Mode.

On Meta Quest devices, the dialog to accept USB File Transfer would sometimes not appear.

Correct Meta Quest Pro device model detection.

Meta Quest v51 users were sometimes able to access previously blocked stock apps, such as the store, via the bluetooth or casting shortcut. This includes a new mechanism to block access to the Avatar.

Meta Quest users were often able to access the stock Meta Quest pause menu overlay when pressing the home button after a reboot - the time window has been significantly reduced, and attempts to do so will result in the overlay closing shortly after.

Reduced the potential for "Application Not Responding" messages on Meta Quest devices.

For all devices but specifically noticeable on Meta Quest, drastically reduced the app start-up time following a reboot.

The Android 11+ file permission update made Arbor's media directory unaccessible to the home app, thereby preventing custom content thumbnails and background environments from loading in.

Pico 4 Enterprise and Pico Neo 3 devices would sometimes fail to load ArborXR Home after a reboot.

Pico 4 Enterprise devices were unable to exit apps while using the home button, due to a Pico UI interception dialog.

Thumbnail icons for videos weren't being resized before downloading, contributing to performance degradation within the home app.

Support for imported PKCS12 enterprise Wi-Fi configuration.

Support for supplying devices with WebXR content via the web portal.

Added Simple Certificate Enrollment Protocol (SCEP) support for enterprise Wi-Fi configuration.

The "Powered by ArborXR" logo in the Arbor Home is now hidden for customers on the Enterprise plan.

Supported devices can now enroll via QR codes.

Support for uploading videos through the web portal and showing them in the home app.

Remotely launch videos from the web portal.

File deployments would sometimes fail due to permission restrictions on Android 11 devices onwards.

Meta Quest devices take upwards of 10 seconds to load the Kiosk Mode or Home App.

Configuration a boundary via the boundary shortcut on Meta Quest 2 devices running firmware version v50, would sometimes remain in the default shell environment.

Initial SDK subscriptions to interests would sometimes timeout resulting in the home app lacking key information at startup.

Local database is now deleted when device ownership is removed.

The storing of a refresh token is now available at the start of the app to make Setup authentication more reliable.

Increase timing intervals used by most components that query or report to the backend API.

HTC Vive Flow devices were reporting the kernel version to the web portal, rather than the firmware version.

Enrolling a device to a group without wifi configurations would assign empty device configurations.

Managed files, updates and removals can now be scheduled via the web portal.

Support for detecting the same serial number displayed on the packaging of RealWear devices.

Some HTC VIVE Focus 3 devices can access restricted controller pairing options via the home app.

Arbor Home support for Pico 4 Enterprise devices.

Further error reporting criteria has been applied.

If a device was already known to the backend, subsequent pairing attempts would fail if the devices was unable to remove a previous installation.

Support for provisioning devices via configuration packages.

Meta Quest 2 devices were wrongly detected as Meta Quest 1 with firmware version v47.

HTC VIVE Focus Plus devices can access WiFi settings within ArborXR Home and Kiosk Mode.

Older devices on at least API Level 27 and below were not logging to our remote logging service.

If a WiFi configuration failed to apply, the WiFi SSID was not correctly obfuscated.

The new 'Pico Cast' app can now be used by supported devices while set to the kiosk or custom home launch methods.

An automatic self-enrollment authentication process has been added.

Setup login endpoint to allow for faster device login from the Setup App.

On HTC Vive Flow devices, the screen would flash repeatedly after a reboot.

Failed HTC Vive Focus 3 Batch Configuration attempts will automatically attempt self-enrollment.

Support for filtering applications in ArborXR Home by tags.

Invalid WiFi configurations from web portal may cause the device to constantly disconnect from the current WiFi connection.

Sometimes an app would disappear from the app library view following a successful installation.

On HTC Vive Focus 3 devices, the home button would sometimes be inoperable after rebooting the device while set to custom home or kiosk modes.

Using the casting or bluetooth shortcuts on the HTC Vive Focus 3 would sometimes fail to launch.

Using an in-app quit method would sometimes fail on HTC Vive Focus 3 devices.

Sometimes following a reboot, the current foreground details would be innacurate resulting in the home or kiosk mode apps not automatically launching when they should.

On supported device models, users can remotely wipe application data via the web portal.

On Pico Neo 3 and Pro Eye devices, sometimes the home app or kiosk mode app would not automatically start after a reboot.

Further error reporting criteria has been applied.

On Meta Quest devices running firmware v46, the casting shortcut would allow users to access the Quest's native home environment.

The app now supports SSO authentication and Guest Access when the device is configured with an SSO Identity Provider.

Managed app installs, updates and uninstalls can now be scheduled via the web portal.

Enabled capture of user events tracked by external SDK clients.

Some error report filters didn't account for nested exceptions. Further error reporting criteria has been applied.

When a device is deleted via the web portal, the client will acknowledge deletion and will no longer communicate with backend servers.

The following device settings can be changed on Pico devices via the Web Portal: System Sleep Timeout and Display Timeout.

On the Pico Neo 3 Pro Eye, the Eye Tracking Refresh Rate can be changed between 90hz and 60hz via the Web Portal.

User events tracked by external SDK clients will be reported to the backend via the createDeviceEvents endpoint.

Devices with large files assigned would temporarily hang when unnecessary checksums were being performed. Subject to timing, this could cause drops in performance, unresponsive home button presses, Meta Quest or HTC Vive Focus 3 stock UI appearing, unresponsive interactions with some home app functionality, delayed reporting of content statuses, and more.

The scanned WiFi networks list in the home app will include all available WiFi networks that are already configured on the device, even if the security type is not Open/PSK/SAE.

Added obfuscation to logs related to WiFi.

Pico Neo 3 devices running PUI 4.8.15 experienced various issues when using ArborXR Home or Kiosk Mode launch methods.

Newly added WiFi configurations at time would not automatically connect.

Captive portal verification would sometimes fail due to an incorrect http response code.

Reconnection to a configured WiFi network would at times fail due to a BSSID conflict.

Following a device reboot, a WiFi configuration at times would be forgotten if it was previously a server configuration.

Scanned WiFi network changes were continuously reported to the web portal without any substantial changes.

Remote actions such as remote launch app, remote reboot devices, and remove factory reset via the web portal sometimes wouldn't execute.

WiFi configurations provisioned from the web portal were not applied once the first configuration failed to apply.

The app now supports Progressive Web Apps (PWA) on Meta Quest devices.

If the current WiFi connection was forgotten via the default device home environment, the home app would not prompt for a password upon reconnection.

To improve WiFi connectivity status in the home app, the list of known WiFi configurations is updated for all outcomes of a new or updated connection attempt.

Following a device reboot, if the device had no active internet connection, assigned apps would not show in the home app.

The home app would sometimes prompt the user to enter a password for a known WiFi configuration.

File extensions of media files were not being preserved during the download process, therefore resulting in them not displaying correctly inside the home app.

Unmanaged apps can now be added to a device via the web portal's launch method settings. Unmanaged apps show in the home app, just like managed apps, although they will not show installation or update progress as they are expected to be pre-installed.

After completing captive portal authentication, the home app or kiosk mode app will be launched.

On Pico Neo 3 and HTC VIVE Focus 3 devices where captive portal authentication is required, a browser would not always start automatically.

Rebooting HTC VIVE Focus 3 devices via the web portal would sometimes cause the device to reboot multiple times.

For Magic Leap 2 devices, the firmware version visible in the web portal will now exclude supplemental text.

Device factory resets can now be restricted via the web portal.

The device will forget WiFi networks when corresponding configurations are removed via the web portal.

The app now supports the ability to reboot a device and launch an application from the web portal.

To ensure errors are identified quickly, internal error tracking has been optimized to treat several specific scenarios as warnings instead of errors.

To improve the performance of the custom home app, cached images are now resized to the size they are needed.

The ArborXR Home app can now request to open controller settings on Pico G2 4K devices.

Instead of failing to install app updates when the signature changes, the client app now automatically uninstalls the previous build if needed.

The client app version shown in the web portal on a device's status page now includes more details to identify preview builds.

To ensure errors are identified quickly, internal error tracking has been optimized to treat several specific scenarios as warnings instead of errors.

When the device was turned off and not turned back on for days, there was a slight chance that the previous app session was reported to span multiple days.

In some scenarios, the web portal showed the wrong home app version on the device status page.

On Meta Quest devices, the stock keyboard failed to display once the home button had been pressed while using the custom home or kiosk mode launch methods

Some built-in apps were not allowed to run when set to ArborXR Home or kiosk mode. The user was instead returned to ArborXR Home or to the kiosk app. As part of this issue, users could not access the controller binding app on Pico G2 4K devices.

The device's location is tracked based on WiFi details and reported to the platform.

The app now supports upcoming WiFi management functionality in the ArborXR Home app.

To allow the ArborXR Home app to display the captive portal for the currently connected WiFi network in the future, the app now recognizes whether a captive portal is required.

To support location tracking via WiFi and upcoming WiFi management in the ArborXR Home app, location services will be enabled automatically.

The ArborXR Home app's environment background image can be changed via the web portal.

Functionality not available on specific device models lead to automatic error collection. Since the functionality is not available, to begin with, no errors will be raised anymore.

When set to ArborXR Home or kiosk mode, the controller binding flow after a device reboot was interrupted on Pico G2 4K devices.

The ArborXR Home app or kiosk app was sometimes launched even though it was already running. This resulted in a brief flicker of the app.

On Meta Quest devices, using the hand gesture to return to the home app while in a stock app like WiFi settings resulted in the panel hiding instead of returning the user to the ArborXR Home app or kiosk app.

When the platform had authentication issues, the ArborXR Home app showed an error instead of displaying the apps list. The client app will now retry the authentication in the background, while the ArborXR Home app will continue to work based on the last data received by the servers.

The device's Bluetooth name is now set to the device title as configured in the web portal.

Launching 2D apps on Oculus devices is now supported.

Support for launching stock Oculus apps such as Files, Browser and TV has been added.

Apps can now use the Oculus keyboard.

On Oculus devices, the user can now use hand tracking gestures to pause and resume apps.

The controller setup flow that normally displays on boot is now supported on Pico G2 4K devices when using the ArborXR Home or kiosk mode launch methods.

Using the boundary shortcut on Oculus devices allows the user to adjust an existing configuration, rather than automatically resetting the previous.

On Oculus Quest 1 devices, the home button will no longer resume the paused app. The user has to click the "Resume" button instead. This resolves a performance issue that occurred when the user quickly paused an app after resuming it.

When exiting Admin Mode while in kiosk mode, the user is now automatically returned to the kiosk app.

While using the Default Home Environment launch method, the shortcuts in ArborXR Home did nothing.

While in kiosk mode, when opening a shortcut, the user was returned to the quick access menu instead of the kiosk app.

Once the kiosk app was installed, it was not automatically started. The user was taken to the quick access menu instead.

When the user navigated to a disallowed app while in kiosk mode, the quick access menu displayed instead of bringing the user to the kiosk app.

When using the home button to resume a paused app, the device was sometimes flickering the quick access menu before finally displaying the paused app again.

When kiosk mode was used while the ArborXR Home app was not installed yet, there was an attempt to open the pause menu that is missing still, resulting in an undesired app transition.

Pressing the home button while in kiosk mode without the ArborXR Home app installed, some devices displayed the stock overlay.

After a reboot, some devices had a chance to just display a black screen or loading indicator instead of ArborXR Home or to the kiosk app.

When opening some shortcuts on Oculus devices, the user was sometimes immediately returned to ArborXR Home or to the kiosk app.

The app was sometimes slow to respond to various device changes because communication with the ArborXR Home app was delayed whenever the home app stopped.

On Oculus devices, the boundary dialog was sometimes taking long to appear while the user was stuck in the pass-through view.

A black screen transition occurred on Pico devices whenever the user pressed the home button while in the ArborXR Home app with no paused app.

A slider to change the screen brightness was available in the ArborXR Home app on devices running earlier versions than Android 9, even though that functionality is only available on Android 9 and later.

Launching Oculus Browser failed on operating system version 40, because the app no longer supports the default launch intent.

Support for ArborXR Home to display the WiFi MAC address and randomized MAC address has been added.

Pairing a Bluetooth device failed on Pico devices when using kiosk mode or ArborXR Home.

The app did not communicate with the platform when location services were disabled on the device. Location services are no longer required for core functionality. However, some parts of the WiFi status won't be able to be reported until location services are enabled.

Opening a shortcut sometimes resulted in the user immediately returning to ArborXR Home or kiosk app on some Quest devices.

Support for the new launch method, "In-House Launcher", has been added.

Opening a setting on Quest devices sometimes prematurely returned the user to ArborXR Home or the kiosk app.

The language the ArborXR Home app uses can now be set via the web portal.

In preparation of allowing to add "unmanaged" apps to be visible to headset users in ArborXR Home, the app now tracks whether an installed app is a VR app or a system app.

On Oculus devices, the Bluetooth, WiFi and screen casting shortcuts can now be used after enabling them via the web portal.

The boundary shortcut was visible on Pico G2 4K devices, even though the device does not support a boundary.

All runtime permissions are granted to apps deployed via the platform from now on.

On Pico Neo 2 devices, the UI elements in the ArborXR Home app were not reacting to triggers clicks from controllers.

After moving a device to a different organization, the app continued to communicate to the previous organization for up to 15 minutes.

The app now immediately switches to the new organization as soon as it recognizes the change, limiting the time it takes to a maximum of one minute.

While setting up HTC VIVE Focus 3 devices via a batch configuration, ArborXR Home or kiosk mode app launched once the device obtained an internet connection, preventing the user from completing the initial device setup.

Opening the stock home shortcut on HTC VIVE Focus 3 devices sometimes immediately returned the user to ArborXR Home or the kiosk app.

If the app encountered an issue while refreshing authentication details, all communication with the platform failed until the device was rebooted.

The startup speed of the app has been optimized to ensure ArborXR Home or Kiosk App is started as early as possible.

The time a user could spend in the stock home environment after rebooting an Oculus device and rapidly accepting the Guardian dialog has been reduced.

On HTC VIVE Focus 3 devices, the stock home app did not launch when setting the launch method to Default Home Environment in the web portal, when using the button to exit the ArborXR Home app in the headset, or when the ArborXR Home app is not yet installed.

Admin mode wasn't automatically exited if the admin PIN changed.

Changing a device setting via the web portal while the user was in admin mode prevented the user from exiting admin mode.

The boundary shortcut was visible in ArborXR Home when the boundary was disabled in the web portal.

On Oculus devices, the app sometimes returned the user to ArborXR Home or kiosk app while accessing shortcuts.

After rebooting Oculus devices, the Guardian dialog disappeared for several seconds if not accepted rapidly.

Waking up an Oculus device sometimes resulted in the stock home environment being displayed instead of ArborXR Home or kiosk mode app.

When using the reboot button found in ArborXR Home's quick access menu, the last recorded session a device was in would sometimes end earlier than expected.

On Oculus devices, the app sometimes returned the user to ArborXR Home or kiosk app while accessing shortcuts.

After rebooting Oculus devices, the Guardian dialog disappeared for several seconds if not accepted rapidly.

Waking up an Oculus device sometimes resulted in the stock home environment being displayed instead of ArborXR Home or kiosk mode app.

When using the reboot button found in ArborXR Home's quick access menu, the last recorded session a device was in would sometimes end earlier than expected.

To ensure previously accessed settings don't show up when using the device's back button, all stock Android settings are now quit once the user returns to ArborXR Home.

The stock Android settings were not quit when the user returned to the kiosk app.

The boundary shortcut was missing on Pico devices when using a build of the app that is not system-signed.

Pressing the home button after opening a shortcut did not return the user to ArborXR Home or the kiosk app.

Refactored the client app from the ground up to enable the new launcher, ArborXR Home.

To ensure devices correctly identify when the active network connection offers a working connection to the internet, the app is now setting the DNS lookup URLs the operating system uses. The DNS lookup will now be done against ArborXR's servers. This means Pico devices no longer require allowing a connection to a specific Pico service, which is hosted on Chinese infrastructure.

On Pico Neo 3 devices running the Pico operating system version 4.3.23 or later, the 2D launcher would no longer react to input from the user and thus become unusable. To work around this operating system bug, the 2D launcher is now force-shown whenever the user navigates into an app that is not currently allowed according to the configured launch method. Previously the user would not be able to even attempt to start another app to begin with. The existing logic has been kept unchanged for all other device models.

On some Pico devices, the device sometimes failed to display the keyboard when trying to join WiFi networks. As a potential fix, the built-in Chinese keyboard (called Sogou) is now allowed to display when using the multi-app launcher.

The device pairing app can now ask the client app whether all data required for the pairing process has been received.

To overcome an issue in which Android applies restrictions to the app, the device pairing app can now request that the UI of the client app is visible for a short period of time.

The web portal will now display the expected operating system version for VIVE Focus 3 headsets.

WiFi configurations that use EAP-TLS or EAP-TTLS were not getting added to the device correctly.

When using enterprise WiFi configurations, users were unable to specify no CA certificate to be used. This is now supported via the new setting "Do not validate". The "Domain" setting is no longer required as well.

When the settings for kiosk mode or multi-app launcher changed, the headset user would always be brought back to the kiosk mode app or the launcher. From now on the user can continue with the running app, as long as the app is still allowed according to the latest settings. The kiosk mode app or the launcher continues to be started when the launch method is changed from previously being set to the default home environment, or when the device boots up with this setting still set.

When using kiosk mode or multi-app launcher, captive portals can now be accessed on devices that support them.

The multi-app launcher failed to render on Pico G2.

Oculus devices can now access Bluetooth settings from the multi-app launcher.

Oculus devices can once again access WiFi settings from the multi-app launcher.

Navigating to the WiFi or casting settings from the multi-app launcher resulted in the started app to be rendered incorrectly on Pico Neo 3.

On Pico Neo 3 the multi-app launcher was not closing the app launch animation once the user returned to the launcher.

Apps that come with .obb files were visible in the headset too early, before the .obb files were installed completely. If the headset user started these apps during that time, the apps failed to launch if they required the .obb files.

WiFi network configurations can be managed via the web portal. Users can still add and remove their own networks inside the headset, but changes to the configurations managed by the platform are prevented.

Support for version management has been added: Users can now select the app version to deploy to their devices via the web portal. As part of this feature, users can now downgrade apps to earlier versions.

Apps can now be installed if the build archive is a Zip64 archive. Previously these installations gave an error instead.

To enable version management, apps are now automatically downgraded to an earlier version, if that's the version set to deploy to the device according to the web portal. Previously, devices were able to have side-loaded app versions installed that were greater than the version marked for deployment in the web portal. Users who intend to side-load different app versions (compared to what they have set in the web portal) should remove the app from the device in the web portal to prevent the client app from managing that app.

Opening the casting options via the multi-app launcher on Oculus devices resulted in a black screen. The casting option has been removed on these devices.

The device status was not updated while removable storage was attached to the device. Because the operating system does not provide insight into the remaining/used space of removable storage, removable storage is no longer reported as part of the device status.

On Pico Neo 3 the multi-app launcher was rendering in portrait orientation, instead of the desired landscape orientation.

Especially after a reboot while in multi-app launcher mode, the Pico Neo 3 had a chance to render the launcher and other 2D apps incorrectly (as if they are VR apps).

When starting the multi-app launcher on Oculus devices, the operating system asked to switch to controllers. Hand tracking is supported on these devices again.

The device serial is displayed in the multi-app launcher.

The multi-app launcher displays a welcome page when the app is not set as the device owner.

Under specific circumstances the app had a chance to crash on startup.

Session analytics events had missing version information for the running app if the app was uninstalled shortly after it was running. As version information is required, no further events were transferred to the platform, but affected devices have been recording new events in the meantime. These devices will send all data as soon as they update to this Client App version.

Hidden files as well as macOS resource forks were not ignored properly, leading to app installation errors.

The Tobii User Calibration app was visible in the multi-app launcher even on device models that don't support eye tracking.

Support for a file-based approach to configure the client app has been added.

To support other ways to install the app besides using the device pairing app, the client app now automatically grants itself all required runtime permissions at startup.

On Pico devices the multi-app launcher allows access to the Tobii User Calibration app.

Attempting to open the casting options a second time crashed the multi-app launcher.

On devices that support casting functionality, the multi-app launcher now includes access to the casting options.

Apps managed via the web portal will appear first in the multi-app launcher.

Apps that were uploaded as a zip from macOS failed to install if the OS included resource forks (found in a nested `__MACOSX` folder) for the archived files. Resource forks as well as hidden files (i.e. files that start with a dot in their name) are now ignored.

In the rare edge case that stored information from a previous run of the app was corrupted, analytical insight was no longer recorded nor reported.

Attempting to reboot the HTC VIVE Focus Plus while in kiosk or multi-app launcher mode didn't work.

Additional details have been added to the logging to ease troubleshooting of potential issues.

On some devices accessing WiFi settings in the default home app failed when the launch method was either set to kiosk mode or multi-app launcher.

If the device was using kiosk mode or multi-app launcher, it failed to allow the default home environment to run and instead repeatedly tried to start the kiosk mode app/launcher.

Reduced the number of check-ins with the platform down to one.

Workers running inside the app failed to properly cancel and instead ran work multiple times.

Details about when the device was started or stopped, as well as insight about the running applications are now recorded (even while the device is offline). The collected information is then reported to the platform to allow the user to view detailed session analytics in the web portal.

Content that has been installed by the app previously, but has since been deleted from the platform, is now left as is and is no longer uninstalled.

The app now regularly checks in at the servers in an optimized manner, letting the whole platform know when the device was last seen. The web portal uses this information when displaying the last status of the device, and the aforementioned analytics feature also uses the gained insight for session details.

The number of possible concurrent downloads has been increased.

Whenever the files assigned to the device didn't actually change, the retrieval of the latest files list resulted in unnecessary checks.

Deleting a device from the web portal didn't reset the device back to the default launch method.

The app could crash in very specific and rare edge cases.

If an operation was canceled, the next attempt to repeat the same operation waited for the canceled operation to finish. In some cases this resulted in content installation getting stuck in the "pending" state according to the web portal.

File management wasn't working and gave permission errors on devices running Android 10.

On devices running Android 10 or later, the app stopped reacting to changes done in the web portal if file management failed.

File support has been added. File operations work similar to content operations and status is reported to the user the same way via the portal. For more information on file support see this article.

Additional measures have been added to ensure the persisted data is not corrupted even if the device shuts down unexpectedly.

The configured launch method is enforced repeatedly in the background on devices that allow access to the device's home app.

Automatically set the date and time. Users are still able to change their time zone if the device normally offers that functionality.

When using external storage like an SD card, the client app no longer reported device health/status information.

Some devices required a reboot of the device to apply self-updates to the app. Until then the app was no longer working. A potential fix has been applied and we continue to monitor the issue.

The multi-app launcher no longer shows apps that cannot be started on their own. This includes apps like some video players, as they require pointing it to a file to view. Such apps are often instead started by file managers. All configured apps continue to be added to the list of apps allowed to run, to allow the user to transition from a file manager to a viewer app.

Upon device deactivation, if content uninstallation is desired, all content managed via the web portal will be uninstalled from the device, even if the content was originally installed by other means.

When setting the launch method to multi-app launcher in combination with a third-party launcher, the app will no longer aggressively restart the launcher app whenever the user backs out of it. Since the launcher allowed the user to leave it, the app allows the user to navigate to apps in the allowlist as part of this change. This change allows users on Oculus devices to utilize the browser app (if that app is also included in the allowlist).

The rate at which progress of .apk and .obb installation is reported has been reduced to improve performance slightly. This reporting is only used for internal purposes - the content status still updates in the web portal in a span of seconds.

Improved reliability of local data persistence in the event of app crashes and/or unexpected device shutdowns and reboots.

Automatic error collection stopped after a specific error was encountered.

If a device updated the operating system to run a newer Android version, the app would cease to function. This was due to the app recognizing that new permissions are available in that Android version, which weren't granted to the app because it was installed when the device was still running the older Android version.

In the web portal the version was reported as `2021.<Week number>` instead of the expected `2021.<Week number>.<Release that week>`.

Checking for the currently running app was stuck in an infinite loop if it has been days since the current app changed.

All apps now include detailed version information to ease the process of identifying development and QA builds. The user-facing versions are staying the same.

When there's an issue reporting the progressing of a content installation, the app no longer fails the installation. The issue is ignored for intermediate progress, but completion status reports are retried indefinitely.

The multi-app launcher treats small scrolling movement as clicks. This makes it easier to start apps with a controller's trigger or on devices that support hand tracking.

Requests to the servers are retried only when encountering transient issues. Additionally a timeout has been added to help with connection issues. Previously all errors were retried, even if there was no chance for the next attempt to give a different result. This resulted in some operations taking longer than expected.

The app did not acknowledge that it is starting to uninstall content. For content of bigger sizes, this resulted in the web portal looking like the device is not receiving the uninstall command, only to then suddenly mark it as uninstalled.

This release is simply a re-upload of the previous build to overcome the content download issue that is hit by devices as part of updating to this release.

The running app will now appear in the web portal as part of the device's status.

The startup speed of the app has been improved slightly.

The WiFi Settings app is hidden inside the multi-app launcher on Oculus devices. The operating system does not correctly show the keyboard in the system WiFi dialog on those devices.

When content failed to download, the app didn't update the content's status correctly. Download errors are now visible in the web portal.

Downloading builds of files that have spaces or special characters in the file name failed. Due to the aforementioned issue this would not be visible to users as part of the content's status in the web portal.

To be more responsive when encountering connection problems, all communication with the servers is retried a few times. Previously the affected operations would only be retried ten seconds later (or even later, depending on the operation).

Additional logging has been added to ease the process of diagnosing communication problems with the servers.

Content that has been installed by the app previously, but has since been deleted from the platform, is now uninstalled.

The multi-app launcher showed the app itself as content.

For devices that provide information about the remaining charge time, the time was showing up as "0 minutes" in the web portal whenever the device wasn't charging.

Content that has no available build yet wasn't ignored properly. The app will no longer repeat an error as the content install status.

Content installation and uninstallation sometimes failed if a previous attempt at the same operation was canceled or failed.

The multi-app launcher failed to start up automatically the first time after a device reboot on devices running newer Android versions.

Failure to install or uninstall content was not recognized when the final step of the operation failed due to an issue in the Android internals.

Content that has been uploaded as a zip failed to install.

App data wasn't properly deleted when remotely deactivating the app.

Device health data was not visible in the web portal for some devices running Android Oreo or earlier.

All required permissions are checked on startup of the app. Previously this wasn't done and as such some silent failures of the installation via the pairing app resulted in failing functionality in the app.

The versioning scheme used by both the app and the pairing app is more user-friendly. Both apps follow the scheme `Year-WeekOfYear-[FurtherRelease]` where `FurtherRelease` is an ever increasing number that is starting at `0` and is attached as a suffix to the original release of the same week. E.g.: A release in the first week of 2021 is `2021.1.0`. A release to fix an issue that is released in the same week will bump that version to `2021.1.1`, while any further release in the same week would result in `2021.1.2` and so on. The (first) release of the second week will use `2021.2.0`.

The pairing app and the app now use the system's built-in networking technology, which ensures proper support for TLS 1.2 and other modern network communication standards.

Logging has been improved to allow easier troubleshooting of issues. Additionally, if a crash occurs the details are collected the next time the application runs.

A reinstall of the app to a device via the pairing app shows as a single progress. Previously the operation was split into two operations that each went from 0% to 100%.

Background work done by the app is more optimized by introducing the concept of constraints. E.g. device health is only monitored when the device is active and online.

The app only refreshes its authorization once whenever necessary. Previously there was a likelihood of multiple refresh operations being done at the same time.

In kiosk mode the user stays in the primary app or the launcher when using the headset's back navigation functionality. Previously there was an animation to a black screen before the user was returned back to the configured app.

When toggling off kiosk mode or toggling off the use of the launcher, the currently running app from the previous allowlist will no longer be stopped. The user can continue in it and won't potentially lose any progress. When the user attempts to quit the Kiosk mode content they will be taken back to it automatically. To allow quitting the kiosk mode app the launch method of the device must be changed in the web portal.

On the Vive Focus the operating system version shown in the device's overview page is now matching what the Vive menu shows.

The app sometimes got stuck and no longer did anything. Self-updating often triggered this issue, but sometimes content operations also triggered it. A device reboot often resolved the issue for a while, but when self-updating triggered the issue even that didn't help and a reinstall of the app was required.

Failing background work in the app is retried repeatedly. Previously specific work only was attempted again after rebooting the device.

The multi-app launcher was leaking (an insignificant amount of) memory whenever it was started.

When the device went offline during content management, the current content status sometimes didn't display correctly in the web portal. The information is updated once the device goes back online.

Some edge cases resulted in remote device deactivation working, but not acknowledging it correctly in the web portal. Once deactivated, the device is deleted as expected in the web portal.