Shared types and enums

Hosting a Cloud Anchor failed because the anchor is not a type of anchor that is currently supported for hosting.

The Android camera has been reallocated to a higher priority application or is otherwise unavailable.

The application does not have Android camera permission.

The host/resolve function call failed because the Session is not configured for Cloud Anchors.

The data passed in for this operation was not in a valid format.

The data passed in for this operation is not supported by this version of the SDK.

Acquire failed because the object being acquired was already released.

For example, this happens if the application holds an ArFrame beyond the next call to ArSession_update, and then tries to acquire its Point Cloud.

An internal error occurred that the application should not attempt to recover from.

The Android precise location permission (ACCESS_FINE_LOCATION) is required, but has not been granted prior to calling ArSession_configure when ArGeospatialMode is set to AR_GEOSPATIAL_MODE_ENABLED.

See Android documentation on Request location access at runtime for more information on how to request the ACCESS_FINE_LOCATION permission.

The Fused Location Provider for Android library is required, but wasn't found in the client app's binary prior to calling ArSession_configure when ArGeospatialMode is set to AR_GEOSPATIAL_MODE_ENABLED.

Ensure that your app includes the Fused Location Provider of Android library, and that your app's ProGuard rules are correctly set up for the Geospatial API.

When building your app, check the resulting binary with the APK Analyzer, and ensure that the built application binary includes the com.google.android.gms.location package, and that its contents are not renamed or minified.

A function has been invoked at an illegal or inappropriate time.

A message will be printed to logcat with additional details for the developer. For example, ArSession_resume will return this status if the camera configuration was changed and there is at least one unreleased image.

Attempted to add an image with insufficient quality (e.g., too few features) to the image database.

ArSession_configure failed because the specified configuration required the Android INTERNET permission, which the application did not have.

One of the arguments was invalid; either NULL or not appropriate for the operation requested.

The requested metadata tag cannot be found in input metadata.

An operation required GL context but one was not available.

An operation was attempted that the session be in the AR_TRACKING_STATE_TRACKING state, but the session was not.

Acquire failed because the data isn't available yet for the current frame.

For example, acquiring image metadata may fail with this error because the camera hasn't fully started.

When playback failed.

When recording failed.

There are no available resources to complete the operation.

In cases of acquire functions returning this error, this can be avoided by releasing previously acquired objects before acquiring new ones.

An operation was attempted that requires the session be paused, but the session was running.

An operation was attempted that requires the session be running, but the session was paused.

Operation is unsupported with the current session.

A texture name was not set by calling ArSession_setCameraTextureName before the first call to ArSession_update.

The configuration supplied to ArSession_configure is unsupported.

To avoid this error, ensure that Session_checkSupported() returns true.

The operation was successful.

The ARCore APK currently installed on device is too old and needs to be updated.

The ARCore APK is not installed on this device.

The device is not currently compatible with ARCore.

The ARCore APK currently installed no longer supports the ARCore SDK that the application was built with.

The user declined installation of the ARCore APK during this run of the application and the current request was not marked as user-initiated.

Motion tracking lost due to bad internal state.

No specific user action is likely to resolve this issue.

Motion tracking paused because the camera is in use by another application.

Tracking will resume once this app regains priority, or once all apps with higher priority have stopped using the camera. Prior to ARCore SDK 1.13, AR_TRACKING_FAILURE_REASON_NONE is returned in this case instead.

Motion tracking lost due to excessive motion.

Ask the user to move the device more slowly.

Motion tracking lost due to insufficient visual features.

Ask the user to move to a different area and to avoid blank walls and surfaces without detail.

Motion tracking lost due to poor lighting conditions.

Ask the user to move to a more brightly lit area. On Android 12 (API level 31) or later, the user may have disabled camera access, causing ARCore to receive a blank camera feed.

Indicates expected motion tracking behavior.

Always returned when ArCamera_getTrackingState is AR_TRACKING_STATE_TRACKING. When ArCamera_getTrackingState is AR_TRACKING_STATE_PAUSED, indicates that the session is initializing normally.

ARCore has paused tracking this object, but may resume tracking it in the future.

This can happen if device tracking is lost, if the user enters a new space, or if the session is currently paused. When in this state, the positional properties of the object may be wildly inaccurate and should not be used.

ARCore has stopped tracking this Trackable and will never resume tracking it.

The object is currently tracked and its pose is current.