Questions & Discussions

Hi, I'm working on a VR app for a museum exhibition with Unreal Engine 5.6 on Quest 3. The experience is passive, no controllers needed, so I'm trying to disable Guardian completely.I found that adding CONTEXTUAL_BOUNDARYLESS_APP to the manifest worked fine on Quest 2 with UE5.0, but on Quest 3 the app just freezes on the Unreal splash screen and never starts. If I remove that line everything works again.I also tried the boundaryless settings inside the Meta XR Plugin. The headset shows "Boundary may be inactive in this app" but then immediately asks the user to set up a stationary boundary anyway.Has anyone managed to fully suppress Guardian on Quest 3 with UE5.6? Is that manifest flag deprecated on Quest 3? Any alternative approach via Blueprint or C++?Thanks!

Hello!I have been trying to get my developer account activated without success. It shows the following error:I have set a credit/debit card on my FB account as well as activated 2-Factor but have not succeeded on getting it working yet.

We are experiencing an issue where the pages_read_engagement permission is correctly granted (Advanced Access) and confirmed present in our Page Access Token scopes, yet all engagement-related endpoints return error #10.App info:App Mode: LiveGraph API version tested: v24.0 and v21.0 (same result)Token verification via /debug_token:{ "data": { "app_id": "....", "type": "PAGE", "is_valid": true, "scopes": [ "pages_show_list", "business_management", "instagram_basic", "instagram_manage_insights", "instagram_content_publish", "pages_read_engagement", "pages_manage_posts", "public_profile" ] } }As shown above, pages_read_engagement is explicitly listed in the token scopes.Calls that FAIL (error #10):GET /{page_id}/posts?fields=id,likes.summary(true) GET /{post_id}/likes?summary=true GET /{post_id}/comments?summary=trueError response:{ "error": { "message": "(#10) This endpoint requires the 'pages_read_engagement' permission or the 'Page Public Content Access' feature.", "type": "OAuthExcep

I'm using the AppDictationExperience component from the Voice SDK in Unity and am trying to play a build on the Quest 2. When I call Activate on the AppDictationExperience component the microphone only starts correctly if the app doesn't have microphone permission when the app starts and asks for permission. If the app already has microphone permission I get an OnMicStartedListening event but the microphone isn't actually recording, if I check Microphone.IsRecording it returns false.

Hi everyone,I’m seeking help regarding a change in the Meta Horizon Link software (Windows) that has disrupted my MR development workflow.The Issue: Previously, I used the "Enable Passthrough" toggle within the Settings to test MR features in Unity. When enabled, I could see the passthrough background in my Quest 3 while in Unity Play mode.However, in the current version (83.0.0.330.349), the "Beta" tab has completely disappeared from the Settings menu, and I can no longer find the Passthrough toggle anywhere else. Consequently, passthrough is not functioning when I press Play in Unity.My Setup & What I've Tried:Meta Horizon Link Version: 83.0.0.330.349Connection: Wired Link (USB-C)Headset: Meta Quest 3OpenXR Runtime: I have already confirmed that "Meta Quest Link" is set as the active OpenXR Runtime in the General tab.Development Tool: UnityQuestions:Is the "Beta" tab being deprecated or moved in version 83?Where can I now find the setting to enable Passthrough over Link for Unity

Pullin my hair out here - I have the V81 simulator installed on Windows 11. Unity 6.2.10f1. I enable the simulator but the window does not appear. Any suggestions on what to check?My goal is to use the headset in editor and the simulator in the Multiplayer play mode. When using XRIT and the unity xr simulator in another project, this type setup works quite well . I can have 3 virtual players using  the simulator and I can use the actual headset over the pc link in the editor. I want to replicate this type of setup but using the Meta XR Simulator instead.  

Hi all, We've been experiencing a sudden and persistent Error 2002 ("Failed to fetch IAP purchases") since March 27, 2026. The error occurs when calling iap.get_viewer_purchases via the Oculus Platform SDK, and it's affecting subscription status checks at app launch. Environment:Meta XR Platform SDK: 77.0.0- Unity: 6000.0.68- Affected devices: Meta Quest 3S, Quest 3, Quest 2 (confirmed on all tested devices)- OS: Android 14Impact:Approximately 1/3 to 1/2 of our daily active users are encountering this error. The issue began on March 27 with no app update or any change to our IAP configuration in the Developer Dashboard on our side. Issue summary:Since March 27, calls to get_viewer_purchases consistently return error code 2002. The error originates in PurchaseFetcherImpl.getAppGroupingId() and propagates up through the IAP service layer: Error AppManagerClient at horizon.platform.service.iap.PurchaseFetcherImpl.getAppGroupingId(:23)Error AppManagerClient at horizon.p

Hi, I'm repairing a Quest 2. The headset boots to the Meta logo then shows a flashing grey screen.ADB sideload mode works but the OS is corrupted.I need the official Quest 2 OTA recovery package to reinstall the firmware through adb sideload.Serial number: 1WMHHB6APM2292Model: KW49CM (128GB)Where can i find the correct OTA zip?Please send the correct signed update zip 

Im a 12 year old who has just made a VR game with unity and want to upload to applab, my APK is working and there is no errors uploading and the release channel is ALPHA, but i need to verify my organization with either legal documents or a government issued ID, can anyone help me upload?

I recently upgraded to the version 1.81.0 of MetaXRInteraction on the Oculus Unreal engine fork. Version 5.6.1And the controller components don't have ray visuals when interacting with menus. The functionality works, I can click, and elements change when hovered, but it's hard to aim.What's weird, is that the ISDKHand components, do have proper ray visuals. (Expect for the right reticle not getting blue when pinching)I am not sure what is broken, or how to get this working. All parameters are defaults. And I only turn off/on the Ray and Grab components (for both ISDK Hands and ISDK Controllers) when the user selects a hand preference in settings using the Set Active function. Video demonstrating the issue.https://drive.google.com/file/d/1GZB-dCXpaxryZP92I9jXAnZO34Lg9WHP/view?usp=sharingThanks!

As a Web/Multimedia Developer (B.A. Comm), I am formally auditing the persistent UI limitations in OS 2.1. Meta continues to treat the Global Navigation Bar and System Menus as a static kiosk interface.​The AOSP / Java RealityThe Navigator is a View group within a Java-based AOSP (Android Open Source Project) framework. There is zero architectural excuse for failing to implement transparency (alpha) and color customization. If the community can port Quake to HTML5, Meta's engineering team can certainly implement a basic slider for the UI layer.​The Sideloading ParadoxThe claim that UI customization is "too complex" for users is logically inconsistent. A significant portion of this community is already using ADB (Android Debug Bridge) and Sideloading to bypass these restrictions. If a user has the technical literacy to sideload an APK, they are more than capable of using a native hex-code color picker or a transparency toggle.​Figure-Ground and AccessibilityBy hard-coding Elevation and

Hi, I'm experiencing an issue where remote avatars are showing as a default/purple fallback instead of loading from CDN. This worked correctly a few days ago with no code changes on my end.Setup:Meta Avatars SDK 40.0.1Unity 2022.3.62f2Meta Quest 3 (system version 14.0)Two devices, both logged into separate Meta accounts, both are organization adminsApp is sideloaded via APKUsing SampleAvatarEntity with Load User From CDN enabled and a hardcoded CDN User IDIssue: Remote avatar shows as default fallback immediately on launch. No CDN-related logs appear in Android Logcat at all.When I tested the Graph API directly:https://graph.oculus.com/{USER_ID}?fields=avatar_spec&access_token={TOKEN}I received this error:json{ "error": { "message": "Tried accessing nonexisting field (avatar_spec)", "type": "OCApiException", "code": 100 } }What I've verified:App ID and User ID are correctBoth accounts are organization adminsReverting to previous builds does not fix the issueProblem occurs on both d

Hi everyone,I am currently developing a VR application using Unity 6000.2.10f1 and Meta Avatars SDK v40 (Style 2).My goal is to render the remote avatars as "Half Body" (hide the legs), similar to the old Horizon style.The Problem:Since the avatars are generated as a single Combined Mesh (LOD00_combined_geometry), I cannot simply disable a "Legs" GameObject.What I have tried:1. Modified Manifestation Flags:I tried setting CAPI.ovrAvatar2EntityManifestationFlags.Half in the Render or Start methods of my OvrAvatarEntity. However, the avatar still renders with full legs.2. Bone Scaling (Critical Joints):I added LeftLegProximal and RightLegProximal to the Critical Joints list and set their local Scale to Vector3.zero via script upon the OnUserAvatarLoadedEvent.- Result: In the Unity Inspector/Debugger, the bone scale is indeed (0, 0, 0). However, in the Game View, the legs are still fully visible.- I suspect this is because the Native Plugin / GPU Skinning ignores the Unity Transform chang

I try loading up games (Gorilla tag for example) and it’s gives me an attestation error. I don’t what this means all I know it that it has something to do with security.

To the Meta Design Team, you are making your device worse by trying to be someone else. Meta was the leader because you were the ones who actually figured out how to make standalone VR functional and accessible in the first place. For you to throw away the very leadership you built just to become a knock-off version of Apple is a total failure of vision. You didn’t need to reinvent the wheel, you just needed to polish it. Instead, you’ve scrapped a great, functional interface for a filtered version of the Vision Pro. By forcing the Navigator into a rigid, head-locked position, you’ve sacrificed user sovereignty for a spatial look that you don't even have the eye-tracking hardware to support on your current mainstream headsets. Even if your next device has that hardware, the millions of people using your hardware right now shouldn't be forced into a "look-to-lock" logic that makes the system feel broken. Taking away the ability to freely grab and park windows, forcing us to re-center ou

Anyone else have problems implementing the Age Group API for Mixed Ages? I went through the course and it says we just have to call the API in our game (which I did), yet I'm still getting this compliance item as TODO in the dashboard, and my game was removed from the store! People who want to install the game are messaging me saying they can't find it on the store.I'm wondering if anyone else has implemented the Age Group API? Should it clear up automatically if the call is working correctly? Maybe this is a common error that somebody else dealt with, or maybe I'm missing something silly. I've attached some screenshots of my Unity Code, the log in my build, the course completion as well as the violation.Maybe this is Meta's way to push us not to have a mixed age app, and set the age to 13+ only?  I really wish there was more transparency so I could know what I have to do.  

Unity colocation build with MRUK, getting this error in Logcat and "host can't share the room with group xx-xx.." on immersive debugger...User ID  and User profile active in dashboard, device has spatial permission enabled, project uploaded to alpha channel, my own user invited as tester, Keystore signed, tried with 4 different WIFI, no LLM has a clue...was working before upload alpha,What else should I check?

Hi, I am trying to use the Unity-SpaceSharing sample: https://github.com/oculus-samples/Unity-SpaceSharingWhat I’m seeing in the logs is:Repeated local anchor read failures with error -60001Then shareSpatialEntity failed with GraphQLError code=2128008A server message saying some anchors could not be found in the cloud by IDAlso, Mesh upload through cloudAnchorService is not supportedMy questions are: Is FailureOperationFailed (-1006) usually caused by anchors not being uploaded or not being available in the cloud yet?Is there a known issue in the sample where sharing a manually collected anchor list can include unsupported scene or mesh anchors?

It looks like you shifted from "headpos" to "camera.main" in everything.But... _cameraAccess.GetCameraPose()  is still using HeadPos which... was somewhere near my chest?To reproduce:Take CameraKit demonstration for QR codes.  Run with 83.0.4 in an unmapped space.Works fine, the green quad covers/is close to the QR code.Now copy/paste the code/objects into a newly set up 6003.9f1 project with MRUK85.0.0.  Run again in an unmapped space.  The QR is off.  The green quad is someplace else.  if you put tracers and debug flavor in, you will find that -- at least Y is ~34 cm off (look at CP)...Debug Spice:    private static Ray BuildWorldRay(QrCodeResult result, Vector2 uv)    {        var viewport = ToViewport(uv);        var intrinsics = result.Intrinsics;        var sensorResolution = (Vector2)intrinsics.SensorResolution;        var currentResolution = (Vector2

I created a Meta Quest Creator portfolio called Arnou Limits and completed identity verification. However, in Media Studio the Upload Media page only shows the Quill Uploader, and there is no option to upload 360/180 MP4 video.  Even if I change the file type - Meta ingestion still won't accept my mp4 videos. Followed the correct 360 requirements and am only trying to test a 1 minuet video. Any help will be much appreciated   

Hi everyone,I am an architect and urban planner, developing VR/MR projects in my spare time. I’m currently working on a native Quest 3 application to view Gaussian Splats for highly detailed virtual project tours.My Goal:Render native Gaussian Splatting (3DGS) on Quest 3 (Standalone).Synchronize the splat position with the real world for a seamless transition from Mixed Reality (MR) to Virtual Reality (VR) with a skybox.Targeting a minimum of 150k splats with stable performance.Previous Attempts: I initially used Unity with the Aras/Ninja implementations. While it works perfectly via Oculus Link (PCVR), it’s not viable for my needs because:PC Builds don't support the specific MR features I need for this project.The Android build (standalone) performance is extremely poor, even with optimized settings and a small 50k splat PLY file (unusable frame rates).Current Issue with Meta Spatial SDK: I’ve switched to the Meta Spatial SDK (Packages v0.9.2) to leverage the new native splat support

Hi everyone,I'm struggling with a very frustrating issue previewing my Unity Scene on my Meta Quest 3, and after a lot of troubleshooting I'm out of ideas. Hoping someone here has seen the same pattern.When I hit Play in Unity with the Quest 3 as the PC-VR headset, the preview is laggy, stutters heavily, and runs at a very low frame rate, sometimes so bad it's impossible to test anything. Sometimes, even the Quest Link menu is already very laggy. The strange part is that it's not consistent:- Sometimes the preview starts perfectly fine.- Then if the HMD goes inactive (I take it off while editing in Unity for a bit) and I put it back on, the lag comes back.- Sometimes it's bad from the very first Play.- Occasionally it just works for a whole session.What I've already ruled out / tried- Air Link / network: I initially thought it was bandwidth, but my WiFi is over 300 Mbps, and my PC is on 1 Gbps Ethernet to the router. Hard to see how that's the bottleneck.- **Link Cable:** Switching to

Hi everyone,I submitted my business verification for my app over 10 days ago and it's still showing "In Review" with no updates.The pending verification is blocking my App Review submission as I cannot complete the required API test calls for Instagram permissions until verification is approved.I've tried the bug reporter but was told individual cases can't be handled there.Has anyone found a way to escalate a stuck business verification? Any help appreciated.Thank you

"This page isn't available at the moment.This may be because of a technical error that we're working to fix. Please try reloading this page."this is the error message that occurs while editing date of birth. please suggest a solution for this. 

Hi,I’m working with Unity + Meta XR SDK and using Meta Quest 3 via Meta Link (PC VR / OpenXR runtime).I would like to retrieve the battery percentage of the headset and controllers while running in PC VR mode (Link/Air Link).What I’ve tried:- SystemInfo.batteryLevel returns PC/laptop battery, not headset- OVRPlugin.batteryLevel marked as obsolete, and returns 0 when running via Link- OVRManager.batteryLevel same behavior as OVRPluginHowever, the Meta Quest Link desktop and mobile app itself are able to display headset and controller battery information, so the data clearly exists in the system.Is there any supported way in Meta XR SDK / OpenXR / Oculus PC SDK to access:- Headset battery percentage- Controller battery level…while running in PC VR mode (Link/Air Link)? Or is this data intentionally not exposed to third-party applications on the SDK side? Any clarification from Meta or experienced XR developers will be appreciated.Thanks!