> 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/caf-sdk/ios/standalone-modules/caffacelivenesslite/faq_caf_face_liveness_sdk.md).

# FAQ

Quick links: [Overview](/caf-sdk/ios/standalone-modules/caffacelivenesslite.md) | [Building the SDK](/caf-sdk/ios/standalone-modules/caffacelivenesslite/builder.md) | [Start Liveness Verification](/caf-sdk/ios/standalone-modules/caffacelivenesslite/start-sdk.md) | [UI Customization](/caf-sdk/ios/standalone-modules/caffacelivenesslite/ui-customization.md) | [Installation](/caf-sdk/ios/standalone-modules/caffacelivenesslite/installation.md) | [Current Version](/caf-sdk/ios/standalone-modules/caffacelivenesslite/current-version.md) | [Requirements](/caf-sdk/ios/standalone-modules/caffacelivenesslite/requirements.md) | [Source Code](/caf-sdk/ios/standalone-modules/caffacelivenesslite/source-code.md) | [Result Reference](/caf-sdk/ios/standalone-modules/caffacelivenesslite/result-reference.md) | [Release Notes](/caf-sdk/ios/standalone-modules/caffacelivenesslite/release-notes.md) | [FAQ](/caf-sdk/ios/standalone-modules/caffacelivenesslite/faq_caf_face_liveness_sdk.md)

***

## **1. What is the CafFaceLivenessLite SDK and what is its main functionality?**

**Answer:**

The Lite SDK provides a smaller, streamlined face liveness verification flow. It detects spoofing attempts to secure onboarding and authentication.

***

## **2. What are the system requirements for the Lite SDK on iOS?**

**Answer:**

Supports iOS 15.0+, Xcode 26.0+, and Swift 6.3+. See the [Requirements](/caf-sdk/ios/standalone-modules/caffacelivenesslite/requirements.md).

***

## **3. What permissions are required to use the Lite SDK?**

**Answer:**

* Camera access (`NSCameraUsageDescription` in `Info.plist`)
* Internet access (ATS exceptions if necessary)

***

## **4. How do I integrate the Lite SDK into my iOS project?**

**Answer:**

Use SPM or CocoaPods to add dependencies, then instantiate `CafFaceLivenessLiteSDK`, set its delegate, and call `startSDK`. See [Installation](/caf-sdk/ios/standalone-modules/caffacelivenesslite/installation.md) and [Start SDK](/caf-sdk/ios/standalone-modules/caffacelivenesslite/start-sdk.md).

***

## **5. How do I start the Face Liveness verification process?**

**Answer:**

1. Set the delegate.
2. Call `startSDK` with `viewController`, `mobileToken`, and `personId`.
3. Handle callbacks in `CafFaceLivenessLiteDelegate`.

See [Start SDK](/caf-sdk/ios/standalone-modules/caffacelivenesslite/start-sdk.md).

***

## **6. What errors and failures should I handle?**

**Answer:**

Handle `didFinishWithError(type:description:)` for execution errors (camera, network, token) and `didFinishWithFailure(type:description:signedResponse:)` for business failures (lighting, alignment). See [Result Reference](/caf-sdk/ios/standalone-modules/caffacelivenesslite/result-reference.md).

***

## **7. Can I customize texts or localization?**

**Answer:**

Yes. Pass `customLocalization` (strings table name, omit `.strings`) to `startSDK`. If the strings live outside the main app bundle, also pass `customLocalizationBundle` (for example `Bundle(for: CafFaceLivenessLiteSDK.self)`). See [iProov Localization](https://github.com/iProov/ios/wiki/Localization).

***

## **8. Can I chain FaceAuth after liveness?**

**Answer:**

No. From **2.0.0**, `executeFaceAuth` was removed — Face Auth is out of scope for the async Lite flow. Use the full Face Liveness / Face Auth products if you need authentication after liveness.

***

## **9. What does `signedResponse` mean in 2.0.0?**

**Answer:**

After capture, the SDK calls the async route and returns only an opaque `signedResponse` JWT via `didFinishWithSuccess` / `didFinishWithFailure`. Your backend must resolve the final liveness result (`isAlive`, images) out-of-band. The SDK does not poll.

***

## **10. What is the `enableSecurity` parameter and when should I disable it?**

**Answer:**

`enableSecurity` is a constructor parameter (default: `true`) that activates security monitoring — jailbreak detection, dylib monitoring, and instrumentation detection. When a violation is detected, `didFinishWithError` is called with `CafErrorType.securityException`.

Disable it (`enableSecurity: false`) only in automated UI testing environments where the test runner triggers false positives. **Keep it enabled in production builds.**

```swift
// Production
let sdk = CafFaceLivenessLiteSDK(enableSecurity: true)

// UI Testing only
let sdk = CafFaceLivenessLiteSDK(enableSecurity: false)
```


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.caf.io/caf-sdk/ios/standalone-modules/caffacelivenesslite/faq_caf_face_liveness_sdk.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.