react-native-usesense 2.3.6 → 2.3.8

package/android/build.gradle

@@ -44,7 +44,14 @@ dependencies {
     // the Play Integrity token request had no timeout and the signal upload
     // joined it unbounded, wedging the verification before a single request
     // was sent. mavenCentral() is already in the `repositories` block above.
-    implementation "ai.usesense:sdk:4.6.5"
+    // 4.6.6 is the floor: below it an upload that arrived incomplete was
+    // reported as `provider`, so the runner told a subject holding a perfectly
+    // good document that verification was "temporarily unavailable" and
+    // offered a retry that re-sent identical bytes.
+    // 4.6.7 is the floor: from it the runner reports whether the subject
+    // scanned the document or chose a file, so failure guidance can name an
+    // action they can actually take. Below it the server guesses from config.
+    implementation "ai.usesense:sdk:4.6.7"
 
     implementation "org.jetbrains.kotlin:kotlin-stdlib:${safeExtGet('kotlinVersion', '2.0.0')}"
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "react-native-usesense",
-  "version": "2.3.6",
+  "version": "2.3.8",
   "description": "React Native plugin for human presence verification. Wraps the native UseSense iOS and Android SDKs.",
   "main": "lib/commonjs/index.js",
   "module": "lib/module/index.js",

package/react-native-usesense.podspec

@@ -26,8 +26,15 @@ Pod::Spec.new do |s|
   # redaction result type with a completely different UseSenseConfig
   # init signature. See CHANGELOG [2.0.0] for the full rewrite
   # rationale.
-  # 4.6.1 is the floor: earlier 4.6.x tore the runner down on a failed
+  # 4.6.1 raised the floor: earlier 4.6.x tore the runner down on a failed
   # document upload, ejecting the subject mid-flow, and cancelling the
   # scanner or photo picker cancelled the whole verification.
-  s.dependency "UseSenseSDK", "~> 4.6.1"
+  # 4.6.2 is the floor: below it an upload that arrived incomplete was reported
+  # as `provider`, so the runner told a subject holding a perfectly good
+  # document that verification was "temporarily unavailable" and offered a
+  # retry that re-sent identical bytes.
+  # 4.6.3 is the floor: from it the runner reports whether the subject scanned
+  # the document or chose a file, so failure guidance can name an action they
+  # can actually take. Below it the server has to guess from the step config.
+  s.dependency "UseSenseSDK", "~> 4.6.3"
 end