> For the complete documentation index, see [llms.txt](https://docs.caf.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.caf.io/sdk-lite/setup/ios/result-reference.md).

# Result Reference

### CafFaceLivenessLiteResult – Success Event

| Field            | Description                                                                                                           |
| ---------------- | --------------------------------------------------------------------------------------------------------------------- |
| `signedResponse` | Opaque JWT issued with the liveness session. Forward it to your backend; the SDK does not return `isAlive` or images. |

{% hint style="info" %}
From **3.1.0**, the `signedResponse` is issued when the liveness session is created and handed to your delegate the moment the capture completes — there is no post-capture wait. Use it with your backend to obtain the final liveness outcome, as described in [Backend Setup](https://docs.caf.io/sdk-lite/setup/backend/setup.md); the SDK does not poll for it.
{% endhint %}

### CafErrorType – Error Handling

The SDK reports execution errors via `didFinishWithError(type:description:)`. Only the error types below are returned by CafFaceLivenessLite. For when each one is expected and how to guide the user, see [Error Handling](https://docs.caf.io/sdk-lite/error-handling/ios/error-handling.md):

| Error                                                                                                                              |
| ---------------------------------------------------------------------------------------------------------------------------------- |
| [`invalidOptionsException`](https://docs.caf.io/sdk-lite/error-handling/ios/error-handling.md#invalidoptionsexception)             |
| [`cameraPermission`](https://docs.caf.io/sdk-lite/error-handling/ios/error-handling.md#camerapermission)                           |
| [`securityException`](https://docs.caf.io/sdk-lite/error-handling/ios/error-handling.md#securityexception)                         |
| [`unsupportedDevice`](https://docs.caf.io/sdk-lite/error-handling/ios/error-handling.md#unsupporteddevice)                         |
| [`serverException`](https://docs.caf.io/sdk-lite/error-handling/ios/error-handling.md#serverexception)                             |
| [`tokenException`](https://docs.caf.io/sdk-lite/error-handling/ios/error-handling.md#tokenexception)                               |
| [`invalidResponseException`](https://docs.caf.io/sdk-lite/error-handling/ios/error-handling.md#invalidresponseexception)           |
| [`networkException`](https://docs.caf.io/sdk-lite/error-handling/ios/error-handling.md#networkexception)                           |
| [`captureAlreadyActiveException`](https://docs.caf.io/sdk-lite/error-handling/ios/error-handling.md#capturealreadyactiveexception) |
| [`userTimeoutException`](https://docs.caf.io/sdk-lite/error-handling/ios/error-handling.md#usertimeoutexception)                   |
| [`unexpectedErrorException`](https://docs.caf.io/sdk-lite/error-handling/ios/error-handling.md#unexpectederrorexception)           |

{% hint style="info" %}
`CafErrorType` is shared with other Certta SDKs and also declares `imageNotFoundException`, `tooManyRequestsException`, `permissionException`, `libraryException`, `unknownException`, `cameraException`, `certificateException`, `faceAuthentication` and `livenessException`. CafFaceLivenessLite never returns them. If you `switch` over `CafErrorType`, add a `default` case rather than handling each of them.
{% endhint %}

### CafFailureType – Failure References

Available feedback codes returned via `didFinishWithFailure(type:description:signedResponse:)`. The `type` is the most likely reason for the failure, and any code the SDK does not recognize is returned as `unknown`. `description` carries the localized message for that reason, and `signedResponse` is always present — it is the same JWT issued with the session, so forward it to your backend as you would on success:

| Enum value                 | Localized description (English)                                                            |
| -------------------------- | ------------------------------------------------------------------------------------------ |
| `unknown`                  | Try again                                                                                  |
| `tooMuchMovement` (legacy) | Keep still                                                                                 |
| `tooBright` (legacy)       | Move somewhere darker                                                                      |
| `tooDark` (legacy)         | Move somewhere brighter                                                                    |
| `misalignedFace` (legacy)  | Keep your face in the oval                                                                 |
| `faceTooFar` (legacy)      | Move your face closer to the screen                                                        |
| `faceTooClose` (legacy)    | Move your face farther from the screen                                                     |
| `sunglasses` (legacy)      | Remove sunglasses                                                                          |
| `systemError`              | System Error                                                                               |
| `rejected`                 | Transaction could not be completed                                                         |
| `faceNotFound`             | Align your face in the oval and then try to keep still                                     |
| `obscuredFace`             | Make sure your whole face is visible and remove any accessories that might cover your face |
| `timeout`                  | System timeout                                                                             |
| `eyewear`                  | Remove your eyewear                                                                        |
| `multipleFaces`            | Ensure only one person is visible                                                          |
| `eyesClosed`               | Make sure your eyes are open                                                               |
| `userNotFound`             | Transaction could not be completed                                                         |
| `lightingIssues`           | Make sure your face is well lit and free from glare                                        |
| `framesBlurry`             | Align your face in the oval and then try to keep still                                     |
| `deviceIssue`              | Try a different device                                                                     |
| `motionIssue`              | Align your face in the oval and then try to keep still                                     |
| `backgroundIssue`          | Move to a different location with a neutral background                                     |
| `deviceRestart`            | Please restart your device and try again                                                   |
| `processingFault`          | Please try again                                                                           |

Values marked as legacy are kept for compatibility, but the current versions no longer return them. See [Legacy Types](https://docs.caf.io/sdk-lite/failure-handling/mobile/failure-handling.md#legacy-types) for the current equivalent of each one.

{% hint style="info" %}
The `description` carries the localized text of the liveness engine for that reason. Do not show it as is: map the `type` to the recommended message in [Failure Reasons and User Guidance](https://docs.caf.io/sdk-lite/failure-handling/mobile/failure-handling.md), which was written to guide the next attempt without revealing what was detected.
{% endhint %}

## Next step

Forward the `signedResponse` to your backend, which validates it and retrieves the result: [Backend Setup](https://docs.caf.io/sdk-lite/setup/backend/setup.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.caf.io/sdk-lite/setup/ios/result-reference.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
