@smileid/usesmileid_huawei_face 12.3.1-SNAPSHOT.75 → 12.4.0

package/CHANGELOG.md

@@ -1,5 +1,10 @@
 Full release notes: [Smile ID docs](https://docs.usesmileid.com/developer-resources/sdks/mobile/release-notes/react-native-expo).
 
+## 12.4.0
+
+See the repository CHANGELOG for the 12.4.0 release notes.
+
+
 ## 12.3.0
 
 See the repository CHANGELOG for the 12.3.0 release notes.

package/README.md

@@ -10,13 +10,16 @@ Google Mobile Services (Huawei post-2019 hardware, etc.); use
 
 The native side runs the entire face-scan pipeline. This package
 contributes a Kotlin Expo Module that constructs
-`UseSmileIDFaceSession(HuaweiFaceDetectorAnalyzer())` against the Huawei
-HMS-backed analyzer in the `com.usesmileid:huawei-face` AAR, and a
+`UseSmileIDFaceSession(HuaweiFaceDetectorAnalyzer.forDevice(context))` against the
+Huawei HMS-backed analyzer in the `com.usesmileid:huawei-face` AAR, and a
 TS wrapper that bridges `configure / analyze / reset / close` with
 Zod-validated wire payloads.
 
 No ML logic is reimplemented in this package — it's a pure passthrough.
 
+On a phone without HMS Core the analyzer refuses before any HMS code runs, so the flow fails with
+`ML_ANALYZER_NOT_FOUND` rather than the app aborting on its first frame.
+
 ## Installation
 
 ```sh

package/android/build.gradle

@@ -17,7 +17,7 @@ plugins {
 }
 
 group = 'com.usesmileid.huawei.face'
-version = '12.3.0'
+version = '12.4.0'
 
 // HMS ML is published only to Huawei's own Maven repository — none of the
 // com.huawei.hms:ml-computer-vision-* artifacts exist on Maven Central. Expo
@@ -56,7 +56,7 @@ android {
   // android/build.gradle and the rest of the @expo/* modules.
   defaultConfig {
     versionCode 1
-    versionName '12.3.0'
+    versionName '12.4.0'
     // R8 keep-rules to bundle into partner apps that depend on this
     // module. Without these, R8 may rename the Expo module entry
     // point and the JS-bridged member functions, breaking autolinking.
@@ -69,7 +69,7 @@ dependencies {
   // kamera native core: the analyzer executor takes analysis frames from
   // kamera's KameraFrameHub so pixels never cross the JS bridge. Resolves from
   // Maven Central; a local publishToMavenLocal build wins (see kamera.md).
-  implementation 'com.usesmileid:kamera:1.2.1-20261027.034149-12'
+  implementation 'com.usesmileid:kamera:1.3.0'
 
   // The analyzer executor and frame storage every provider module shares, from the bridge module.
   implementation project(':smileid-usesmileid_bridge')
@@ -78,11 +78,14 @@ dependencies {
   // Targets Huawei AppGallery / no-GMS devices via HMS ML kit. The
   // Expo Module is a thin Kotlin shim that constructs the session
   // and bridges its four methods to JS via Expo Modules.
-  implementation 'com.usesmileid:huawei-face:12.3.0-20261027.143404-307'
+  implementation 'com.usesmileid:huawei-face:12.4.0'
   // The bridge build the bridge module ships. The provider's SDK artifact names its bridge too, and a
   // snapshot names the moving x.y.z-SNAPSHOT, so this keeps the provider compiling against the build
   // the app runs.
-  implementation 'com.usesmileid:bridge:12.3.0-20261027.143404-308'
+  implementation 'com.usesmileid:bridge:12.4.0'
+  // The device-check test is written against kotlin.test, which runs on JUnit 4 here, with a mocked context.
+  testImplementation 'org.jetbrains.kotlin:kotlin-test-junit'
+  testImplementation 'org.mockito:mockito-core:5.0.0'
 
 
 }

package/android/src/main/java/com/usesmileid/huawei/face/UseSmileIDHuaweiFaceModule.kt

@@ -1,12 +1,12 @@
 package com.usesmileid.huawei.face
 
+import android.content.Context
 import com.usesmileid.bridge.dsl.builder.FaceDetectorMode
 import com.usesmileid.bridge.huawei.face.HuaweiFaceDetectorAnalyzer
 import com.usesmileid.bridge.model.BoundingBox as NativeBoundingBox
 import com.usesmileid.bridge.model.CaptureReadyEvent as NativeCaptureReadyEvent
 import com.usesmileid.bridge.model.FaceDetectorOutput as NativeFaceOutput
 import com.usesmileid.bridge.model.HeadPoseResult
-import com.usesmileid.bridge.model.YuvFrame as NativeYuvFrame
 import com.usesmileid.bridge.registry.FaceAnalyzerFactoryRegistry
 import com.usesmileid.bridge.session.FaceScanConfig
 import com.usesmileid.bridge.session.UseSmileIDCaptureStep
@@ -26,7 +26,7 @@ import com.usesmileid.bridge.config.ThresholdConfig
 
 /**
  * Expo Module bridging the existing native session
- * `UseSmileIDFaceSession(HuaweiFaceDetectorAnalyzer())` (shipped in the
+ * `UseSmileIDFaceSession(HuaweiFaceDetectorAnalyzer.forDevice(context))` (shipped in the
  * `com.smileidentity:huawei-face` AAR) to the JS side. The Huawei
  * variant targets devices without Google Mobile Services and uses
  * Huawei HMS ML kit for face detection.
@@ -60,12 +60,6 @@ class UseSmileIDHuaweiFaceModule : Module() {
             )
         }
 
-        override suspend fun scan(
-            session: UseSmileIDFaceSession,
-            frame: NativeYuvFrame,
-            rotation: Int,
-        ): UseSmileIDFaceScanResult = session.scan(frame, rotation)
-
         override fun drainEvents(session: UseSmileIDFaceSession): List<NativeCaptureReadyEvent> =
             session.drainCaptureReadyEvents()
 
@@ -106,9 +100,10 @@ class UseSmileIDHuaweiFaceModule : Module() {
         Name("UseSmileIDHuaweiFace")
 
         OnCreate {
-            if (LinkedAnalyzers.has(KEY)) FaceAnalyzerFactoryRegistry.register(KEY) { HuaweiFaceDetectorAnalyzer() }
             val ctx = appContext.reactContext
                 ?: throw IllegalStateException("Module not attached to a React context")
+            val applicationContext = ctx.applicationContext
+            if (LinkedAnalyzers.has(KEY)) FaceAnalyzerFactoryRegistry.register(KEY) { huaweiFaceAnalyzerFor(applicationContext) }
             executor.onAttach(ctx)
 
         }
@@ -282,3 +277,10 @@ private fun NativeCaptureReadyEvent.toWireMap(): Map<String, Any?> = when (this)
         "url" to file.toURI().toString(),
     )
 }
+
+/**
+ * The HMS face analyzer built for this device: on a phone without HMS Core it refuses with
+ * `ML_ANALYZER_NOT_FOUND` before HMS's native code, which otherwise aborts the app on its first frame.
+ */
+internal fun huaweiFaceAnalyzerFor(context: Context): HuaweiFaceDetectorAnalyzer =
+    HuaweiFaceDetectorAnalyzer.forDevice(context)

package/dist/index.d.ts

@@ -4,7 +4,7 @@ import type { FaceConfig, FaceScanResult } from "@smileid/usesmileid_bridge";
  * Google Mobile Services).
  *
  * Thin shim around the existing native session
- * `com.usesmileid.bridge.session.UseSmileIDFaceSession(HuaweiFaceDetectorAnalyzer())`
+ * `com.usesmileid.bridge.session.UseSmileIDFaceSession(HuaweiFaceDetectorAnalyzer.forDevice(context))`
  * shipped in the `com.smileidentity:huawei-face` AAR. The native side
  * runs the entire pipeline (analyzer + validator + transitioner +
  * state machine); this TS layer routes calls and validates wire

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@smileid/usesmileid_huawei_face",
-  "version": "12.3.1-SNAPSHOT.75",
+  "version": "12.4.0",
   "description": "Huawei HMS face detection implementation for the UseSmileID React Native (Expo) SDK.",
   "homepage": "https://usesmileid.com",
   "repository": {
@@ -47,8 +47,8 @@
     "CHANGELOG.md"
   ],
   "dependencies": {
-    "@smileid/usesmileid_platform_interface": "12.3.1-SNAPSHOT.75",
-    "@smileid/usesmileid_bridge": "12.3.1-SNAPSHOT.75"
+    "@smileid/usesmileid_bridge": "12.4.0",
+    "@smileid/usesmileid_platform_interface": "12.4.0"
   },
   "peerDependencies": {
     "expo": ">=56.0.0",
@@ -58,7 +58,7 @@
   "devDependencies": {
     "@types/node": "^26.6.4",
     "expo": "~57.0.26",
-    "expo-modules-core": "^57.0.23",
+    "expo-modules-core": "^57.0.24",
     "react-native": "^0.86.3",
     "typescript": "^6.0.3"
   },