Hi, I'm experiencing the exact same issue and wanted to share my findings in case it helps.
My setup:
- Meta Quest 3 (4 devices)
- Unity + Photon Fusion + MRUK Space Sharing
- Meta XR All-in-One SDK v201.0.0
- APK uploaded to Alpha channel, testers invited
My chronology: The app was working correctly, then stopped working spontaneously the following week without any changes on my side (no new build, no firmware update, no SDK update).
Phase 1 — First error:
ERROR_CLOUD_NO_PERMISSION_TO_MODIFY_SPATIAL_ENTITY GraphQL error code: 2128019 internal_anchor_uuid: 80569ce7-abaa-77c1-6aac-b8b013b0486a owner app id: com.oculus.guardian
Phase 2 — After factory reset:
ERROR_CLOUD_MESH_UPLOAD_FAILED GraphQL error code: 2128008 internal_anchor_uuid: beeb90ea-86ca-d629-37a5-263efa9e934a owner app id: com.oculus.guardian
Key observation from ADB logs: The upload of the app's own spatial anchor always succeeds. Only the Scene Anchors owned by com.oculus.guardian fail to upload. The code used is the standard room.ShareRoomAsync(groupUuid) as per official Meta documentation.
fb_traceids:
fb_traceid=EBvV8NP9m0d fb_traceid=DKZacnQLK4C fb_traceid=Fl5LV2uxHaJ
What I tried without success:
- Cleared Physical Space History and redid Space Setup on all headsets
- Factory reset on one headset
- Reinstalled the app
- Tested on 2 different WiFi networks and mobile hotspot
- Uploaded APK to Alpha channel with testers invited
I notice at least 2 developers on this forum reported the same issue appearing this week. This strongly suggests a server-side breaking change or bug introduced by Meta recently, not a problem in our code.
Has anyone found a workaround? And can a Meta engineer please investigate using the fb_traceids above?