Developer Forum

My developer account shows 'You cannot access this service' after a personal account security lock on July 31. Account is now unlocked, phone re-added, but developer access still blocked. The disputes page at account_status/disputes/ loads blank."

Hi everyone,our studio is developing a Unity B2B application for Meta Quest 3 and Quest 3S using the Meta XR SDK.The application uses:Hand Tracking only, with no controllersPassthroughMultiplayerOVRManager with Tracking Origin Type = Floor LevelOur application needs to place several virtual objects directly on the physical floor of the room.We are experiencing an issue that we have not been able to solve: in some sessions, when the application starts, the floor level reported by the headset is incorrect. The error is significant, approximately 0.5 meters, so virtual objects that should appear on the physical floor are instead positioned noticeably above or below it.What makes the issue difficult to understand is that it is not consistent.When the problem occurs, restarting the application usually does not help: multiple sessions started around the same time tend to report the same incorrect floor level. However, at other times, using the same headset in the same physical room

GPU clocks pinned, per-frame GPU cost flat; coincides with tracking/localization activity resuming after session start; exiting and re-entering the session resets the cycle. Environment----------- - **Device:** Meta Quest Pro- **OS:** Horizon OS v207, Android build UP1A.231005.007.A1- **Browser:** Meta Quest Browser 149.1.0.10.52.1018773329- **Content:** WebXR immersive-vr session (three.js r185, WebGL2), OVR_multiview2\stereo scene pass into a single-colour-attachment offscreen target, 72 Hz session,\framebufferScaleFactor 0.75. App GPU cost ≈ 15 ms/frame at the test station (heavy\scene, deliberately chosen --- the effect is easiest to see when frames sit near budget).- Repro'd with eye tracking, natural facial expressions, and hand/body tracking **disabled**,\and with the developer-mode boundary **disabled** --- the behaviour is unchanged. Summary------- For the first ~20--50 s of an immersive session the browser produces XR frames at the rate\the GPU allows (~55

Starting in June, two apps of ours that have been on the Meta store for two years suddenly started forcing a popup to turn on wifi, even though the apps were designed to run offline, and had been doing so without incident until this started. Is anyone else experiencing this? Meta support is pretty much nonexistent now apparently.

I'm unable to connect my device to my organisation via work.meta.com/devices, as it does not recognise my registered email. There are no spelling mistakes, I've recieved emails from meta to this address, and this address is connected to my organisation.

Library/PackageCache/com.meta.xr.sdk.core@c0efcbf2ba70/Scripts/OVRManager.cs:2761

Hello I need help big times.My Meta Account is in Good Standing with no restrictions in Accounts Center > Account Status. However, the Meta Horizon mobile app, when I try to play anybgames it shows: "Your account is restricted at the moment. Due to several violations against our Code of Conduct for Virtual Experiences policy, you can't access games in Meta Horizon."I did not receive any notification about getting my account restricted neither I have received any emails.There is no restriction listed, so I have no option to appeal. I have already:Logged out of all devices via the account center Reinstalled the appConfirmed I do not own a VR headset and have never used Horizon Worlds. I have contacted Meta but they cant resolve the issue apparently.  Çan someone help please? 

Hi everyone,My Meta developer account is restricted and showing account_status/error page.Details:- App Name: Tia (E-commerce)- App ID: 9951181664973l0I have already:- Contacted Meta support via chat- Received a phone call from Meta Pro Team- Submitted multiple support ticketsBut the issue is still not resolved.Meta support keeps sending me to business-support-home which has no appeal option for developer restrictions.Has anyone successfully resolved this issue? Any help is appreciated.

Feature Request: Bring Back the Original Horizon Home lobby. I really miss the original Horizon Home lobby. It made putting on my Quest feel like stepping into a living virtual world instead of opening an app launcher. I loved being able to enter a shared social space, talk to random people, attend concerts, explore events, and decide what I wanted to do. It felt natural, immersive, and made VR feel exciting every time I put on my headset. Now Horizon mostly feels like a place where I launch games by myself. The social experience that made VR special is gone, and because of that, I’ve stopped using Horizon Worlds. If you bring the original lobby back, please don’t just restore it. Make it even better, add more live events, concerts, community activities, and a wider variety of games and experiences to discover directly from the lobby. Create interactive spaces where people can meet, explore, and participate together. A more immersive, ever evolving lobby would make people want to spend

Hello, My name is Martine Bordeleau, PhD, and I am a researcher in Canada. My team is planning to use Meta Quest headsets with older adults, some of whom may have implanted cardiac pacemakers or implantable cardioverter-defibrillators (ICDs). While reviewing the Meta Quest 2 and Meta Quest 3 Health & Safety Guides, I noticed the recommendation that users with implanted medical devices should consult their physician or the device manufacturer because the headset contains magnets and emits electromagnetic fields: To better understand the rationale behind this recommendation, I conducted a review of the scientific literature. To date, I have not identified any published study demonstrating that a VR headset causes electromagnetic interference with a pacemaker. The only published study I identified that included participants with implanted cardiac devices is the study by Jóźwik et al. (2021) (attached). The authors reported that: "Some patients raised conc

My Quest 2 completes a factory reset successfully. The setup process completes and the headset reaches the Home environment.The issue is only with the Home environment/system interface. When I press the Meta button, the menu does not open normally. The interface appears to pop out/expand incorrectly and the Home environment behaves as if the system UI is corrupted.I have repeated the factory reset and the same issue happens again.The headset was previously enrolled in an organization setup, so I am wondering if there could be a conflict between organization enrollment and the normal Quest Home environment.Has anyone experienced this issue or know the correct way to completely remove organization configuration and restore the normal Quest Home environment?

A few people in the "what should we polish next" thread brought up wanting new machines, so wanted to pull back the curtain on how that actually happens.Every cabinet starts as one of roughly 10-15 rough concepts, and most don't survive the first review usually because the core hook doesn't land within a few seconds of standing in front of it, which is the bar we hold ourselves to in VR specifically. The ideas that do survive get built as an unstyled, playable mockup first. No art, no polish just the mechanic, to make sure it's actually fun before we spend time making it look good.This doesn't answer whether we're adding new cabinets vs. going deeper on existing ones that's still genuinely open, see the polish thread but hopefully it's useful context either way.

The download progress stops at 10-12GB.DEVELOPERS, WHEN WILL YOU FIX THIS?

I just have returned my AI Ray-Ban glasses because issue with features I have like a Meta what I’m looking at or hi meta what is the population of Japan, for example and keep saying this future is not available in your region even I am living in United States couple months ago I traveled to France and Egypt and it was working very good and a lot of people were excited about it. I give them a recommendation to buy it , but I feel bad now and I return it. Because few features is not working anymore and it’s very frustrationdo have eny update?

Wanted to share some context on where Arcade Mania actually came from, since a few of you have asked.It didn't start as "let's build a VR game" — it started as missing the specific feeling of a real arcade: standing in front of a cabinet, other people nearby, the game as a physical object rather than a menu. That's a feeling flat-screen games can't reproduce, and we weren't convinced VR could either until we tested it directly.The first build was intentionally small: one machine, one room, no art, built purely to test whether "standing in front of it" felt physical and present rather than like navigating a UI. Once that held up, we started building out the rest of the game around that core feeling. Open question for the community: is there anything about a real, physical arcade that you feel like we (or VR games in general) still haven't captured? That's genuinely useful for us to hear.

Hey everyone, We're QuantumArcadia, a small studio based in India. We recentlypublished Arcade Mania on the Quest Store — a collection ofskill-based mini-games built for VR, arcade-style. We're still learning what resonates with the Quest community, so Iwanted to share it here and get honest feedback — what works, whatdoesn't, anything that feels off in the first 5 minutes. You can check it out on the Quest Store here:https://www.meta.com/en-gb/experiences/arcade-mania/1181756821683806/ Happy to answer questions about how we built it, tech stack, orlessons learned so far. Would really appreciate any thoughts!

Hello, I am working on a vulkan app. I tried taking capture on an oculus quest pro using the latest v68.16 version. I am using raw vulkan code and I think the issue is on the libVkLayer_GLES_RenderDoc.so side. I am using vulkan memory allocator for all my allocations:tried multiple scenarios, this is one example of callstack: Essentially what happens, is either vkBindBufferMemory or vkBindBufferMemory2 is intercepted by the renderdoc validation layer. The validation layer tried to inspect my buffer pointer for replayability I suppose. It ends up calling CreateAddressRange which is a nullptr.   I think everything boils down to VK_KHR_buffer_device_address, it does not appear to be supported by either my quest pro or quest3. But even if not supported, it looks like renderdoc is using some of its feature such as vkGetBufferDeviceAddress or vkGetBufferOpaqueCaptureAddress and fails to do so. Is there any way of avoiding renderdoc to use this extension?   I ran a similar app on Qu

Hi guys, i am a student pilot and like to take pictures while in flight with my meta 2 glasses. I also like to identify towns from above but my glasses cannot accomplosh that without internet connection. I was wandering...if the GPS of my Phone is on and I have download the offline maps for Google maps, why should not be possibile.for my glasses interpolate gps/maps data to give the location and tell what i am looking?!?Any idea would be appretiated 

I’m looking for help regarding an issue with Meta XR Simulator on Windows 11.I’ve installed Meta XR Simulator (v83), but it continuously shows an error saying “Windows App Runtime 1.5 or higher is required”, even though Windows App Runtime versions 1.1 through 1.8 are already installed and working on my system. Meta XR Simulator seems unable to detect the expected 1.5 package structure or registry/runtime signals.If anyone has encountered this issue or found a workaround (other than downgrading to v82), I’d really appreciate your insights. Thanks in advance.

I’ve added the first version of the multiplayer mode.At the moment, I don’t have access to multiple Meta Quest headsets to fully test real headset-to-headset gameplay. I’ve tested the online flow using a bot, and it appears to work correctly, but I’d really appreciate feedback from users who can try it between multiple headsets.If you test multiplayer, please let me know whether matchmaking, synchronization, player movement, and race results work correctly. https://www.meta.com/es-es/experiences/ufo-snowboard/1178822797740806/?require_login=true

The Start program team will be on the ground at Gamescom this year—and we’d love to connect with you in person. We’re bringing Launch and Growth Consulting support for face-to-face meetings throughout the week. Whether you’re preparing for a release or looking to level up your growth strategy, this is a great opportunity to get hands-on, tailored support while we’re all in the same place. What’s available: 🚀 Launch consultations 📊 Growth analytics consultations 📅 Meetings available Tuesday, Wednesday, and Thursday of Gamescom week We’re also hosting a social event on Wednesday, August 26 6:00–9:00 p.m.—let us know if you’d be interested! 👉 Sign up here: https://forms.gle/oJSJjLt9aeffeRAK6 Looking forward to seeing some of you in Cologne!

We isolated a reproducible browser/driver-level hang on Meta Quest Browser and want to share it with other WebXR developers (also filed via the developer Feedback Center). Symptom: entering an immersive WebXR session permanently hangs (rAF stops within ~2 seconds, no webglcontextlost event, no GPU process recovery; the headset OS stays responsive) when a WebGL2 page combines ALL THREE of:antialias: true on the WebGL2 context (MSAA)2. A per-frame shadow map pass (rendering into a depth texture every frame, e.g. three.js shadowMap)3. The Spark 3D Gaussian Splatting renderer (sparkjs.dev), which performs out-of-band GPU work between frames and fence-based async readbacks (fenceSync + getBufferSubData) for splat sortingRemoving any ONE of the three avoids the hang. Baking the shadow map once (three.js: shadowMap.autoUpdate = false) instead of rendering it every frame also avoids it - that is the workaround we shipped. Environment: Quest 3, Meta Quest Browser (latest as of July 20

Ever since I updated to v78, my devices go to sleep in 1 minute.  I'm on v79 now and this persists.  I have the "power" settings so that it is supposed to sleep in 4 hours, but they seem to have no effect.  I also have my presence sensor disabled (as well as having tape over it).This is driving me crazy because if I set my headset down, I have 60 seconds to debug before it turns off and suspends my title, then when I pick it up, I have to choose a profile again before I can continue.  Meta: how do I disable this?I used to be able to keep my devices awake and running my app for HOURS, through many iterations of debugging.  I try to drive my app through automation as much as possible, and when I am debugging multiplayer, I would be in the habit of running the app on both headsets via ADB and driving most of the interactions through APIs so I don't have to juggle headsets.  This is now impossible because in 60 seconds, the device goes to sleep.  I'm

Hi everyone, I'm working on an MR project in Unreal Engine 5.7 using Meta Quest 3 with a PCVR offline setup (Quest Link via USB). I want to place virtual objects at fixed real-world positions, so I'm trying to use MRUK's LoadSceneFromDeviceAsync() along with UMRUKAnchorActorSpawner. However, LoadSceneFromDeviceAsync() is returning false and I'm unable to load the scene.Things I have already checked:1. Requested com.oculus.permission.USE_SCENE and com.oculus.permission.USE_ANCHOR_API2. Completed Space Setup on Quest 33. Spatial anchors & scene support enabled in project settings.4. Share spatial over Link is enabled in Meta Horizon link.Has anyone successfully used MRUK Scene API with Quest Link/PCVR? Is there any additional setting required for LoadSceneFromDeviceAsync() to work?Any help would be appreciated. Thanks!

Hi, could someone at Meta look into how subscriptions are surfaced to users? I know there's a grey "Choose subscription" button, and from inside my app I can open the Meta Quest store page, but I still regularly get messages from players saying they can't find how to subscribe or don't know how to subscribe. My Meta Quest app is Slice Art Engine.