My reports
Submit feedback

VR

Investigation titles and descriptions are summarized by AI from Meta based on reports submitted by developers
0
XR Simulator Controller Connection Issue
Investigating
Issue
1 report
Created about a day ago
The Meta XR Simulator documentation lacks clear instructions on how to connect controllers, causing developers to struggle with setting up and using controllers within the simulator environment. Specifically, the documentation page for XR Simulator interaction does not adequately explain the controller connection process, leaving developers without guidance on this crucial aspect of simulator usage.
Add your report
Subscribe
Suggest an edit
Copy link
0
Hand Tracking Menu Access Issue with Palm-Up-Pinch Gesture
Investigating
Suggestion
1 report
Created 2 days ago
The palm-up-pinch gesture used to invoke the Quest system menu during hand tracking sessions is causing frequent accidental app exits. Users, especially inexperienced VR users, are unintentionally triggering the gesture or interacting with the Meta icon prompt, leading to application exits. The issue arises from the ease of triggering the gesture during normal hand movements. A feature request has been made to restore the wrist button as an alternative method for accessing the system menu, which would require more deliberate user intent and reduce unintended app exits in hand-tracking applications.
Add your report
Subscribe
Suggest an edit
Copy link
0
Private App Distribution Documentation Clarification
Investigating
Issue
1 report
Created 2 days ago
The documentation for private app distribution on Meta for Work and Meta for Education states that private apps do not require formal review. However, the developer dashboard still displays 'app submissions' options for private apps, and the app remains listed as 'draft' in release channels even after following the documented steps. The documentation is unclear on whether a submission is still required to distribute a private app despite the stated exemption from formal review, causing confusion and potential issues with app distribution.
Add your report
Subscribe
Suggest an edit
Copy link
0
Passthrough Not Displayed in MQDH Debug Window
Investigating
Issue
1 report
Created 3 days ago
The passthrough view fails to render or appear when accessing the debug interface through the Link Settings panel in Meta Quest Developer Hub (MQDH). This issue prevents developers from viewing passthrough output during debugging sessions, specifically within the Unity and Other categories.
Add your report
Subscribe
Suggest an edit
Copy link
0
Positive Feedback on Electronic Developer Distribution Agreement Documentation
Investigating
Issue
1 report
Created 3 days ago
The user provided positive feedback on the Electronic Developer Distribution Agreement documentation, confirming that it was helpful and provided the necessary information. No technical issues or problems were reported.
Add your report
Subscribe
Suggest an edit
Copy link
0
XR Space Discovery Fails on Quest 3 with Error Code -2
Investigating
Issue
1 report
Created 3 days ago
XR Space discovery is failing on Quest 3 devices with error code -2 returned from queryCompleteEvent->result on XR_TYPE_EVENT_DATA_SPACE_DISCOVERY_COMPLETE_META. This issue occurs frequently on devices deployed via Horizon Managed Services (HMS) with OS version 203 (5208318.3200.520) and Unity Editor 6.3.11f1, despite the USE_SCENE permission being granted and space setup being complete. The issue is less common or absent on developer devices not connected to HMS, suggesting an HMS-specific environmental factor is affecting space discovery functionality.
Add your report
Subscribe
Suggest an edit
Copy link
0
Android Device Setup Issue: Unable to Enable Developer Mode
Investigating
Issue
3 similar reports
Created 3 days ago
During Meta Quest development setup, a developer is unable to enable developer mode on their Android mobile device. Despite following all steps in the mobile device setup documentation, the developer mode toggle fails to activate or is inaccessible. This issue prevents the developer from proceeding with the device configuration required for Quest development.
Add your report
Subscribe
Suggest an edit
Copy link
0
Positive PC SDK Documentation Feedback
Investigating
Issue
1 report
Created 5 days ago
The user provided positive feedback for the PC SDK introduction page, rating the documentation as "Helpful". No specific issues or improvement suggestions were provided, indicating that the user found the documentation satisfactory and sufficient for their needs.
Add your report
Subscribe
Suggest an edit
Copy link
0
libovrplatformloader.so Not 16KB-Aligned for arm64 Architecture
Investigating
Issue
1 report
Created 6 days ago
The libovrplatformloader.so native library has a compatibility issue on Android devices that use 16KB memory page sizes, specifically those with arm64 architecture. The library currently is not 16KB-aligned, which causes issues on newer ARM64 Android devices that enforce 16KB page alignment requirements. To resolve this, the library needs to be recompiled with 16KB ELF segment alignment.
Add your report
Subscribe
Suggest an edit
Copy link
0
OVROverlayCanvas Flickering Issue in Quest OS 2.4
Investigating
Issue
1 report
Created 8 days ago
After updating to Quest OS 2.4, the use of OVROverlayCanvas causes black screen flickering and framerate drops. The flickering is only visible on the headset and not in casts or video recordings. The issue is confirmed to be related to OVROverlayCanvas usage, as builds without it do not exhibit the problem. The flickering worsens when the Oculus system menu is opened, suggesting the issue intensifies with additional overlay layers. This regression was introduced with OS version 2.4.
Add your report
Subscribe
Suggest an edit
Copy link
Load more
Reset to default

Sort

Type

Platform

Category

Status