Google.XR.ARCoreExtensions

Indicates that ARCore will not attempt to use a hardware depth sensor, such as a time-of-flight sensor (or ToF sensor), even if it is present.

Most commonly used to filter camera configurations when the app requires exclusive access to the hardware depth sensor outside of ARCore, for example to support 3D mesh reconstruction. Available on all ARCore supported devices.

Indicates that a hardware depth sensor, such as a time-of-flight sensor (or ToF sensor), must be present on the device, and the hardware depth sensor will be used by ARCore.

Not supported on all devices.

Back-facing (world) camera is enabled.

Available on all ARCore supported devices.

Front-facing (selfie) camera is enabled.

See ARCore supported devices for available camera configs by device.

To limit distribution of your app to only devices that have a front-facing camera, use android.hardware.camera.

ARCore will not attempt to use a stereo camera, even if one is present.

Valid on all ARCore supported devices.

A stereo camera is present on the device and will be used by ARCore.

Not available on all ARCore supported devices.

Target 30fps camera capture frame rate.

Available on all ARCore supported devices.

Target 60fps camera capture frame rate.

Increases power consumption and may increase app memory usage.

See the ARCore supported devices page for a list of devices that currently support 60fps.

Cloud Anchors are disabled.

This is the default value.

Cloud Anchors are enabled, HostCloudAnchor() and ResolveCloudAnchorId() functions are available.

The app is expected to have the INTERNET permission (Android only).

Hosting failed because the server could not successfully process the dataset for the given Cloud Anchor.

The developer should try again after the devices has gathered more data from the environment.

The ARCore Cloud Anchor service was unreachable.

This can happen because of a number of reasons. The device may be in airplane mode or does not have a working internet connection. The request sent to the server could have timed out with no response, there could be a bad network connection, DNS unavailability, firewall issues, or anything that could affect the device's ability to connect to the ARCore Cloud Anchor service.

A hosting or resolving task for this Cloud Anchor has completed with an internal error.

The app should not attempt to recover from this error.

The app cannot communicate with the ARCore Cloud because of an invalid authentication.

Check Project Settings > XR Plug-in Management > ARCore Extensions for a valid authentication strategy.

Resolving failed because the ARCore Cloud Anchor service could not find the provided Cloud Anchor Id.

The Cloud Anchor could not be acquired because the ARCore Extensions package used to host the Cloud Anchor was older than and incompatible with the version being used to acquire it.

The Cloud Anchor could not be resolved because the ARCore Extensions package used to host the Cloud Anchor was newer than and incompatible with the version being used to acquire it.

The application has exhausted the request quota alloted to the given API key.

The developer should request additional quota for the ARCore Cloud for their API key from the Google Developers Console.

The Cloud Anchor is not ready to use.

A hosting or resolving task for this Cloud Anchor has completed successfully.

A hosting or resolving task is in progress for this Cloud Anchor.

Once the task completes in the background, the Cloud Anchor will get a new state after the next update.

Hosting failed because the server could not successfully process the dataset for the given Reference Point.

The developer should try again after the devices has gathered more data from the environment.

The ARCore Cloud Anchor service was unreachable.

This can happen because of a number of reasons. The device may be in airplane mode or does not have a working internet connection. The request sent to the server could have timed out with no response, there could be a bad network connection, DNS unavailability, firewall issues, or anything that could affect the device's ability to connect to the ARCore Cloud Anchor service.

A hosting or resolving task for this Reference Point has completed with an internal error.

The app should not attempt to recover from this error.

The app cannot communicate with the ARCore Cloud because of an invalid or unauthorized API key in the manifest, or because there was no API key present in the manifest.

Resolving failed because the ARCore Cloud Anchor service could not find the provided Cloud Anchor Id.

The Reference Point could not be acquired because the ARCore Extensions package used to host the Cloud Anchor was older than and incompatible with the version being used to acquire it.

The Reference Point could not be resolved because the ARCore Extensions package used to host the Cloud Anchor was newer than and incompatible with the version being used to acquire it.

The application has exhausted the request quota alloted to the given API key.

The developer should request additional quota for the ARCore Cloud for their API key from the Google Developers Console.

The cloud reference point is not ready to use.

A hosting or resolving task for this Reference Point has completed successfully.

A hosting or resolving task is in progress for this Reference Point.

Once the task completes in the background, the Reference Point will get a new state after the next update.

Earth localization is enabled, and has not encountered any problems.

Check AREarthManager.EarthTrackingState to determine if the Geospatial API can be used.

Earth localization has been disabled on this session.

All ARGeospatialAnchor created during this session will have TrackingState set to None and should be destroyed.

Earth localization has encountered an internal error.

The app should not attempt to recover from this error. Please see application logs for additional information.

The authorization provided by the application is not valid.

• The Google Cloud project may not have enabled the ARCore API.
• When using API key authentication, this will happen if the API key in the manifest is invalid, unauthorized. It may also fail if the API key is restricted to a set of apps not including the current one.
• When using keyless authentication, this may happen when no OAuth client has been created, or when the signing key and package name combination does not match the values used in the Google Cloud project. On Android, it may also fail if Google Play Services isn't installed, is too old, or is malfunctioning for some reason (e.g. killed due to memory pressure).

The package is older than the supported version.

The application has exhausted the quota allotted to the given Google Cloud project.

The developer should request additional quota for the ARCore API for their project from the Google Cloud Console.

The quality of feature points seen from the pose in the preceding few seconds is likely sufficient for ARCore to successfully resolve a Cloud Anchor with a high degree of accuracy.

The quality of feature points seen from the pose in the preceding few seconds is low.

This state indicates that ARCore will likely have more difficulty resolving the Cloud Anchor. Encourage the user to move the device, so that the desired position of the Cloud Anchor to be hosted is seen from different angles.

The quality of feature points seen from the pose in the preceding few seconds is likely sufficient for ARCore to successfully resolve a Cloud Anchor, although the accuracy of the resolved pose will likely be reduced.

Encourage the user to move the device, so that the desired position of the Cloud Anchor to be hosted is seen from different angles.

The feature or capability is supported.

Support is unknown.

This could be because support is still being determined.

The feature or capability is not supported.

The Geospatial API is disabled.

When a configuration with Disabled becomes active on the AR session, current anchors created from ARAnchorManagerExtensions.AddAnchor( UnityEngine.XR.ARFoundation.ARAnchorManager, double, double, double, UnityEngine.Quaternion) will stop updating and have their UnityEngine.XR.ARSubsystems.TrackingState set to None.

ARCore Extensions will not request location permissions.

The Geospatial API is enabled, and AREarthManager can be used.

Using this mode requires your app do the following:

• On Android, be granted the Android ACCESS_FINE_LOCATION permission. ARCore Extensions will request this permission when Geospatial is enabled in ARCore Extensions Project Settings > Optional Features.
• On Android, have enabled Unity's Internet Access permission in Android Player Settings.
• On iOS, have at least CLAuthorizationStatus authorizedWhenInUse and CLAccuracyAuthorization fullAccuracy in iOS's Location Services permissions.

Location is tracked only while ARSession is enabled. While it is disabled, AREarthManager.EarthTrackingState will be UnityEngine.XR.ARSubsystems.TrackingState.None.

For more information, see documentation on the Geospatial API on Google Developers.

This mode is not compatible with the UnityEngine.XR.ARFoundation.CameraFacingDirection.User (selfie) camera; use the World camera instead.

Not all devices support this mode, use AREarthManager.IsGeospatialModeSupported(GeospatialMode) to check if the current device and selected camera support enabling this mode.

Playback failed.

The session was not paused when setting the playback dataset.

Operation is unsupported with the current session.

The request completed successfully.

The call to ARPlaybackManager.SetPlaybackDataset(string) failed because ARCore is currently attempting to resume or pause the session.

Try calling it again in the next frame. Note:

• Resuming session may require several frames to complete.
• Pausing session may take up to 10 seconds to pause.

Playback has finished successfully.

The session is waiting on the final frame of the dataset. To resume a live camera feed or play another dataset, pause the session, call ARPlaybackManager.SetPlaybackDataset(), and resume the session.

Playback has stopped due to an error.

The session is not playing back a dataset.

Playback is in process without issues.

When using ARRecordingManager.StartRecording(ARCoreRecordingConfig), this means a recording is already in progress.

When using ARRecordingManager.RecordTrackData(Guid, byte[]), this means either RecordingStatus is not currently RecordingStatus.OK or the system is currently under excess load for images to be produced. The system should not be under such excess load for more than a few frames and an app should try to record the data again during the next frame.

When using ARRecordingManager.StartRecording(ARCoreRecordingConfig), this means the ARCoreRecordingConfig was null or invalid.

When using ARRecordingManager.RecordTrackData(Guid, byte[]), this means the track id or payload given are null or invalid.

IO or other general failure.

The request completed successfully.

The call to ARRecordingManager.StartRecording(ARCoreRecordingConfig) failed because ARCore is currently attempting to resume or pause the session.

Try calling it again in the next frame. Note:

• Resuming session may require several frames to complete.
• Pausing session may take up to 10 seconds to pause.

There was an IO error while recording.

The recorder is not recording.

The recorder is recording normally.