> 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/react-native/changelog.md).

# Changelog

React Native SDK release notes. Track versions, breaking changes, provider updates, and migration notes for Certta, Face Liveness, and Document Detector.

## Release notes

### @caf.io/react-native-sdk\@5.5.0

#### **Release date**

* 10-13-2026

#### **Highlights**

* Native Android SDK updated to **7.28.0**, which includes Document Detector fixes.
* iOS native SDK version is unchanged (**7.8.0**).

#### **Fixes**

Inherited from CafSDK Android 7.28.0:

* **Document Detector:** Document upload no longer shows a blank screen when the user presses **back** on the upload dialog.
* **Document Detector:** Consecutive capture flows no longer reuse the previous flow state. A flow configured for RG no longer accepts CNH.
* **Document Detector:** The module now respects the configured environment.
* **Document Detector:** The instruction-screen popup no longer clips the confirmation button.
* **Face Liveness Lite:** The iProov screen stays visible until the result is delivered. The BFF address is resolved from the region in the token and is restricted to `*.caf.io`.

### @caf.io/react-native-sdk\@5.4.0

#### Release date

* 09-29-2026

#### Highlights

* **Certta DevX (first hybrid release):** New `useCerttaSdk` hook with Document Detector and Face Liveness (core and UI) on Android and iOS.
* Configure the session once with `configureSDK(CerttaConfiguration)`, then open each module independently via `useCafFaceLiveness().open()`, `useCafDocumentDetector().open()`, and `useCafDocumentDetectorUI().open()`.
* The sequential `useCafSdk` API remains available in the same package.

#### Updates

* Per-module Certta events on hook `event` state (`CerttaLivenessEvent`, `CerttaEvent`).
* Session logs collected in `useCerttaSdk().logs`.
* Runtime `updateUserId` / `updateMobileToken` after the initial session configuration.
* `CerttaLivenessFailure` with stable `cause` codes and `description` for user-facing text.
* Bridge mapper rejections reject with `CerttaPlatformException` and code `BRIDGE_EXCEPTION`.
* Bridge updates aligned with native Certta commons (including React Native platform propagation).

See the [Installation Guide](/caf-sdk/react-native/installation-guide.md) and [Migrating from CafSdk](/caf-sdk/react-native/migrating-from-cafsdk.md).

### @caf.io/react-native-sdk\@5.2.0

#### Release date

* 08-14-2026

#### Highlights

* **Android 16 compatibility:** Updated React Native module to support Android 16 (`compileSdk` / `targetSdk` 36).

#### Fixes

* **Face Liveness:** Fixed Payface flow reporting success on validation failure.
* **Document Detector:** Fixed capture and upload issues on tablets and landscape devices.

Older release notes (5.1.0, 5.0.0, and below) are preserved in [Legacy Getting Started with the SDK](/caf-sdk/react-native/getting-started-with-the-sdk.md#release-notes).


---

# 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/react-native/changelog.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.