Hi, I have the same issue and went deeper into the ADB logs to find the root cause.
Is FailureOperationFailed (-1006) caused by anchors not being uploaded?
Yes, exactly. In my case the full chain is:
ShareRoomAsync tries to share the room
Before sharing, it attempts to upload the Scene Anchors to the cloud
The upload fails with ERROR_CLOUD_MESH_UPLOAD_FAILED (-400039) because the GLOBAL_MESH anchor is included in the upload but mesh upload through cloudAnchorService is not supported
Because the upload fails, the share fails with FailureOperationFailed (-1006)
Is there a known issue with unsupported scene/mesh anchors?
Yes. From my ADB logs, the system prints:
"Mesh upload through cloudAnchorService is not supported. Skipping upload of Scene Anchor with UUID 8e1074bf-6247-1fe9-2ae3-c7542e0de436"
The system says it skips the GLOBAL_MESH, but then the mesh upload operation still runs and fails, blocking the entire batch. This looks like a bug in the SDK.
My detailed error sequence from ADB:
GraphQLError code=2128008 - Could not find Anchor(s) in Cloud by specified id(s) internal_anchor_uuid: beeb90ea-86ca-d629-37a5-263efa9e934a owner app id: com.oculus.guardian ERROR_CLOUD_MESH_UPLOAD_FAILED (-400039) fb_traceid=EBvV8NP9m0d fb_traceid=DKZacnQLK4C fb_traceid=Fl5LV2uxHaJ
This was working before and stopped spontaneously. At least 2 developers on this forum reported the same issue appearing this week, suggesting a server-side change by Meta.
I tried excluding the GLOBAL_MESH manually using OVRAnchor.ShareAsync(filteredAnchors, groupUuid) but Scene Anchors owned by com.oculus.guardian do not support the OVRSharable component, so manual sharing is not possible either.
Hope this helps narrow down the issue. Would appreciate any input from Meta engineers.
