Refresh of the Liveness SDK with the following improvements:

• Fixing issues that would result in the client getting stuck on "Hold still".
• Additional security improvements for the client.

To learn more on how the Liveness SDK versioning works and to evaluate how critical these updates are, please refer to the documentation here.

Refresh of the Liveness SDK with a few improvements:

• Upgrade gradle version on Android SDK to address compatibility issues.

To learn more on how the Liveness SDK versioning works and to evaluate how critical these updates are, please refer to the documentation here.

Refresh of the Liveness SDK with a few improvements:

• Added support for the client to route to government region endpoints.
• Improved UI responsiveness to provide smoother active user instructions.
• Optimized client logic to improve the user experience and reduce the need for retries during active checks.

To learn more on how the Liveness SDK versioning works and to evaluate how critical these updates are, please refer to the documentation here.

Refresh of the Liveness Web SDK with a few improvements:

• Several stability fixes for the Web SDK to reduce errors during initialization.
• New loading animation that will show up when network speeds are slow during initialization.
• Fixed several low memory related issues.

To learn more on how the Liveness SDK versioning works and to evaluate how critical these updates are, please refer to the documentation here.

Refresh of the Liveness SDK with a few improvements:

1. Several stability fixes across both Web and Mobile SDKs.
2. Customize branding and logo with Web SDK.

To learn more on how the Liveness SDK versioning works and to evaluate how critical these updates are, please refer to the documentation here.

Refresh of the Liveness SDK with a few improvements:

1. Several stability fixes across both Web and Mobile SDKs.

To learn more on how the Liveness SDK versioning works and to evaluate how critical these updates are, please refer to the documentation here.

Refresh of the Liveness SDK with a few improvements:

1. Several stability fixes across both Web and Mobile SDKs.

To learn more on how the Liveness SDK versioning works and to evaluate how critical these updates are, please refer to the documentation here.

Refresh of the Liveness SDK with a few improvements:

1. Several stability fixes across both Web and Mobile SDKs.
2. Improved stability of face tracking in edge cases.

To learn more on how the Liveness SDK versioning works and to evaluate how critical these updates are, please refer to the documentation here.

Introduces public wrapper SDKs in npm, Maven, and GitHub for easier updates, plus a new API for streamlined gated asset access in CI/CD.

In this release, we are introducing a significant improvement to how the Azure AI Vision Liveness SDK is distributed and integrated into your applications.

Starting with version 1.4.1, we are publishing a new public wrapper SDK for each supported platform. These wrapper SDKs are now hosted in widely used public package repositories—npm for JavaScript/Web, Maven Central for Android, and a GitHub repository for the iOS xcframework. By making the SDK available in these public locations, developers can take advantage of automated dependency monitoring tools to stay up to date with the latest releases. For example, you can enable GitHub Dependabot if your project is hosted on GitHub, or use Renovate to monitor updates across platforms such as GitHub, GitLab, Bitbucket, and Azure Repos.

While the SDK is now easier to obtain and keep updated, the gated assets required to compile it remain in place as part of the security model. However, we have made the access process much simpler. Previously, obtaining an access token required running a local script. In this version, you can instead retrieve the access token directly by calling the new Get Client Assets Access Token API. This API uses your Azure Face resource’s endpoint and API key, making it straightforward to integrate into automated CI/CD build pipelines without manual intervention.

Below are the updated reference links for each platform-specific SDK:

Swift (iOS)

• Artifacts: Azure AI Face UI SDK for iOS
• API Reference: AzureAIVisionFaceUI Reference
• Sample: iOS Sample

Kotlin/Java (Android)

• Artifacts: Maven Central - com.azure:azure-ai-vision-face-ui
• API Reference: azure-ai-vision-face-ui Reference
• Sample: Android Sample

JavaScript (Web)

• Artifacts: @azure/ai-vision-face-ui - npm
• API Reference: AzureAIVisionFaceUI Reference
• Sample: Web Sample
• Framework Support: Works with React (including Next.js), Vue.js, and Angular

We recommend that all developers update to this version to take advantage of the improved distribution model, easier CI/CD integration, and the ability to automate SDK update monitoring.

To learn more on how the Liveness SDK versioning works and to evaluate how critical these updates are, please refer to the documentation here.

Refresh of the Liveness SDK with a few improvements:

1. Optimizations to reduce time for session completion.
2. Fixes to reduce "No Face detected" errors during runtime.
3. Fixes bug in Web SDK for React framework.

To learn more on how the Liveness SDK versioning works and to evaluate how critical these updates are, please refer to the documentation here.