react-native-acoustic-connect-beta 19.1.6 → 19.1.7

package/AcousticConnectRN.podspec

@@ -52,7 +52,15 @@ iOSVersion = connectConfig["Connect"]["iOSVersion"]
 # `ConnectDelegateProxy`-swizzled `UNUserNotificationCenter` delegate path
 # the bridge relies on in `pushMode: 'automatic'`). 2.1.12 and older mis-wire
 # that path, so the floor is raised to guarantee the fix is present.
-sdkFloor = '>= 2.1.13'
+# 2.1.51 floor: the first AcousticConnectDebug build with every iOS fix this
+# release relies on. The bridge now captures the react-native-screens screen on
+# display, and the SDK stops sending a duplicate, self-referencing screen view
+# (from 2.1.44); an on-screen Alert.alert no longer re-posts the current screen
+# while screenshots are on (from 2.1.49); and React Native's dev loading banner
+# is no longer logged as a screen (2.1.51). Earlier builds still resolve and
+# compile, but keep those defects. Open-ended on purpose: 2.2.x and newer
+# satisfy it too.
+sdkFloor = '>= 2.1.51'
 dependencyRequirements = iOSVersion.to_s.empty? ? [sdkFloor] : [sdkFloor, iOSVersion]
 
 # Normalize Connect.PushEnabled to a STRICT boolean before writing the native

package/CHANGELOG.md

@@ -1,3 +1,8 @@
+## 19.1.7 (2026-10-06)
+
+### Reverts
+
+* Revert "Beta ReactNativeConnect build: 18.0.36" ([609ad7d](https://github.com/aipoweredmarketer/react-native-acoustic-connect-beta/commit/609ad7d3244ec06f27dced5864d40585c5b3c9cf))
 ## 19.1.6 (2026-10-01)
 
 ### Reverts

package/README.md

@@ -19,8 +19,8 @@ These requirements apply to SDK **19.1** and later. If your app is on React Nati
 - Node 20.19.4 or newer for RN 0.84–0.86. **RN 0.87 requires Node 22.13 or newer** (`^22.13.0 || ^24.3.0 || >= 26`) and will not install on Node 20 at all
 - JDK 17 or newer for Android builds — the same JDK React Native itself requires.
   The Android module compiles at Java 17; newer JDKs work.
-- iOS deployment target ≥ 15.1, AcousticConnect / AcousticConnectDebug pod ≥ 2.0.5
-- Android `minSdk` ≥ 26, `compileSdk` ≥ 35, `io.github.go-acoustic:connect` in `[11.0.11, 12.0.0)`
+- iOS deployment target ≥ 15.1, AcousticConnect / AcousticConnectDebug pod ≥ 2.1.51
+- Android `minSdk` ≥ 26, `compileSdk` ≥ 35, `io.github.go-acoustic:connect` in `[11.1.16-beta, 12.0.0)` (Connect Android 11.1 or newer)
 - **Expo SDK 56+ is supported** from 19.1 (Expo SDK 55 → use 19.0.x) via the bundled Expo Config Plugin —
   development builds only (Expo Go is not supported); see
   [Using with Expo SDK 56+](#using-with-expo-sdk-56).
@@ -537,14 +537,13 @@ AcousticConnectRN.logSignal(pageView, 1)
 > 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:
+> The Android versions in that note are below the `[11.1.16-beta, 12.0.0)` range this
+> package accepts, so every supported Android version carries a top-level number.
+> Nesting the number stays portable across both platforms:
 >
 > ```ts
 > AcousticConnectRN.logSignal({ cart: { items: 3 } }, 1) // any supported version
-> AcousticConnectRN.logSignal({ items: 3 }, 1)           // iOS, + Android 11.0.24-beta and newer
+> AcousticConnectRN.logSignal({ items: 3 }, 1)           // any supported version
 > ```
 
 ### `AcousticConnectRN.logCustomEvent(eventName, values, level): boolean`
@@ -996,15 +995,15 @@ that **changing `android.package` requires a clean prebuild**
 (`npx expo prebuild --platform android --clean`); an incremental prebuild keeps
 the stale `applicationId`.
 
-### iOS — `pod install` fails with `[Connect] requires AcousticConnect >= 2.0.5`
+### iOS — `pod install` fails with `[Connect] requires AcousticConnect >= 2.1.51`
 
 You've pinned an older `iOSVersion` in `ConnectConfig.json`. Bump it to a
-2.0.5+ release (or leave it empty for the newest available) and re-run
+2.1.51 or newer (or leave it empty for the newest available) and re-run
 `pod install`.
 
 ### Android — Gradle resolution fails on `io.github.go-acoustic:connect`
 
-The strict constraint at `[11.0.11, 12.0.0)` is rejecting your pin. Bump
+The strict constraint at `[11.1.16-beta, 12.0.0)` is rejecting your pin. Bump
 `AndroidVersion` in `ConnectConfig.json` to a release within that range (or
 leave it empty for the newest 11.x available). 12.x is intentionally outside
 the supported range pending compatibility validation — track that work

package/android/build.gradle

@@ -189,9 +189,19 @@ println "AcousticConnectRN: PushEnabled=$acousticPushEnabled, useRelease=$acoust
 // constraints below. Checked up front because the constraint cannot reject a
 // pin on its own: a strict range is itself a request for the newest version in
 // range, so an out-of-range pin was silently replaced by that version.
-def acousticMinVersion = [11, 0, 11]
+// The lower bound is the first published Connect Android build with everything
+// the bridge relies on: the Connect APIs it calls (`canTakeScreenShot`,
+// `getLayoutInfo`, `logDialogLayout`, from 11.1.1-beta), the screen-view fix
+// that logs a return to a screen after one that is not captured (11.1.13-beta),
+// and password fields captured as dots rather than as typed (11.1.16-beta).
+// Gradle orders `11.1.16-beta` below `11.1.16` (a `-beta` qualifier sorts before
+// the release with the same numbers), so the range admits the 11.1.16 release
+// and everything newer. The numeric pin check below ignores qualifiers, so it
+// compares against the bare [11, 1, 16].
+def acousticMinVersion = [11, 1, 16]
+def acousticMinVersionQualifier = '-beta'
 def acousticMaxVersionExclusive = [12, 0, 0]
-def acousticSupportedRange = "[${acousticMinVersion.join('.')}, ${acousticMaxVersionExclusive.join('.')})"
+def acousticSupportedRange = "[${acousticMinVersion.join('.')}${acousticMinVersionQualifier}, ${acousticMaxVersionExclusive.join('.')})"
 if (!acousticVersionPin.isEmpty()) {
   def m = acousticVersionPin =~ /^(\d+)\.(\d+)\.(\d+)/
   def compare = { a, b -> [a, b].transpose().collect { x, y -> x <=> y }.find { it != 0 } ?: 0 }
@@ -340,7 +350,7 @@ dependencies {
         strictly acousticSupportedRange
         if (!acousticVersionPin.isEmpty()) { prefer acousticVersionPin }
       }
-      because 'AcousticConnectRN requires Connect Android SDK in [11.0.11, 12.0.0). Bump the upper bound after validating compatibility with a new major.'
+      because "AcousticConnectRN requires Connect Android SDK in ${acousticSupportedRange} (the bridge uses Connect APIs added in 11.1). Bump the upper bound after validating compatibility with a new major."
     }
     implementation('io.github.go-acoustic:connect-push-fcm') {
       version {

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

@@ -1,4 +1,4 @@
-#Thu Oct 01 15:10:29 GMT 2026
+#Tue Oct 06 08:39:10 GMT 2026
 UseWhiteList=true
 PrintScreen=3
 UseRandomSample=false

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

@@ -1547,10 +1547,9 @@ class HybridAcousticConnectRN : HybridAcousticConnectRNSpec(),
      * 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.
+     * carried top-level numbers. Both sides of the boundary sit below the
+     * `[11.1.16-beta, 12.0.0)` range this bridge accepts, so every supported
+     * version carries a top-level number; nesting a number stays portable.
      *
      * A [JSONException] aborts the whole payload rather than escaping to the
      * caller. Non-finite numbers are the case that raises it: `org.json`

package/cli/ios/connect_pods.rb

@@ -7,7 +7,8 @@
 # app target and the push extensions (ConnectNSE / ConnectNCE) all link the SAME
 # SDK build:
 #   - useRelease => 'AcousticConnect', otherwise 'AcousticConnectDebug'
-#   - floor '>= 2.1.13' (push permission API + automatic-mode fix floor)
+#   - floor '>= 2.1.51' (screen-capture, alert and dev-banner fixes; includes the push permission API
+#     and automatic-mode fix)
 #   - optional exact pin via Connect.iOSVersion
 #
 # Usage from a Podfile (resolve the file the same way the RN template resolves
@@ -42,7 +43,7 @@ def acoustic_connect_pod(podfile_dir, config_path: nil)
   use_release = connect_config['useRelease']
   ios_version = connect_config['iOSVersion'].to_s
   name = use_release ? 'AcousticConnect' : 'AcousticConnectDebug'
-  floor = '>= 2.1.13'
+  floor = '>= 2.1.51'
   requirements = ios_version.empty? ? [floor] : [floor, ios_version]
   [name, requirements]
 end

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

@@ -187,9 +187,9 @@ export interface AcousticConnectRN extends HybridObject<{
      * 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.
+     * top-level numbers normally. Both versions sit below the
+     * `[11.1.16-beta, 12.0.0)` range this package accepts, so every supported
+     * version carries a top-level number.
      *
      * @example Nested payload
      * ```ts

package/package.json

@@ -228,7 +228,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.1.6",
+    "version": "19.1.7",
     "workspaces": [
         "example",
         "Examples/bare-workflow"

package/plugin/build/withConnectNSE.d.ts

@@ -53,7 +53,7 @@ export declare function buildNSEEntitlements(appGroupIdentifier: string): string
  *
  * Tolerates a missing ConnectConfig.json or a missing `Connect` key: when
  * the file or key is absent the block defaults to AcousticConnectDebug with
- * floor '>= 2.1.12' and no version pin, so prop-only setups (no
+ * floor '>= 2.1.51' and no version pin, so prop-only setups (no
  * ConnectConfig.json) keep working.  If the file exists but contains invalid
  * JSON, `pod install` will print a warning and use the same defaults rather
  * than crashing.

package/plugin/build/withConnectNSE.js

@@ -179,7 +179,7 @@ const PODFILE_MARKER = '# @generated ConnectNSE target (react-native-acoustic-co
  *
  * Tolerates a missing ConnectConfig.json or a missing `Connect` key: when
  * the file or key is absent the block defaults to AcousticConnectDebug with
- * floor '>= 2.1.12' and no version pin, so prop-only setups (no
+ * floor '>= 2.1.51' and no version pin, so prop-only setups (no
  * ConnectConfig.json) keep working.  If the file exists but contains invalid
  * JSON, `pod install` will print a warning and use the same defaults rather
  * than crashing.
@@ -201,7 +201,7 @@ def ${helperName}
   use_release = connect_config['useRelease'] || false
   ios_version = (connect_config['iOSVersion'] || '').to_s
   name = use_release ? 'AcousticConnect' : 'AcousticConnectDebug'
-  floor = '>= 2.1.12'
+  floor = '>= 2.1.51'
   requirements = ios_version.empty? ? [floor] : [floor, ios_version]
   [name, requirements]
 end

package/plugin/src/withConnectNSE.ts

@@ -210,7 +210,7 @@ const PODFILE_MARKER =
  *
  * Tolerates a missing ConnectConfig.json or a missing `Connect` key: when
  * the file or key is absent the block defaults to AcousticConnectDebug with
- * floor '>= 2.1.12' and no version pin, so prop-only setups (no
+ * floor '>= 2.1.51' and no version pin, so prop-only setups (no
  * ConnectConfig.json) keep working.  If the file exists but contains invalid
  * JSON, `pod install` will print a warning and use the same defaults rather
  * than crashing.
@@ -236,7 +236,7 @@ def ${helperName}
   use_release = connect_config['useRelease'] || false
   ios_version = (connect_config['iOSVersion'] || '').to_s
   name = use_release ? 'AcousticConnect' : 'AcousticConnectDebug'
-  floor = '>= 2.1.12'
+  floor = '>= 2.1.51'
   requirements = ios_version.empty? ? [floor] : [floor, ios_version]
   [name, requirements]
 end

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

@@ -205,9 +205,9 @@ export interface AcousticConnectRN extends HybridObject<{ ios: 'swift', android:
      * 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.
+     * top-level numbers normally. Both versions sit below the
+     * `[11.1.16-beta, 12.0.0)` range this package accepts, so every supported
+     * version carries a top-level number.
      *
      * @example Nested payload
      * ```ts