Forum Discussion

mu_raza's avatar
mu_raza
Honored Guest
24 days ago

Unity-SpaceSharing sample fails with shareLocalScene failed: FailureOperationFailed (-1006)

Hi, I am trying to use the Unity-SpaceSharing sample: https://github.com/oculus-samples/Unity-SpaceSharing

 

I consistently get: shareLocalScene failed: FailureOperationFailed (-1006)

 

I have already checked the usual setup items. The app is in the Alpha release channel, the App ID is correct, MQDH/device setup looks correct, and spatial data sharing is enabled.

 

What I’m seeing in the logs is:

Repeated local anchor read failures with error -60001

Then shareSpatialEntity failed with GraphQLError code=2128008

A server message saying some anchors could not be found in the cloud by ID

Also, Mesh upload through cloudAnchorService is not supported

 

Two example anchor IDs mentioned in the failure are:

ce6a45dd-d2bd-2115-e2d7-8ec57d8fcd58

9c4d1d9c-7949-392b-c39c-3ca9c3ee1547

 

I am calling the sample’s local scene-sharing flow from the MRUK room-sharing path, but I also tested a version where I manually built the anchor list from room anchors and child scene anchors.

 

My 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?

Should the recommended approach be to use only room.ShareRoomAsync(groupId) or mruk.ShareRoomsAsync(mruk.Rooms, groupId) and avoid manual anchor collection?

Does error -60001 indicate that the scene anchors need to be recreated or re-persisted before sharing?

 

If helpful, I can also share the exact method I am using and a larger log snippet.

 

Thanks.

1 Reply

  • Degly's avatar
    Degly
    Start Mentor

    Not sure about the specifics of this, but taking a look at the docs it looks like the share call is receiving anchors that are not valid cloud-shareable anchors yet.

    The biggest clue is:

    Mesh upload through cloudAnchorService is not supported

    So I would avoid manually collecting anchors unless you are sure they are persisted spatial anchors.

    maybe with:

    room.ShareRoomAsync(groupId)

    or

    mruk.ShareRoomsAsync(mruk.Rooms, groupId)

    -60001 also suggests the local anchor read/persistence step is failing, so recreating/resaving the room may help.

    This feels more like unsupported/non-persisted anchors being included in the share list rather than a networking issue.

→ Find helpful resources to begin your development journey in Getting Started

→ Get the latest information about HorizonOS development in News & Announcements.

→ Access Start program mentor videos and share knowledge, tutorials, and videos in Community Resources.

→ Get support or provide help in Questions & Discussions.

→ Show off your work in What I’m Building to get feedback and find playtesters.

→ Looking for documentation?  Developer Docs

→ Looking for account support?  Support Center

→ Looking for the previous forum?  Forum Archive

→ Looking to join the Start program? Apply here.

 

Recent Discussions