Release Notes
Version 7.27.0
Release date: 09/25/2026
What's new
Automatic backend routing from the mobile token
The SDK now resolves the backend URL from the location carried in your mobile token, so each session is routed to the correct environment automatically. When the token does not carry a location, it falls back to the environment set by stage. No integration change is required.
Smoother result transition
The capture screen now stays on screen until the liveness result is delivered, removing the brief flash of your app between the capture finishing and the result arriving. No integration change is required.
Breaking changes
None. This version requires no changes to your integration.
Version 7.25.0
Release date: 09/08/2026
What's new
Immediate result after capture
The liveness result now reaches your listener as soon as the capture finishes, instead of waiting for the backend transaction call to complete. No code change is required — you keep handling the same events.
Breaking changes
None. This version requires no changes to your integration.
Version 7.23.0
Release date: 08/24/2026
What's new
Faster camera start with session pre-warming
The Liveness flow is now split into configure(), prewarm() and startLiveness(). Calling prewarm() while the user is still on the previous screen creates the Liveness session in the background, so the camera opens without waiting for the network.
prewarm() is optional — skip it and startLiveness() creates the session itself, exactly as before.
Breaking changes
startLiveness() no longer takes a Context or a CafLivenessConfig. Both move to the new configure() method, which you call once before starting.
startLiveness(context, config, listener)
configure(context, config) then startLiveness(listener)
—
prewarm() (new, optional)
configure(context: Context, config: CafLivenessConfig)stores the credentials and retains the application context. It makes no network request, so it is safe to call early.startLiveness(result: FaceLivenessLiteListener)now takes only the listener.Calling
startLiveness()withoutconfigure()deliversLivenessLiteEvent.Errorwith typeCONFIGURATION_EXCEPTION, and no request is made.The event callback is unchanged — your existing handling of
Success,Failure,Error,Cancelled,LoadingandLoadedkeeps working as is.release()now also discards any pre-warmed session. The configuration fromconfigure()is kept, so you can start again without reconfiguring.
Version 7.21.0
Release date: 08/07/2026
What's new
Customize the liveness screen
You can now brand the liveness screen through the new uiCustomization option in CafLivenessConfig. Colors, the app bar title, the logo and close icons, the font and the mask blur are all configurable. Every field is optional — anything you leave out keeps the default appearance, so existing integrations are unaffected.
Colors are color values (@ColorInt), not color resources — resolve resources with ContextCompat.getColor(...) before passing them. Icons and fonts are resource ids.
Version 7.18.0
Release date: 07/30/2026
What's new
Dynamic iProov service location
The SDK now follows the iProov SP provided by the backend. Server-side change — no integration changes required.
Signed response on failure
When a liveness attempt fails (for example, eyes closed or poor lighting), the SDK now also retrieves the transaction result and returns the signedResponse in the Failure event — previously available only on success. If the result can't be retrieved, an Error event is returned instead.
Breaking changes
The LivenessLiteEvent contract changed. Update your event handling:
Success(val response: String)
Success(val signedResponse: String)
Failure(type, description)
Failure(signedResponse, type, description)
Error(type, description)
Error(type, description, cause)
Success.responsewas renamed toSuccess.signedResponse.Failurenow includessignedResponse.Errornow includescause(the originatingThrowable).CafLivenessConfig.stagenow defaults toCafStage.PRODand no longer needs to be provided explicitly.
Last updated

