react-native-acoustic-connect-beta 19.0.24 → 19.0.26

package/CHANGELOG.md

@@ -1,3 +1,13 @@
+## 19.0.26 (2026-09-11)
+
+### Reverts
+
+* Revert "Beta ReactNativeConnect build: 18.0.36" ([609ad7d](https://github.com/aipoweredmarketer/react-native-acoustic-connect-beta/commit/609ad7d3244ec06f27dced5864d40585c5b3c9cf))
+## 19.0.25 (2026-09-11)
+
+### Reverts
+
+* Revert "Beta ReactNativeConnect build: 18.0.36" ([609ad7d](https://github.com/aipoweredmarketer/react-native-acoustic-connect-beta/commit/609ad7d3244ec06f27dced5864d40585c5b3c9cf))
 ## 19.0.24 (2026-09-11)
 
 ### Reverts

package/README.md

@@ -473,23 +473,22 @@ const pageView: SignalValues = {
 AcousticConnectRN.logSignal(pageView, 1)
 ```
 
-> **Android: send numbers nested, not at the top level.** The Android SDK's
-> signal serializer carries strings, booleans, objects and arrays at the top
-> level of the payload but drops a top-level numeric value. Numbers nested
-> inside an object or array are unaffected. iOS carries top-level numbers
-> normally, so put numbers one level down when you need both platforms to agree:
+> **Android: top-level numbers need Connect Android 11.0.24-beta or newer.**
+> Android's signal serializer gained a number branch in Connect Android
+> **11.0.24-beta**; from that version a top-level numeric value is carried, the
+> same as on iOS. Earlier versions carried strings, booleans, objects and arrays
+> at the top level but dropped a top-level number. Numbers nested inside an
+> object or array were never affected on either platform.
+>
+> Both versions sit inside the `[11.0.11, 12.0.0)` range this package accepts,
+> and the Android dependency floats to the newest published build unless you pin
+> it, so most integrations get the new behaviour. Nest the number if you pin an
+> older one:
 >
 > ```ts
-> AcousticConnectRN.logSignal({ cart: { items: 3 } }, 1) // both platforms
-> AcousticConnectRN.logSignal({ items: 3 }, 1)           // iOS only
+> AcousticConnectRN.logSignal({ cart: { items: 3 } }, 1) // any supported version
+> AcousticConnectRN.logSignal({ items: 3 }, 1)           // iOS, + Android 11.0.24-beta and newer
 > ```
->
-> The Android bridge logs a warning naming the keys the SDK is about to
-> discard, so the loss shows up in `logcat` instead of only in a dashboard
-> that never fills in. It does not coerce the value: making the number survive
-> as a JSON string would replace a missing field with a differently-typed one
-> and diverge from iOS in a new way. The fix belongs in the Android SDK's
-> serializer.
 
 ### `AcousticConnectRN.logCustomEvent(eventName, values, level): boolean`
 
@@ -758,7 +757,21 @@ instead — each call captures the layout as it stands at that moment.
 Leaving the block out entirely gives you 500 ms as well. That is the wrapper's
 default, chosen so both platforms behave the same; the native SDKs' own bundled
 defaults differ from each other and are tuned for the lifecycle trigger rather
-than the React Navigation one.
+than the React Navigation one. Internally, omitting the second argument to
+`TLTRN.logScreenLayout` sends a sentinel (`-1`) that both bridges resolve to
+this configured value; any value the caller passes explicitly (`>= 0`) is used
+as-is instead, bypassing the config lookup for that one call.
+
+A near-zero value is not a request for faster captures. On iOS the
+auto-instrumentation capture is triggered off the view-controller lifecycle,
+and a delay close to `0` lets that trigger re-fire against the same screen far
+faster than the app can settle — hundreds of captures within a couple of
+hundred milliseconds while the app just sits idle, rather than one per actual
+transition. The visible symptom is a runaway capture loop: a "Refreshing…"
+indicator that stays up continuously instead of the brief one after a normal
+transition. The SDK enforces no floor on this value, so `1` (millisecond) is
+accepted and is exactly what produces the loop. Keep `CaptureLayoutDelay` at
+`500` or raise it per screen — never lower it toward `0`.
 
 #### Where screen-view and layout messages come from, and how to reduce duplicates
 

package/android/src/main/assets/ConnectBasicConfig.properties

@@ -1,4 +1,4 @@
-#Fri Sep 11 08:15:03 GMT 2026
+#Fri Sep 11 16:19:04 GMT 2026
 UseWhiteList=true
 PrintScreen=3
 UseRandomSample=false

package/android/src/main/java/com/acousticconnectrn/HybridAcousticConnectRN.kt

@@ -1481,35 +1481,26 @@ class HybridAcousticConnectRN : HybridAcousticConnectRNSpec(),
      *
      * The rebuild is mandatory, not cosmetic. The SDK serializes the signal
      * through EOCore's `JsonUtil.getHashValues`, which walks the top-level
-     * entries and accumulates only `String`, `Boolean`, `JSONObject`,
-     * `JSONArray` and `ByteArray` — anything else is **silently dropped**. So
-     * a nested `Map`/`List` handed over as-is would vanish from the emitted
-     * signal without any error. Converting here is what makes nested payloads
-     * survive the wire.
+     * entries and accumulates only `String`, `Boolean`, `Number` (from Connect
+     * Android 11.0.24-beta), `JSONObject`, `JSONArray` and `ByteArray` —
+     * anything else is **silently dropped**. So a nested `Map`/`List` handed
+     * over as-is would vanish from the emitted signal without any error.
+     * Converting here is what makes nested payloads survive the wire.
      *
      * `null` becomes [JSONObject.NULL] rather than a Kotlin `null`, which
      * `org.json` requires for an explicit JSON `null`.
      *
-     * Known limitation: a **top-level** numeric value is still dropped, and
-     * cannot be rescued from here. `Signal.getJSON()` serializes the payload
-     * through EOCore's `JsonUtil.getHashValues`, whose `instanceof` ladder has
-     * no `Number` branch, so the entry is skipped with no error. Numbers nested
-     * inside an object or array are unaffected — the enclosing
-     * [JSONObject]/[JSONArray] is built here, so `org.json` serializes them
-     * normally. iOS carries top-level numbers fine; this is an SDK-side
-     * asymmetry, pre-dating this conversion.
-     *
-     * Two non-fixes, so they are not attempted again: coercing the number to a
-     * [String] would make it survive as a JSON string, diverging from iOS's
-     * JSON number in a *new* way and silently changing the shape of data
-     * already-shipping clients receive; and there is no `org.json` wrapper that
-     * `getHashValues` accepts and that serializes as a bare number, so the
-     * shape cannot be preserved either. The real fix is a `Number` branch in
-     * `getHashValues` (Android SDK).
-     *
-     * What this method does do is [warnAboutDroppedTopLevelNumbers] — name the
-     * keys the SDK is about to discard, so the loss is visible in logcat
-     * instead of silent.
+     * Version boundary — **top-level** numbers. `getHashValues` gained a
+     * `Number` branch in Connect Android 11.0.24-beta and accumulates the boxed
+     * value as-is, so a top-level number now reaches the wire. On earlier builds
+     * its `instanceof` ladder had no such branch, the entry was skipped with no
+     * error, and nothing here could rescue it. Numbers nested inside an object
+     * or array were never affected — the enclosing [JSONObject]/[JSONArray] is
+     * built here, so `org.json` serializes them normally — and iOS has always
+     * carried top-level numbers. Both sides of the boundary sit inside the
+     * `[11.0.11, 12.0.0)` range this bridge accepts, so an integration pinning
+     * an older Connect version still sees the old behaviour; nesting a number
+     * is portable across the whole range.
      *
      * A [JSONException] aborts the whole payload rather than escaping to the
      * caller. Non-finite numbers are the case that raises it: `org.json`
@@ -1536,44 +1527,9 @@ class HybridAcousticConnectRN : HybridAcousticConnectRNSpec(),
             Log.w(TAG, "[bridge] logSignal payload is not representable as JSON — dropping it: ${e.message}")
             return HashMap()
         }
-        warnAboutDroppedTopLevelNumbers(map)
         return map
     }
 
-    /**
-     * Logs a warning naming the top-level numeric keys that the SDK's signal
-     * serializer will discard (see [toSignalPayload] for why it does).
-     *
-     * The point is purely to stop the loss being silent. Before this, a JS
-     * `logSignal({ orderTotal: 24.99 })` returned `true`, emitted a type-21
-     * message, and simply had no `orderTotal` in it — indistinguishable, from
-     * the caller's side, from a signal that arrived intact. The same call on
-     * iOS carries the value, so a cross-platform dashboard shows the metric
-     * populated on one platform and empty on the other with nothing anywhere
-     * to explain it.
-     *
-     * Iterates the already-converted map so it reflects exactly what is handed
-     * to the SDK. Booleans and strings are not mentioned: `getHashValues`
-     * accumulates both.
-     *
-     * @param payload The converted payload, as returned to `logSignal`.
-     */
-    private fun warnAboutDroppedTopLevelNumbers(payload: Map<String?, Any?>) {
-        val dropped = payload.entries
-            .filter { it.value is Number }
-            .mapNotNull { it.key }
-        if (dropped.isEmpty()) {
-            return
-        }
-        Log.w(
-            TAG,
-            "[bridge] logSignal: top-level numeric value(s) ${dropped.sorted()} will be dropped by the " +
-                "Android SDK's signal serializer, which accumulates only strings, booleans and nested " +
-                "JSON. iOS sends them. Nest the value under an object to carry it on both platforms, " +
-                "e.g. { cart: { total: 24.99 } } instead of { total: 24.99 }."
-        )
-    }
-
     /**
      * Recursive helper for [toSignalPayload]. Maps Kotlin containers onto their
      * `org.json` equivalents and leaves scalars alone.
@@ -1603,12 +1559,15 @@ class HybridAcousticConnectRN : HybridAcousticConnectRNSpec(),
                 for (element in value) put(toJsonValue(element))
             }
             // Checked here rather than left to `org.json`. A non-finite number
-            // nested in an object or array would be rejected by that container's
+            // nested in an object or array is rejected by that container's
             // `put`, but a TOP-LEVEL one is only ever handed to `HashMap.put`,
             // which accepts anything — so without this the payload would reach
-            // the SDK and lose just that one key, while the nested case loses
-            // the whole payload. Raising it uniformly keeps the two consistent
-            // and matches iOS, where one non-finite value fails
+            // the SDK, and what happened there would depend on the resolved
+            // Connect version: before 11.0.24-beta it lost just that one key
+            // while the nested case lost everything; from 11.0.24-beta the
+            // SDK's own `Number` branch rejects it and drops the whole payload.
+            // Raising it here keeps the two cases consistent across the
+            // supported range and matches iOS, where one non-finite value fails
             // `isValidJSONObject:` for the entire signal.
             is Double -> if (value.isFinite()) {
                 value

package/lib/typescript/src/specs/react-native-acoustic-connect.nitro.d.ts

@@ -179,16 +179,17 @@ export interface AcousticConnectRN extends HybridObject<{
      *   logcat / os_log.
      *
      * @remarks
-     * **Android limitation — top-level numbers.** The Android SDK's
-     * `JsonUtil.getHashValues` serialises only `String`, `Boolean`,
+     * **Android version boundary — top-level numbers.** The Android SDK's
+     * `JsonUtil.getHashValues` gained a `Number` branch in Connect Android
+     * **11.0.24-beta**, so from that version a top-level numeric value is
+     * carried. Earlier versions serialised only `String`, `Boolean`,
      * `JSONObject`, `JSONArray` and `byte[]` at the top level of the signal
-     * map; a top-level numeric value is dropped. Numbers nested *inside* an
-     * object or array are unaffected, because the bridge builds those
-     * `JSONObject`/`JSONArray` values itself. iOS carries top-level numbers
-     * normally. Send numbers inside a nested object when cross-platform
-     * parity matters. This is a pre-existing SDK-side gap, not a
-     * restriction of this bridge — the Android bridge now names the affected
-     * keys in a logcat warning so the loss is not silent.
+     * map and dropped a top-level number. Numbers nested *inside* an object
+     * or array were never affected, because the bridge builds those
+     * `JSONObject`/`JSONArray` values itself, and iOS has always carried
+     * top-level numbers normally. Both versions sit inside the
+     * `[11.0.11, 12.0.0)` range this package accepts, so nest the number if
+     * your integration pins a Connect Android version below 11.0.24-beta.
      *
      * @example Nested payload
      * ```ts

package/lib/typescript/src/specs/react-native-acoustic-connect.nitro.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"react-native-acoustic-connect.nitro.d.ts","sourceRoot":"","sources":["../../../../src/specs/react-native-acoustic-connect.nitro.ts"],"names":[],"mappings":"AAYA,OAAO,EAAE,KAAK,MAAM,EAAE,KAAK,YAAY,EAAE,MAAM,4BAA4B,CAAA;AAG3E,MAAM,MAAM,cAAc,GAAG;IACzB,WAAW,EAAE,MAAM,CAAC;IACpB,CAAC,GAAG,EAAE,MAAM,GAAG,OAAO,CAAC;CAC1B,CAAC;AAEF;;;;;;;;;;;;;;;;;;;;;;;GAuBG;AACH,MAAM,MAAM,YAAY,GAAG,MAAM,CAAA;AAEjC,MAAM,MAAM,0BAA0B,GAAG,QAAQ,GAAG,iBAAiB,GAAG,MAAM,CAAA;AAE9E;;;;;;GAMG;AACH,MAAM,WAAW,aAAa;IAC1B,oEAAoE;IACpE,IAAI,CAAC,EAAE,MAAM,CAAA;IACb,wEAAwE;IACxE,MAAM,CAAC,EAAE,MAAM,CAAA;IACf,gFAAgF;IAChF,OAAO,EAAE,MAAM,CAAA;CAClB;AAED;;;;;;;;GAQG;AACH,MAAM,WAAW,oBAAoB;IACjC,gEAAgE;IAChE,OAAO,EAAE,OAAO,CAAA;IAChB,4EAA4E;IAC5E,KAAK,CAAC,EAAE,MAAM,GAAG,IAAI,CAAA;CACxB;AAED,MAAM,WAAW,iBAAkB,SAAQ,YAAY,CAAC;IAAE,GAAG,EAAE,OAAO,CAAC;IAAC,OAAO,EAAE,QAAQ,CAAA;CAAE,CAAC;IACxF;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;OAwCG;IACH,MAAM,IAAI,OAAO,CAAA;IAEjB;;;;;;;;;;;;;;;;;;OAkBG;IACH,OAAO,IAAI,OAAO,CAAA;IAClB,0BAA0B,CAAC,GAAG,EAAE,MAAM,EAAE,KAAK,EAAE,OAAO,EAAE,UAAU,EAAE,MAAM,GAAG,OAAO,CAAA;IACpF,mBAAmB,CAAC,GAAG,EAAE,MAAM,EAAE,KAAK,EAAE,MAAM,EAAE,UAAU,EAAE,MAAM,GAAG,OAAO,CAAA;IAC5E,mBAAmB,CAAC,GAAG,EAAE,MAAM,EAAE,KAAK,EAAE,MAAM,EAAE,UAAU,EAAE,MAAM,GAAG,OAAO,CAAA;IAC5E,mBAAmB,CAAC,GAAG,EAAE,MAAM,EAAE,KAAK,EAAE,MAAM,GAAG,MAAM,GAAG,OAAO,EAAE,UAAU,EAAE,MAAM,GAAG,OAAO,CAAA;IAC/F,0BAA0B,CAAC,UAAU,EAAE,OAAO,EAAE,GAAG,EAAE,MAAM,EAAE,UAAU,EAAE,MAAM,GAAG,OAAO,CAAA;IACzF,mBAAmB,CAAC,UAAU,EAAE,MAAM,EAAE,GAAG,EAAE,MAAM,EAAE,UAAU,EAAE,MAAM,GAAI,MAAM,GAAG,IAAI,GAAG,SAAS,CAAA;IACpG,mBAAmB,CAAC,UAAU,EAAE,MAAM,EAAE,GAAG,EAAE,MAAM,EAAE,UAAU,EAAE,MAAM,GAAG,MAAM,CAAA;IAChF;;;;;;;;;;;;;;;;;;;;;OAqBG;IACH,cAAc,CAAC,SAAS,EAAE,MAAM,EAAE,MAAM,EAAE,MAAM,CAAC,MAAM,EAAE,MAAM,GAAG,MAAM,GAAG,OAAO,CAAC,EAAE,KAAK,EAAE,MAAM,GAAG,OAAO,CAAA;IAE5G;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;OAsDG;IACH,SAAS,CAAC,MAAM,EAAE,YAAY,EAAE,KAAK,EAAE,MAAM,GAAG,OAAO,CAAA;IACvD,iBAAiB,CAAC,OAAO,EAAE,MAAM,EAAE,SAAS,EAAE,MAAM,EAAE,SAAS,EAAE,OAAO,GAAG,OAAO,CAAA;IAClF,WAAW,IAAI,OAAO,CAAA;IACtB,gCAAgC,CAAC,QAAQ,EAAE,MAAM,EAAE,SAAS,EAAE,MAAM,EAAE,KAAK,EAAE,MAAM,GAAG,OAAO,CAAA;IAC7F,aAAa,CAAC,MAAM,EAAE,MAAM,EAAE,SAAS,EAAE,MAAM,GAAG,OAAO,CAAA;IACzD,kBAAkB,CAAC,MAAM,EAAE,MAAM,EAAE,SAAS,EAAE,MAAM,EAAE,IAAI,EAAE,MAAM,GAAG,IAAI,GAAG,SAAS,GAAG,OAAO,CAAA;IAC/F,oBAAoB,CAAC,eAAe,EAAE,MAAM,GAAG,OAAO,CAAA;IACtD,wBAAwB,CAAC,eAAe,EAAE,MAAM,GAAG,IAAI,GAAG,SAAS,EAAE,QAAQ,EAAC,MAAM,GAAG,IAAI,GAAG,SAAS,GAAG,OAAO,CAAA;IACjH,0BAA0B,CAAC,eAAe,EAAE,MAAM,GAAG,IAAI,GAAG,SAAS,EAAE,QAAQ,EAAC,MAAM,GAAG,IAAI,GAAG,SAAS,GAAG,OAAO,CAAA;IACnH;;;;;;;;;;;;;;;;;;OAkBG;IACH,eAAe,CAAC,IAAI,EAAE,MAAM,EAAE,KAAK,EAAE,MAAM,GAAG,OAAO,CAAA;IAErD,kBAAkB,CAAC,QAAQ,EAAE,MAAM,EAAE,WAAW,EAAE,MAAM,EAAE,UAAU,EAAE,MAAM,GAAG,OAAO,CAAA;IACtF,qBAAqB,CAAC,QAAQ,EAAE,MAAM,EAAE,aAAa,EAAE,MAAM,GAAG,OAAO,CAAA;IACvE,yBAAyB,CAAC,QAAQ,EAAE,MAAM,EAAE,UAAU,EAAE,MAAM,EAAE,WAAW,EAAE,MAAM,GAAG,OAAO,CAAA;IAC7F;;;;;;OAMG;IACH,oBAAoB,CAAC,QAAQ,EAAE,MAAM,EAAE,SAAS,EAAE,MAAM,EAAE,MAAM,EAAE,MAAM,CAAC,MAAM,EAAE,MAAM,GAAG,MAAM,GAAG,OAAO,CAAC,GAAG,OAAO,CAAA;IAErH;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;OA6EG;IACH,WAAW,CACP,cAAc,EAAE,MAAM,EACtB,eAAe,EAAE,MAAM,EACvB,UAAU,CAAC,EAAE,MAAM,EACnB,oBAAoB,CAAC,EAAE,MAAM,CAAC,MAAM,EAAE,MAAM,CAAC,GAC9C,OAAO,CAAC,OAAO,CAAC,CAAA;IAUnB;;;;;;;;;;;OAWG;IACH,wBAAwB,CAAC,WAAW,EAAE,WAAW,GAAG,OAAO,CAAC,OAAO,CAAC,CAAA;IAEpE;;;;;;OAMG;IACH,qBAAqB,CAAC,KAAK,EAAE,aAAa,GAAG,OAAO,CAAC,OAAO,CAAC,CAAA;IAE7D;;;;;;;;;;;;;OAaG;IACH,0BAA0B,CAAC,QAAQ,EAAE,MAAM,CAAC,MAAM,EAAE,MAAM,GAAG,MAAM,GAAG,OAAO,CAAC,GAAG,OAAO,CAAC,OAAO,CAAC,CAAA;IAEjG;;;;;;;;;;;OAWG;IACH,sBAAsB,CAAC,gBAAgB,EAAE,MAAM,EAAE,QAAQ,EAAE,MAAM,CAAC,MAAM,EAAE,MAAM,GAAG,MAAM,GAAG,OAAO,CAAC,GAAG,OAAO,CAAC,OAAO,CAAC,CAAA;IAIvH;;;;;;;;;;;;;OAaG;IACH,2BAA2B,CAAC,OAAO,EAAE,OAAO,GAAG,IAAI,EAAE,KAAK,CAAC,EAAE,aAAa,GAAG,OAAO,CAAC,OAAO,CAAC,CAAA;IAE7F;;;;;;;OAOG;IACH,qBAAqB,IAAI,OAAO,CAAC,oBAAoB,CAAC,CAAA;IAEtD;;;;OAIG;IACH,sBAAsB,IAAI,OAAO,CAAC,OAAO,GAAG,IAAI,CAAC,CAAA;CACpD"}
+{"version":3,"file":"react-native-acoustic-connect.nitro.d.ts","sourceRoot":"","sources":["../../../../src/specs/react-native-acoustic-connect.nitro.ts"],"names":[],"mappings":"AAYA,OAAO,EAAE,KAAK,MAAM,EAAE,KAAK,YAAY,EAAE,MAAM,4BAA4B,CAAA;AAG3E,MAAM,MAAM,cAAc,GAAG;IACzB,WAAW,EAAE,MAAM,CAAC;IACpB,CAAC,GAAG,EAAE,MAAM,GAAG,OAAO,CAAC;CAC1B,CAAC;AAEF;;;;;;;;;;;;;;;;;;;;;;;GAuBG;AACH,MAAM,MAAM,YAAY,GAAG,MAAM,CAAA;AAEjC,MAAM,MAAM,0BAA0B,GAAG,QAAQ,GAAG,iBAAiB,GAAG,MAAM,CAAA;AAE9E;;;;;;GAMG;AACH,MAAM,WAAW,aAAa;IAC1B,oEAAoE;IACpE,IAAI,CAAC,EAAE,MAAM,CAAA;IACb,wEAAwE;IACxE,MAAM,CAAC,EAAE,MAAM,CAAA;IACf,gFAAgF;IAChF,OAAO,EAAE,MAAM,CAAA;CAClB;AAED;;;;;;;;GAQG;AACH,MAAM,WAAW,oBAAoB;IACjC,gEAAgE;IAChE,OAAO,EAAE,OAAO,CAAA;IAChB,4EAA4E;IAC5E,KAAK,CAAC,EAAE,MAAM,GAAG,IAAI,CAAA;CACxB;AAED,MAAM,WAAW,iBAAkB,SAAQ,YAAY,CAAC;IAAE,GAAG,EAAE,OAAO,CAAC;IAAC,OAAO,EAAE,QAAQ,CAAA;CAAE,CAAC;IACxF;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;OAwCG;IACH,MAAM,IAAI,OAAO,CAAA;IAEjB;;;;;;;;;;;;;;;;;;OAkBG;IACH,OAAO,IAAI,OAAO,CAAA;IAClB,0BAA0B,CAAC,GAAG,EAAE,MAAM,EAAE,KAAK,EAAE,OAAO,EAAE,UAAU,EAAE,MAAM,GAAG,OAAO,CAAA;IACpF,mBAAmB,CAAC,GAAG,EAAE,MAAM,EAAE,KAAK,EAAE,MAAM,EAAE,UAAU,EAAE,MAAM,GAAG,OAAO,CAAA;IAC5E,mBAAmB,CAAC,GAAG,EAAE,MAAM,EAAE,KAAK,EAAE,MAAM,EAAE,UAAU,EAAE,MAAM,GAAG,OAAO,CAAA;IAC5E,mBAAmB,CAAC,GAAG,EAAE,MAAM,EAAE,KAAK,EAAE,MAAM,GAAG,MAAM,GAAG,OAAO,EAAE,UAAU,EAAE,MAAM,GAAG,OAAO,CAAA;IAC/F,0BAA0B,CAAC,UAAU,EAAE,OAAO,EAAE,GAAG,EAAE,MAAM,EAAE,UAAU,EAAE,MAAM,GAAG,OAAO,CAAA;IACzF,mBAAmB,CAAC,UAAU,EAAE,MAAM,EAAE,GAAG,EAAE,MAAM,EAAE,UAAU,EAAE,MAAM,GAAI,MAAM,GAAG,IAAI,GAAG,SAAS,CAAA;IACpG,mBAAmB,CAAC,UAAU,EAAE,MAAM,EAAE,GAAG,EAAE,MAAM,EAAE,UAAU,EAAE,MAAM,GAAG,MAAM,CAAA;IAChF;;;;;;;;;;;;;;;;;;;;;OAqBG;IACH,cAAc,CAAC,SAAS,EAAE,MAAM,EAAE,MAAM,EAAE,MAAM,CAAC,MAAM,EAAE,MAAM,GAAG,MAAM,GAAG,OAAO,CAAC,EAAE,KAAK,EAAE,MAAM,GAAG,OAAO,CAAA;IAE5G;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;OAuDG;IACH,SAAS,CAAC,MAAM,EAAE,YAAY,EAAE,KAAK,EAAE,MAAM,GAAG,OAAO,CAAA;IACvD,iBAAiB,CAAC,OAAO,EAAE,MAAM,EAAE,SAAS,EAAE,MAAM,EAAE,SAAS,EAAE,OAAO,GAAG,OAAO,CAAA;IAClF,WAAW,IAAI,OAAO,CAAA;IACtB,gCAAgC,CAAC,QAAQ,EAAE,MAAM,EAAE,SAAS,EAAE,MAAM,EAAE,KAAK,EAAE,MAAM,GAAG,OAAO,CAAA;IAC7F,aAAa,CAAC,MAAM,EAAE,MAAM,EAAE,SAAS,EAAE,MAAM,GAAG,OAAO,CAAA;IACzD,kBAAkB,CAAC,MAAM,EAAE,MAAM,EAAE,SAAS,EAAE,MAAM,EAAE,IAAI,EAAE,MAAM,GAAG,IAAI,GAAG,SAAS,GAAG,OAAO,CAAA;IAC/F,oBAAoB,CAAC,eAAe,EAAE,MAAM,GAAG,OAAO,CAAA;IACtD,wBAAwB,CAAC,eAAe,EAAE,MAAM,GAAG,IAAI,GAAG,SAAS,EAAE,QAAQ,EAAC,MAAM,GAAG,IAAI,GAAG,SAAS,GAAG,OAAO,CAAA;IACjH,0BAA0B,CAAC,eAAe,EAAE,MAAM,GAAG,IAAI,GAAG,SAAS,EAAE,QAAQ,EAAC,MAAM,GAAG,IAAI,GAAG,SAAS,GAAG,OAAO,CAAA;IACnH;;;;;;;;;;;;;;;;;;OAkBG;IACH,eAAe,CAAC,IAAI,EAAE,MAAM,EAAE,KAAK,EAAE,MAAM,GAAG,OAAO,CAAA;IAErD,kBAAkB,CAAC,QAAQ,EAAE,MAAM,EAAE,WAAW,EAAE,MAAM,EAAE,UAAU,EAAE,MAAM,GAAG,OAAO,CAAA;IACtF,qBAAqB,CAAC,QAAQ,EAAE,MAAM,EAAE,aAAa,EAAE,MAAM,GAAG,OAAO,CAAA;IACvE,yBAAyB,CAAC,QAAQ,EAAE,MAAM,EAAE,UAAU,EAAE,MAAM,EAAE,WAAW,EAAE,MAAM,GAAG,OAAO,CAAA;IAC7F;;;;;;OAMG;IACH,oBAAoB,CAAC,QAAQ,EAAE,MAAM,EAAE,SAAS,EAAE,MAAM,EAAE,MAAM,EAAE,MAAM,CAAC,MAAM,EAAE,MAAM,GAAG,MAAM,GAAG,OAAO,CAAC,GAAG,OAAO,CAAA;IAErH;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;OA6EG;IACH,WAAW,CACP,cAAc,EAAE,MAAM,EACtB,eAAe,EAAE,MAAM,EACvB,UAAU,CAAC,EAAE,MAAM,EACnB,oBAAoB,CAAC,EAAE,MAAM,CAAC,MAAM,EAAE,MAAM,CAAC,GAC9C,OAAO,CAAC,OAAO,CAAC,CAAA;IAUnB;;;;;;;;;;;OAWG;IACH,wBAAwB,CAAC,WAAW,EAAE,WAAW,GAAG,OAAO,CAAC,OAAO,CAAC,CAAA;IAEpE;;;;;;OAMG;IACH,qBAAqB,CAAC,KAAK,EAAE,aAAa,GAAG,OAAO,CAAC,OAAO,CAAC,CAAA;IAE7D;;;;;;;;;;;;;OAaG;IACH,0BAA0B,CAAC,QAAQ,EAAE,MAAM,CAAC,MAAM,EAAE,MAAM,GAAG,MAAM,GAAG,OAAO,CAAC,GAAG,OAAO,CAAC,OAAO,CAAC,CAAA;IAEjG;;;;;;;;;;;OAWG;IACH,sBAAsB,CAAC,gBAAgB,EAAE,MAAM,EAAE,QAAQ,EAAE,MAAM,CAAC,MAAM,EAAE,MAAM,GAAG,MAAM,GAAG,OAAO,CAAC,GAAG,OAAO,CAAC,OAAO,CAAC,CAAA;IAIvH;;;;;;;;;;;;;OAaG;IACH,2BAA2B,CAAC,OAAO,EAAE,OAAO,GAAG,IAAI,EAAE,KAAK,CAAC,EAAE,aAAa,GAAG,OAAO,CAAC,OAAO,CAAC,CAAA;IAE7F;;;;;;;OAOG;IACH,qBAAqB,IAAI,OAAO,CAAC,oBAAoB,CAAC,CAAA;IAEtD;;;;OAIG;IACH,sBAAsB,IAAI,OAAO,CAAC,OAAO,GAAG,IAAI,CAAC,CAAA;CACpD"}

package/package.json

@@ -233,7 +233,7 @@
     "source": "src/index",
     "summary": "react-native ios android tealeaf connect cxa wxca er enhanced-replay",
     "types": "./lib/typescript/src/index.d.ts",
-    "version": "19.0.24",
+    "version": "19.0.26",
     "workspaces": [
         "example",
         "Examples/bare-workflow"

package/src/specs/react-native-acoustic-connect.nitro.ts

@@ -197,16 +197,17 @@ export interface AcousticConnectRN extends HybridObject<{ ios: 'swift', android:
      *   logcat / os_log.
      *
      * @remarks
-     * **Android limitation — top-level numbers.** The Android SDK's
-     * `JsonUtil.getHashValues` serialises only `String`, `Boolean`,
+     * **Android version boundary — top-level numbers.** The Android SDK's
+     * `JsonUtil.getHashValues` gained a `Number` branch in Connect Android
+     * **11.0.24-beta**, so from that version a top-level numeric value is
+     * carried. Earlier versions serialised only `String`, `Boolean`,
      * `JSONObject`, `JSONArray` and `byte[]` at the top level of the signal
-     * map; a top-level numeric value is dropped. Numbers nested *inside* an
-     * object or array are unaffected, because the bridge builds those
-     * `JSONObject`/`JSONArray` values itself. iOS carries top-level numbers
-     * normally. Send numbers inside a nested object when cross-platform
-     * parity matters. This is a pre-existing SDK-side gap, not a
-     * restriction of this bridge — the Android bridge now names the affected
-     * keys in a logcat warning so the loss is not silent.
+     * map and dropped a top-level number. Numbers nested *inside* an object
+     * or array were never affected, because the bridge builds those
+     * `JSONObject`/`JSONArray` values itself, and iOS has always carried
+     * top-level numbers normally. Both versions sit inside the
+     * `[11.0.11, 12.0.0)` range this package accepts, so nest the number if
+     * your integration pins a Connect Android version below 11.0.24-beta.
      *
      * @example Nested payload
      * ```ts