FirebaseMLException

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).

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 not enough space left on the device.

Some requested resource was not found.

The operation completed successfully. FirebaseMLException will never have a status of OK.

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. This is a most likely a transient condition and may be corrected by retrying with a backoff.

In ML Kit, this error is mostly about the models being not available yet.

Operation is not implemented or not supported/enabled.

Unknown error or an error from a different error domain.

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