react-native-usesense 2.3.7 → 2.3.9

package/android/build.gradle

@@ -48,7 +48,18 @@ dependencies {
     // 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.
-    implementation "ai.usesense:sdk:4.6.6"
+    // 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.
+    // 4.7.0 is the floor: below it frames_manifest reported a hardcoded
+    // 640x480 regardless of what was captured. That is right for the legacy
+    // path but wrong for v4, which captures 1280x720, and the server now
+    // scales its screen-replay sharpness thresholds off that value, so
+    // under-reporting made spoof detection more permissive on the better
+    // capture path. 4.7.0 reports the real encoded size, caps frames at 960,
+    // gzips the metadata, raises the 30s upload write timeout to 300s, and
+    // emits real upload progress.
+    implementation "ai.usesense:sdk:4.7.1"
 
     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.7",
+  "version": "2.3.9",
   "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

@@ -33,5 +33,18 @@ Pod::Spec.new do |s|
   # 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.
-  s.dependency "UseSenseSDK", "~> 4.6.2"
+  # 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.
+  # 4.7.0 is the floor: below it the signals upload could not complete on a
+  # slow connection. Frames were encoded at the camera's full 1080x1920 with no
+  # downscale, so a session put 12.9 MB on the wire, against a 30s request
+  # timeout and a 120s URLSession resource timeout. A measured production
+  # session uploaded at 14.6 KB/s, so the transfer was cancelled every time and
+  # the subject just saw a spinner. 4.7.0 caps frames at 960, raises both
+  # timeouts to 300s, gzips the metadata, and emits real upload progress.
+  #
+  # Note `~> 4.7.0` means >= 4.7.0, < 4.8.0. The previous `~> 4.6.3` excluded
+  # 4.7.0 outright, so this pin has to be raised by hand for every native fix.
+  s.dependency "UseSenseSDK", "~> 4.7.1"
 end