Shared Spatial Anchors Troubleshooting Guide

• It does not recognize the space the user is in.
• When attempting to load an anchor from storage location Cloud, verify the Enhanced Spatial Services setting is enabled.

• Reconstruct the scene, by having the user place the content where it belongs, or have the user walk to known locations to help the system recover the content.
• In the case of Shared Spatial Anchors, inform users to turn on Enhanced Spatial Services.

• Navigate to dashboard.oculus.com.
• Click Create New App under your developer team.
• Choose Meta Horizon Store. If you use Link to run the app from your PC, repeat these steps to also create a Rift app.
• Navigate to Data Use Checkup from the left-side navigation and request access to the User ID and User Profile platform features.
• Navigate to API from the left-side navigation and note the App ID.
• In your Unity project, navigate to Oculus / Platform / Edit Settings.
• Specify the Quest App Id from above as “Oculus Go/Quest”.
• If you want to test with Link, specify the Rift App Id as “Oculus Rift”.
• Put the headset in the developer mode.
• Make sure you are logged in as a developer or with a test account from the developer team that owns the application you are developing.

• The anchors do not exist on the cloud, or the user attempting to download the anchors does not have access to the anchors.
• The anchors were downloaded, but the device was unable to localize using the spatial data received from the sharing device, because the user has not observed enough of the environment.

• If you see any of these messages, the download step itself has failed:
  • xr_cloud_anchor_service: Downloaded 0 anchors
  • xr_cloud_anchor_service: Failed to download Map for spatial anchors
  • xr_cloud_anchor_service: Failed to download spatial anchor with error:
• If the log from log channel, SlamAnchorRuntimeIpcServer, contains the message below, it means the user was able to download the anchors, but the device was unable to localize itself in the spatial data received from the sharing device. You may see the error code EOculusXRAnchorResult::Failure_SpaceMappingInsufficient and a message Import task failed with code: <error> message: <message>.
• If you see the error code EOculusXRAnchorResult::Failure_SpaceNetworkRequestFailed or EOculusXRAnchorResult::Failure_SpaceNetworkTimeout, it means there was a network issue connecting to the cloud. Make sure your device wi-fi connection is working and try again.

• The map/anchors have expired. There is Time to Live (TTL) for any anchor that is uploaded to the cloud. After the TTL expires, the anchor is erased from the cloud.
• The Spatial Anchor was not successfully uploaded to the cloud.
• The intended recipient of the anchor does not have access. The sender may not have shared the anchor, or the share operation may have failed.
• The device is not connected to the network. Make sure your device wi-fi is working and try again.

1. Create a new anchor with new UUID, save and share again.
2. Confirm the upload was successful by searching for the following messages in logcat: xr_cloud_anchor_service: Successfully uploaded spatial anchors: and xr_cloud_anchor_service: UUID: <some uuid>
   • If the upload was not successful, follow the troubleshooting steps from the Anchor upload fails.
3. Confirm sharing was successful by searching for following message in logcat: xr_cloud_anchor_service: Share spatial anchor success. If the sharing was not successful, follow the troubleshooting steps from the Anchor sharing fails section.

• The specified user ID does not exist, or is not valid
• The Spatial Anchor was not uploaded to the cloud

• If the Spatial Anchor is not uploaded, first invoke the save operation to cloud, and then share the anchor again.
• If a Spatial Anchor is already uploaded, you do not have to re-upload the anchor to share it again. In this case, invoke the share operation without invoking the save operation.

• Request denied based on storage location for package {}, sessionUuid:{}.
• getCloudPermissionEnabled: oculus_spatial_anchor_cloud=false

• The user has disabled “Enhanced Spatial Services” in Settings > Privacy, or has selected “Not now” in the dialog presented the first time they launch an experience that it. In this case, the logs should contain any of:
  • PreferencesManager: anchor_persistence_cloud_anchor_service_enabled: false
  • userPreference(anchor_persistence_cloud_anchor_service_enabled)=false
• The headset and/or OS version does not support Shared Spatial Anchors. In this case, the logs should contain any of:
  • checkGatekeeper gatekeeperName: oculus_spatial_anchor_cloud, value: false
  • GK(oculus_spatial_anchor_cloud)=false

XrSpaceComponentStatusFB storableStatus;
xrGetSpaceComponentStatusFB(
    space, XR_SPACE_COMPONENT_TYPE_STORABLE_FB, &storableStatus));
if (storableStatus.enabled) {
    // Save or upload the anchor.
}

XrSpaceComponentStatusFB sharableStatus;
xrGetSpaceComponentStatusFB(
    space, XR_SPACE_COMPONENT_TYPE_SHARABLE_FB, &sharableStatus));
if (sharableStatus.enabled) {
    // Share the anchor.
}

• Use Shared Spatial Anchors
• Samples
• Troubleshooting
• C++ Reference
• Blueprint Reference