smartcomply-web-sdk 1.0.91 → 1.0.93

package/dist/smartcomply.browser.js

@@ -5837,7 +5837,7 @@ var SmartComplySDK = (() => {
    * CDN tag they installed with (e.g. @1, which floats to the latest
    * matching release) actually resolved to the version they expect.
    */
-  _SmartComply.VERSION = "1.0.91";
+  _SmartComply.VERSION = "1.0.93";
   var SmartComply = _SmartComply;
 
   // src/flow/theme.ts
@@ -7883,6 +7883,7 @@ var SmartComplySDK = (() => {
         // legitimately need document_capture.
         info.failure_stage === "data_match") {
           this.selectedCountry = info.country || this.selectedCountry || "global";
+          this.identityCheckId = info.identity_check_id ?? null;
           return "liveness";
         }
         if (info.failure_stage === "document" && info.country && info.identifier_type) {
@@ -9052,7 +9053,20 @@ var SmartComplySDK = (() => {
               identifier,
               identifier_type: this.selectedIdType,
               country,
-              challenge_actions: ["BLINK"],
+              // Was hardcoded to ["BLINK"] only. This entry is reused for the
+              // liveness step later via existingEntryId (see liveness.ts's
+              // startCheck) — that reuse path builds a LOCAL stub object and
+              // never calls create() again, so whatever challenge_actions is
+              // sent HERE is what the backend permanently stores for this
+              // entry, regardless of what the widget actually challenges the
+              // user for afterward. A document-flow entry's liveness_challenges
+              // was stuck showing only BLINK even when the customer genuinely
+              // completed a full blink-and-motion scan, because the stored
+              // set never included TURN_HEAD to begin with. Match
+              // DEFAULT_CHALLENGE_ACTIONS so this is consistent with what the
+              // liveness step (SmartComplyFlow's other startCheck call) and
+              // the widget's own ActionDetector actually check for.
+              challenge_actions: [...DEFAULT_CHALLENGE_ACTIONS],
               document: blob,
               document_back: this.documentBackBlob || void 0,
               device_type: deviceMeta.device_type,