MlKitException

The operation was aborted, typically due to a concurrency issue like transaction aborts, etc.

Some resource that we attempted to create already exists.

The operation was cancelled (typically by the caller).

Not able to get the calling App name.

Camera permission is not granted to Google Play Service.

User closes the scanner to cancel code scanning.

Google play services version is too old.

Failed to run the inference of barcode detection.

Failed to initialize barcode scanner pipeline.

At most one scanning task is allowed to be in progress.

Required code scanner module is not available yet.

Unrecoverable data loss or corruption.

Deadline expired before operation could complete. For operations that change the state of the system, this error may be returned even if the operation has completed successfully. For example, a successful response from a server could have been delayed long enough for the deadline to expire.

Operation was rejected because the system is not in a state required for the operation's execution.

Internal errors. Means some invariants expected by underlying system has been broken. If you see one of these errors, something is very broken.

Client specified an invalid argument. Note that this differs from FAILED_PRECONDITION. INVALID_ARGUMENT indicates arguments that are problematic regardless of the state of the system (e.g., an invalid field name).

The downloaded model's hash doesn't match the expected value.

The downloaded model isn't compatible with the TFLite runtime.

There is a network issue when filing a network request.

There is not enough space left on the device.

Some requested resource was not found.

Operation was attempted past the valid range.

The caller does not have permission to execute the specified operation.

Some resource has been exhausted, perhaps a per-user quota, or perhaps the entire file system is out of space.

The request does not have valid authentication credentials for the operation.

The service is currently unavailable.

In ML Kit, this error is mostly caused by one of the following reasons: 1. The models being not available yet: This is a most likely a transient condition and may be corrected by retrying with a backoff. 2. The remote server is not available when trying to connect to it. 3. The detector/scanner has already been closed: This usually indicates that detector is called after lifecycle event "ON_DESTROY".

Operation is not implemented or not supported/enabled.

Unknown error or an error from a different error domain.

The feature is not supported on this device. Waiting or trying again won't resolve it.

Gets the error code for the ML Kit operation that failed.