Skip to main content
New Participant
April 21, 2026
Question

ERROR_CLOUD_MESH_UPLOAD_FAILED(-400039)

Unity colocation build with MRUK, getting this error in Logcat and "host can't share the room with group xx-xx.." on immersive debugger...

User ID  and User profile active in dashboard, device has spatial permission enabled, project uploaded to alpha channel, my own user invited as tester, Keystore signed, tried with 4 different WIFI, no LLM has a clue...

was working before upload alpha,

What else should I check?

5 replies

New Participant
April 22, 2026

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?

MohsenzZAuthor
New Participant
April 22, 2026

Hi, thanks for your reply, 

Totally makes sense, since nothing looks wrong in my code, and even more strange that today I started with a fresh project [unity and meta], and getting the same error!

Getting this error on different devices, even the ones that never had the same app installed, so I think a factory reset also might not help! [will try it anyhow]

Do you also get this error in Logcat [I get it in some of the tries]:

Entitlement callback: isEntitled: True Name: MZ UserID: 0

have no idea why the user ID is 0!

It's been two days that I'm trying out anything [including what you mentioned], and it's still the same...

 

 

New Participant
April 23, 2026

Hi, I just wanted to let you know that I'm having the same issue as you.

I tried everything you also did.

This strengthens the suspicion that there is something wrong on Meta's site.

I'm getting these errors:

SP:AF:AnchorFramework: operator() shareAnchorToGroup failed!
SP:AF:AnchorFramework: operator() shareAnchorToGroup result code: -400039
SP:AnchorResultCode: anchorResultCodeToXrResult: Unknown mapping for AnchorResultCode AnchorResultCode::ERROR_CLOUD_MESH_UPLOAD_FAILED(-400039)
[Error] Host failed to share rooms with group 63e6d4f5-19d1-7044-85f3-7dae1c22eb31 : FailureOperationFailed

 

New Participant
April 23, 2026

Hi, yes, I also think there's a problem with cloud Meta.

I've opened a ticket and am waiting for a response.

New Participant
April 23, 2026

Thanks for that. Can you keep us posted when you got an answer?