Known Issues

Oculus for Business November 2021 Release

Version 29.0 known issues

Known issues with work arounds

  • When an app is removed from the headset through Device Manager, the app may not be removed from the App Library. If this happens, enable Admin Mode and select the Check for Updates button.

  • Home screen with bubbles on it might display in headset after provisioning. If this happens, enable Admin Mode and select the Check for Updates button.

  • Headset display may turn black if Guardian is adjusted while in an in Kiosk Mode. If this happens, reboot the headset or attempt to set the Guardian again.

  • Casting might fail to continue after the headset has been sitting idle for 15 seconds. If this happens, reboot the headset and try casting again.

  • "Swith to Controllers" prompt may appear after attempting to restart an app using controllers when hand tracking is enabled in Device Manager. If this happens, select Continue on the promprt to dismiss it.

  • When casting, the in-headset experience is still seen on the casted device after the headset has been removed from the user's head. If this happens, wait 15 seconds for the casting screen to return to a blank, black screen.

  • If an app is paused and Wi-Fi settings are opened, the app will disappear. If this happens press the Oculus button on the right Touch controller to display the app again.

Known issues with no current work arounds

  • Some apps may display the Oculus logo as a pause screen placeholder instead of the app that was paused.

  • Scrolling through Storage Manager with controllers may not function as expected.

  • USB debugging is enabled on headsets when it is displayed as disabled in Device Manager.

  • If Guardian is disabled, passthrough will not display while pairing controllers.

Mobile Device Manager fixes and known issues

General fixes for v29

  • It is possible for a user to link to the wrong MDM on the Apps page of Device Manager. As of v29, Device Manager will display a status of "Setting Device Owner Failure".

  • The confirmation prompt for powering off or restarting the headset will now display if power button is pressed and held during enrollment.

  • The prompts for "Allow access to data" and "Allow USB Debugging" will now display if selected during device enrollment.

  • The MDM panel will now automatically launch when the headset is powered on after installing MDM.

  • Apps added to a headset from the MDM will no longer be blocked if "Enable Sideloaded Apps" is disabled in Device manager.

  • The Wi-Fi settings panel will now display if selected during device enrollment.

  • The prompt for "Allow USB Debugging" will only be displayed once now.

Workspace ONE fixes for v29

  • The Workspace ONE app will no longer force close after selecting "Done" from the lock screen notification.

  • If the headset is moved into a different Device Manager group during PIN selection, the headset display will no longer go to a black screen.

  • Guardian can now be adjusted in the headset even if the device has not completed enrollment.

Fix a known issue for Workspace ONE

If you're experiencing a known issue listed below for Workspace ONE, please reboot the headset:

  • Stuck on a loading screen after clicking Agree on the "Data Sharing" prompt after device enrollment.

  • Unable to launch an application after enrolling in Workspace ONE.

  • Stuck on a loading screen after the Workspace ONE app is relaunched before an internet connection is established.

  • Stuck on a black screen after choosing Yes on the "You will need to start over and re-enter your information if you cancel" prompt during device enrollment.

  • Stuck on a blank Workspace ONE screen after trying to launch the One Hub app from App Library while the app is already open.

  • Logging in fails or gets stuck after closing the login screen.

General fixes for all MDM

  • "Android Recovery" error is displayed in the headset during a device update after MDM authority was changed for the headset in Device Manager. If this happens, preform a factory reset by pressing the Vol- and Vol+ buttons to navigate the menu, highlight Factory Reset,and press the power button to select this option.

  • Using MDM on a private network that requires certificates instead of a SSID/password combination is possible but not supported. If you do attempt this please check with your Security/IT department to verify that the username is valid and has the correct level of permissions.

  • A headset may disappear from Device Manager when switching from a a third party MDM back to Oculus Device Manager during device provisioning. If this happens, use the Oculus for Business Android app to reprovision the device.

  • Backing out of the Setup Notifications screen after setting a PIN takes the user to the MDM home screen, not the start of the set PIN flow. If you need to set or reset the PIN of an MDM-managed device, use the MDM's web console.

  • MDM applications are not seen in the App Library. This can occur when a headset that is enrolled in MDM is moved to a group with Device Manager that has Sideloaded Apps disabled. If this happens, set Sideloaded Apps to enabled.

  • If Admin Mode is enabled a user will be able to launch apps before enrollment of the headset in MDM is complete.

MobileIron GO known issues

  • Quest 2 devices are listed as "Quest" in the Device Details of the MobileIron Go app.

  • During enrollment the lock screen notification text may appear very dark for entries other than "Don't show notifications". Please select "Don't show notifications."

  • In some situations the Status of a headset will not display "Setting Device Owner Failure" when MDM has been set to the wrong app. If you are having trouble setting up MDM, please check that you have linked the correct app in Device Manager on the Apps page.

  • The "Continue" button is not showing on the enrollment page of MobileIron Go. If this happens, use the joystick on the controller to scroll down.

Workspace ONE known issues

  • In some situations the headset PIN does not change when changed from the Workspace ONE web console. If this happens lock the headset from the web console then have the user put on the headset and unlock it. At that point it should start accepting a PIN change from the web console.

  • When moving a headset that is enrolled in WorkSpace ONE into and out of groups in Device Manager the device lock PIN can sometimes stop working. Use the WorkSpace ONE web console to change the device PIN of the headset.

  • After unenrolling the headset from Workspace ONE the headset display will be a black screen with three floating dots. If this happens, press the Oculus button.

  • In some situations the Status under Mobile Device Manager for a headset in Device Manager does not show as "Installed" after MDM has been assigned. If this happens try the following:

    • Reprovision the headset using the Device Setup app.

    • Refresh the Device Manager page to see if Status has changed.

    • Put on headset to make sure there isn't a prompt you need to click on to continue.

    • If the message for the Status mentions a failure or it still does not say Installed, set MDM Authority back to Oculus Device Manager. Then verify in the headset that the Oculus for Business operating system loads completely. Once Oculus Device Manager is verified as working, change MDM Authority to the third party MDM and try to enroll again.

  • In the latest build the Workspace ONE app panel automatically opens in dark mode. If this happens, you can change to light mode in Settings after device enrollment.

Oculus for Business June 2021 Release

Version 28.0 known issues

We're investigating the following issues and are working to resolve them in future updates:

    Known issues with work arounds

    • "Setup Incomplete" error showing during device provisioning. If this happens, wait a few hours to see if it goes away. If it doesn't:

      1. Factory reset the headset.

      2. When the device is turned off, press and hold the volume down and power buttons until you see a menu appear.

      3. Select the factory reset option.

      4. Once the device resets, put the headset on and connect to your available Wi-Fi connection.

      5. Once you connect to Wi-Fi the Oculus Introduction video will begin. During the video, your headset will reset and install the Enterprise software.

    • Home screen environment appears black if an app is closed after leaving and returning to Guardian area. If this happens, relaunch the closed app.

    • Second controller fails to pair when selecting "Next Controller" during controller pairing. If this happens, pair the second controller separately.

    • If the headset is left idle while casting and goes into sleep mode, screen may be black when casting resumes. If this happens, reboot the headset.

    • Sideloaded apps deleted from the headset do not show as deleted. If this happens, let the headset idle and then awaken it from sleep mode.

    • Apps removed from Device Manager still appear in the headset. If this happens, reboot the headset.

    • Switching from an app that supports hand tracking to an app that doesn't causes the "Switch to Hands" prompt to appear. If this happens, fully close both apps before relaunching the app that doesn't support hand tracking.

    Known issues with no current work around

    • Pausing Focus Overlay-enabled app shows an Oculus placeholder image on the pause panel instead of an in-app screenshot or thumbnail.

    • Drawing a large Guardian area causes the tool to function unexpectedly.

    • Apps installed in Device Manager appear in App Library instead of Unknown Sources.

    • Passthrough not displayed when pairing controllers if Guardian is disabled.

    • Hand Tracking tutorial audio does not play when tutorial is launched.

    • Apps with long names block the “Quit” button in-VR.