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.
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.
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.
Describes possible tracking failure reasons of an ArCamera.
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.
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.