From 987159064010f34c799353b7fcab3e13b5922f66 Mon Sep 17 00:00:00 2001
From: GitHub Action <41898282+github-actions[bot]@users.noreply.github.com>
Date: Tue, 19 Nov 2024 16:30:41 +0000
Subject: [PATCH] Release 14.38.1

---
 CHANGELOG.md | 19 +++----------------
 README.md    | 22 ----------------------
 2 files changed, 3 insertions(+), 38 deletions(-)

diff --git a/CHANGELOG.md b/CHANGELOG.md
index 4637ef086..911e96633 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -4,29 +4,16 @@ All notable changes to this project will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/)
 and this project adheres to [Semantic Versioning](https://semver.org/).
 
-## 14.39.0 - 2024-11-18
-### Added
-- Warning to push usage of Studio token over SDK token and deprecation message
-- New accessible autocomplete component
-
-### Changed
-- adds smart caret false for OTP phone input
-
-### Removed
-- Removed debug log from production build
-
-### Fixed
-- Fix type exports
-- Provided A more descriptive error screen
-
 ## 14.38.0 - 2024-09-30
 ### Fixed
 - Fixed QR code from showing during re-connection phase
-- Fixed navigation bug related to consent in classic mode
+- Fix navigation bug related to consent in classic mode
 - Removed the 10s timeout for the loading of modules
 - Implement cross_device_url for enterprise clients
 - Removed redundant video upload in document capture
 - add side, issuing_country and type to the video upload
+- Removed redundant video upload in document capture
+- add side, issuing_country and type to the video upload
 
 ## 14.37.1 - 2024-09-19
 ### Fixed
diff --git a/README.md b/README.md
index dfb3678db..64e0b213d 100644
--- a/README.md
+++ b/README.md
@@ -1196,28 +1196,6 @@ The callbacks return a `FormData` object, including the information that the SDK
 }
 ```
 
-### Custom biometric token storage
-
-When using the decentralized authentication solution, by default the SDK manages biometric token storage, by storing it on local storage. The SDK also allows the clients to take control of the token lifecycle and exposes an callback to override the default implementation to read and write the token, so it can be stored on device, in cloud, in a keystore or on your premises.
-
-**Note** that by using the callback it will prevent the SDK to store the token.
-
-```typescript
-Onfido.init({
-	...
-  onBiometricTokenGenerated: (customerUserHash: string, biometricToken: string): void => {
-    // Called when new biometric token is generated during onboarding
-    // Use this callback to securely store the biometric token
-    // Please ensure that customerUserHash to biometricToken relationship is 1:1
-  },
-  onBiometricTokenRequested: (customerUserHash: string): Promise<string> => {
-    // Called when biometric token is requested during re-authentication
-    // Once you have the token, resolve the promise with it
-    return Promise.resolve('biometricToken')
-  }
-});
-```
-
 #### Uploading the media files to Onfido
 
 By default, this feature will prevent the request from being sent to Onfido, requiring you to [manually upload](https://documentation.onfido.com/api/latest#upload-document) the media files to Onfido from your backend for further processing.