RequestSharedAnchors: Failed with result code 11
I'm building a multiplayer app in Unreal Engine targeting Meta Quest 3 and utilizing shared spatial anchors. I'm trying to request shared spatial anchors by calling GetSharedAnchorsAsync(). I provide a GroupUUID and the anchors UUIDs that I previously saved in the cloud and shared via ShareAnchorsAsync(). However I'm getting the error: RequestSharedAnchors: Failed with result code 11. The error code is tied to the error: Failure_ErrorLimitReached. Here is my setup: -The Quest is logged into the same developer account, which owns the organization which owns the app - The headset is in developer mode - Enhanced Spatial Services are enabled - anchor_persistence_cloud_anchor_service_enabled: true confirmed in logcat - Data Use Checkup (DUC) completed – User ID and User Profile access approved - The organization is verified - Build uploaded to a release channel - The release channel has a test user assigned – the same admin developer account, also used for organization verification The ShareAnchorsAsync call completes with XR_SUCCESS. If maybe this helps, I also found following line in logcat: xr_cloud_anchor_service: discoverSpatialEntities Failed with error: networking::GraphQLError: code=2128025, fb_traceid=EhAbjwCqMot Can anyone please explain to me the cause for error with result code 11? How to setup the sharing + requesting spatial anchors correctly? What am I missing here? I work in c++.
Shared Mode, Browser app access?
I have a need to allow my Shared Mode headsets access to the Browser app. Support told me this was currently not an option. Please allow this app to be added to the managed apps page on the work.meta.com site > Apps & content page. It should be up to me (the admin) whether that app is secure or not for my use. I'd also really like it if I can set the starting page of the Browser app to a specific URL in this scenario. My use case for this is... We're a construction MEP engineering firm where we're primarily using the headsets with the Autodesk Workshop XR app, BUT we have a need to also access Matterport's website to view 3D scans in VR. I would however prefer to setup our headsets in Shared Mode so that many different users can simply hop on a shared headset and more easily get right into these specific workflows.
Accessibility Feature Request: Conversation Focus Mode for Ray-Ban Meta Display Glasses
Hi everyone! I’m a Ray-Ban Meta display glasses user who is hard of hearing and wears hearing aids daily. I’d love to see a conversation focus mode added that prioritizes voices directly in front of the wearer and reduces background noise. In busy environments, this would make a big difference for hearing-aid users and others who rely on clearer speech in real time. If this type of accessibility feature is ever developed, I would absolutely love the ability to have it added to my glasses and would be happy to provide feedback or participate in any beta or user-testing opportunities. I’ve also submitted this through support channels, but wanted to share here in case the team is gathering feedback.
Error passing entitlements check in Native SDK
I cannot pass the entitlements check in the Native SDK, receiving the following message: Either the service couldn't be connected to, Horizon isn't installed, or you're running an incompatible version of Home/Horizon Here is the context for a better understanding: - My Meta account has been added to the organization where the app was created. - My Meta account has been added to the test channel where the app is being tested. - The app has been in the Meta Horizon Store for a long time, and now I'm trying to release a patch. - Developer mode is enabled. - The SDK is initialized with the correct App ID. - I see the app in my library. - Both the headset and the mobile app have the latest update. However, I cannot pass the entitlements check even in the latest version of the app published in the Meta Horizon Store. Could you tell me what I'm missing?
user_nonce_validate returns 503 Service Unavailable
Our web server sends request to the https://graph.oculus.com/user_nonce_validate/ endpoint when our players run our game. At 2025-10-15 21:31:54 (UTC) we started getting 503 Service Unavailable responses to our requests to this endpoint. The last instance with a 503 response was observed in our logs at 2025-10-16 01:43:03 (UTC). We haven't seen the issue since then. The Graph API status page shows no known issues during this time. Did anyone else observe this downtime in their tech stacks? Can someone from Meta confirm that there was an issue during that time period?
