> 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/installation.md).

# Installation

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

To integrate the **CafFaceLivenessLite SDK** into your iOS project, use Swift Package Manager (SPM) or CocoaPods. From 7.8.0, the binaries are also published to the [CAF repository](#caf-repository-binary-distribution).

## Requirements

* iOS Version: 15.0 or higher
* Xcode Version: 26.0 or higher
* Swift Version: 6.3 or higher
* CAF Mobile Token: A valid mobileToken

## Installation

### Swift Package Manager (SPM)

1. Open your project in Xcode.
2. Go to `File` > `Add Packages...`.
3. Enter the repository URL: `https://github.com/combateafraude/caf-ios-sdk`
4. Select the `CafFaceLivenessLite` package or your unified SDK if applicable.
5. Complete integration via the prompts.

### CocoaPods

1. Ensure CocoaPods is installed on your system. If not:

```bash
sudo gem install cocoapods
```

2. Navigate to your project directory.
3. Create or update your Podfile (example):

```ruby
platform :ios, '15.0'
use_frameworks!

target 'YourAppTarget' do
  pod 'CafSDKiOS/CafFaceLivenessLite', '7.8.0'
end
```

4. Install pods:

```bash
pod install
```

5. Open the generated `.xcworkspace`.

### CAF Repository (Binary Distribution)

From 7.8.0, CafFaceLivenessLite is also published to the CAF repository, the same one used for the Android SDKs. Each version has its own folder:

```
https://repo.combateafraude.com/ios/release/CafFaceLivenessLite/{version}/
```

Replace `{version}` with the SDK version you want, for example `7.8.0`. See [Current Version](https://docs.caf.io/caf-sdk/ios/standalone-modules/caffacelivenesslite/current-version.md).

#### CocoaPods with the CAF podspec

Point CocoaPods to the podspec published in the repository:

```ruby
platform :ios, '15.0'
use_frameworks!

target 'YourAppTarget' do
  pod 'CafFaceLivenessLite', :podspec => 'https://repo.combateafraude.com/ios/release/CafFaceLivenessLite/{version}/CafFaceLivenessLite.podspec'
end
```

Then run `pod install`. The podspec downloads the xcframework from the CAF repository and declares its dependencies.

{% hint style="warning" %}
Use either `CafSDKiOS/CafFaceLivenessLite` or the CAF podspec, not both in the same target.
{% endhint %}

#### Release artifacts

| Artifact                                     | URL                                                                                                                    |
| -------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------- |
| `CafFaceLivenessLite.xcframework.zip`        | `https://repo.combateafraude.com/ios/release/CafFaceLivenessLite/{version}/CafFaceLivenessLite.xcframework.zip`        |
| `CafFaceLivenessLite.xcframework.zip.sha256` | `https://repo.combateafraude.com/ios/release/CafFaceLivenessLite/{version}/CafFaceLivenessLite.xcframework.zip.sha256` |
| `CafFaceLivenessLite.podspec`                | `https://repo.combateafraude.com/ios/release/CafFaceLivenessLite/{version}/CafFaceLivenessLite.podspec`                |
| `Package.swift`                              | `https://repo.combateafraude.com/ios/release/CafFaceLivenessLite/{version}/Package.swift`                              |

SHA256 of `CafFaceLivenessLite.xcframework.zip` for v7.8.0:

```
9f40c4cac7d196f6435c7fbf0926849e177e4aaf61b14c63b5cfdb7706dfbe36
```

To verify a downloaded file:

```bash
shasum -a 256 CafFaceLivenessLite.xcframework.zip
```

The output must match the `.sha256` file published for that version.

{% hint style="info" %}
The xcframework has external dependencies that are declared in the podspec and in `Package.swift`. Use one of them rather than adding the xcframework to your project by hand.
{% endhint %}


---

# 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/caf-sdk/ios/standalone-modules/caffacelivenesslite/installation.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.
