VR

Investigation titles and descriptions are summarized by AI from Meta based on reports submitted by developers

Search VR investigations

Voice SDK Mic Initialization Failure After Pre-Granted Permission

Expected behavior

Issue

1 report

Created 2 days ago

The Voice SDK's AppDictationExperience microphone fails to record on Quest 2 when the app already has microphone permission at launch. Specifically, calling Activate on AppDictationExperience triggers the OnMicStartedListening event, but Microphone.IsRecording returns false, indicating that the microphone is not actually recording. This issue only occurs when microphone permission was previously granted; if the app lacks permission at startup and requests it, the microphone initializes and records correctly. This suggests a race condition or initialization order issue in the Voice SDK when permissions are pre-granted.

Add your report

Suggest an edit

Copy link

Intermittent Invalid Data from Users.getAccessToken

Investigating

Issue

1 report

Created 2 days ago

The Users.getAccessToken() method in com.meta.horizon.platform.ovr.requests occasionally returns an error response with code 2006 and message "User access token is not available." instead of the expected user token. This issue occurs sporadically but can persist repeatedly for affected users once it starts. No specific reproduction steps or environmental triggers have been identified.

Add your report

Suggest an edit

Copy link

MQDH APK Upload Issue with Signed Distribution Contract

Investigating

Issue

1 report

Created 2 days ago

The Meta Quest Developer Hub (MQDH) is blocking APK uploads despite the Developer Distribution Agreement having been signed multiple times. The system prompts to accept the agreement again, directing organization admins to the legal documents page, but the signing status is not recognized. This issue occurs even though the developer has successfully uploaded builds in the past, suggesting a problem with agreement status synchronization or validation in the MQDH upload flow.

Add your report

Suggest an edit

Copy link

Quest 3 Headset Pairing Issue with Meta Quest Developer Hub

Fix complete

Issue

1 report

Created 5 days ago

The Meta Quest Developer Hub (MQDH) fails to pair with a specific Quest 3 headset, displaying an account mismatch error, despite both being logged into the same managed account. This issue is device-specific, as pairing succeeds with a different Quest 3 headset under the same account. The error occurs during the MQDH-to-headset connection process when attempting to establish a developer pairing.

Add your report

Suggest an edit

Copy link

Horizon Link v85/v201 PCVR Regression

Investigating

Issue

1 report

Created 5 days ago

A critical regression in Meta Horizon Link v85 and later (including v201) causes issues with Unity Editor and PCVR builds when using Body Tracking and Character Retargeter. Symptoms include Unity Editor crashes when entering Play Mode with a headset connected, black screens or exiting VR sessions in standalone PCVR builds, non-functional Body Tracking, and Character Retargeter avatars failing to initialize. This issue occurs in both production projects and minimal isolated Unity projects, affects both Link and Air Link connections, and is reproducible across multiple machines without any code, scene, hardware, USB cable, or driver changes, solely correlating with the Horizon Link update.

Add your report

Suggest an edit

Copy link

Unity 6000.4.4f1 Export Failure with Oculus Integration SDK and OpenXR

Investigating

Issue

1 report

Created 5 days ago

When using the Oculus Integration SDK with the OpenXR backend in Unity 6000.4.4f1, a build failure occurs due to conflicts between the Interaction SDK and OVRPlugin components. This issue prevents the project from being exported or built, resulting in a complete export failure rather than a runtime error. The conflict specifically arises from the combination of these components, hindering the export process entirely.

Add your report

Suggest an edit

Copy link

Device Name Modification Fails with Meta Quest 3 Connected to MQDH

Investigating

Issue

1 report

Created 8 days ago

The issue is that the device name for a Meta Quest 3 cannot be changed when the device is connected to the Meta Quest Developer Hub (MQDH). Despite an active connection between the headset and MQDH, the functionality to modify the device name fails or is inaccessible. This issue is categorized under Web and Device Actions, indicating a potential problem with either the web interface of MQDH or the device management actions performed through the hub.

Add your report

Suggest an edit

Copy link

Capsense Hand Poses Issue with PC Link

Investigating

Issue

1 report

Created 8 days ago

The ControllerDrivenHandPoses sample scene from Meta XR Core SDK fails to render Capsense hand poses correctly when running via PC Link. The issue is specific to Link playback and does not occur in standalone builds on device. The problem was tested with Unity 6000.4.0f1 and Meta XR Core SDK 201.0.0, and it reproduces with both OpenXR and Oculus plugins.

Add your report

Suggest an edit

Copy link

Installed Apps Not Visible in Device Manager

Investigating

Issue

1 report

Created 9 days ago

Installed apps are not appearing in the Apps section of the Device Manager, preventing visibility and management of installed applications through the expected UI location. This issue affects the Web and Device Actions categories, indicating a problem with either the device management interface or the app installation process. Specifically, apps that have been installed on the device fail to display in the device management interface, making it difficult to manage installed applications.

Add your report

Suggest an edit

Copy link

Quest 1 Pairing Failure Across Multiple Setup Methods

Investigating

Issue

3 similar reports

Created 9 days ago

The user's Quest 1 device is experiencing persistent pairing failures across multiple setup methods, including the Meta Quest mobile app on iPhone and Meta Quest Developer Hub (MQDH) on both PC and Mac. When using the mobile app, the 6-digit pairing code never successfully connects. In MQDH, setup stalls at step 1 of 2 on the headset, displaying "Finish setup on Meta Quest app" while the app requests a code that only appears when the headset is unplugged. Additionally, MQDH setup reaches near-completion but hangs indefinitely on "Reconnecting... this may take a minute." Factory resets have been attempted but have not resolved the issue. The device is a third-party purchased Quest 1.

Add your report

Suggest an edit

Copy link

VR

Sort

Type

Platform

Category

Status