cancel
Showing results for 
Search instead for 
Did you mean: 

Issue with Sharing Spatial Anchors in Meta XR SDK v. 66

Dev.Khora
Explorer

Hello,

I am encountering an issue with spatial anchors in my application using Meta XR SDK v. 66 on Quest 3. My application allows one user to create a spatial anchor and share it with other users in the session. However, the users who receive the shared spatial anchor are unable to share the same anchor using ShareAsync, despite successfully loading (LoadUnboundSharedAnchorsAsync) and saving (SaveAnchorsAsync) the anchor beforehand.

Previously, with Meta XR SDK v. 60, I could do this without any issues by saving the anchor to the cloud before sharing using the now obsolete method:

OVRSpatialAnchor.SaveOptions saveOptions;
saveOptions.Storage = OVRSpace.StorageLocation.Cloud;
_spatialAnchor.Save(saveOptions, (spatialAnchor, isSuccessful) => { ... });

Since updating to Meta XR SDK v. 66 and the latest Quest 3 software, and switching to the new async SSA methods, only the user who originally created the anchor can share it. For other users, the OVRSpatialAnchor.ShareAsync method fails with error code -1006.

Here is a summary of the steps I am following:

  1. User A creates a spatial anchor and saves it using OVRSpatialAnchor.SaveAnchorsAsync.
  2. User A shares the anchor using OVRSpatialAnchor.ShareAsync.
  3. User B receives and successfully loads the shared anchor using OVRSpatialAnchor.LoadUnboundSharedAnchorsAsync.
  4. User B successfully saves the anchor using OVRSpatialAnchor.SaveAnchorsAsync.
  5. User B attempts to share the anchor but OVRSpatialAnchor.ShareAsync fails with error code -1006.

I have verified that I am correctly adding the OVRSpaceUsers when sharing the anchors. The app has also been correctly configured on Oculus Developer Dashboard, and Share Point Cloud Data is enabled on all devices.

Any guidance or solutions to resolve this issue would be greatly appreciated.

Thank you!

3 REPLIES 3

jtriveri
Adventurer

Experiencing this too. These things are a nightmare to use and I'm tired of every update making subtle undocumented changes to how they work. I'm tempted to say you shouldn't rely on shared spatial anchors. They are insanely finicky both functionally and to work with : (

Fabularis
Protege

Did you solve it?
I check permission a thousand of times, trying all about the documentation and forum but I have always the error -1006

No unfortunately, it is still unsolved. I assume it's an issue with the SDK, and I haven't seen any updates from Meta that should fix it. Please let me know if you find any solution!