react-native-acoustic-connect-beta 18.0.22 → 18.0.24

package/AcousticConnectRN.podspec

@@ -8,7 +8,28 @@ repository = package["repository"]["url"]
 useRelease = connectConfig["Connect"]["useRelease"]
 dependencyName = useRelease ? 'AcousticConnect' : 'AcousticConnectDebug'
 iOSVersion = connectConfig["Connect"]["iOSVersion"]
-dependencyVersion = iOSVersion.to_s.empty? ? "" : ", '#{iOSVersion}'"
+
+# Floor required by the RN bridge:
+#   - `ConnectSDK.shared.enable(with:)` and `ConnectConfig` landed in 2.0.0
+#     (CA-135041) — anything older lacks the Swift symbols this file imports.
+#   - Bundle-less init via `_connectApplyBundleDefaults` landed in 2.0.5
+#     (CA-136977, Release_Connect_Module_2_0_5, 2026-04-13). Without it,
+#     consumers who don't bundle `EOCoreSettings.bundle` + `TLFResources.bundle`
+#     fail to enable the SDK at all — the bridge ships no bundles and relies
+#     on programmatic config, so this fix is load-bearing here.
+# Consumers can still pin a specific version via
+# `ConnectConfig.json -> Connect.iOSVersion`; CocoaPods composes both
+# constraints, so an attempted downgrade fails loudly at `pod install`.
+#
+# Push: the iOS Connect SDK ships push as part of the same pod (`ConnectPushConfig`
+# is in `ConnectSDK.shared.enable(with:)`), so this single floor covers both the
+# analytics and push code paths. If a future SDK major splits push into a
+# separate pod or moves push features to a higher floor, this is the natural
+# place to introduce a conditional floor keyed off
+# `ConnectConfig.json -> Connect.PushEnabled` (mirrors the Android conditional
+# on `connect-push-fcm` in `android/build.gradle`).
+sdkFloor = '>= 2.0.5'
+dependencyRequirements = iOSVersion.to_s.empty? ? [sdkFloor] : [sdkFloor, iOSVersion]
 
 # Write the merged consumer config to the resource-bundle source path AT POD INSTALL TIME.
 # This MUST happen before CocoaPods builds the AcousticConnectRNConfig bundle target,
@@ -29,8 +50,7 @@ puts JSON.pretty_generate(connectConfig)
 puts "repository:#{repository}"
 puts "useRelease:#{useRelease}"
 puts "dependencyName:#{dependencyName}"
-puts "dependencyVersion:#{dependencyVersion}"
-puts "connectDependency:#{dependencyName}#{dependencyVersion}"
+puts "dependencyRequirements:#{dependencyRequirements.inspect}"
 puts "***************************************************************"
 
 Pod::Spec.new do |s|
@@ -69,6 +89,6 @@ Pod::Spec.new do |s|
 
   s.dependency 'React-jsi'
   s.dependency 'React-callinvoker'
-  s.dependency "#{dependencyName}#{dependencyVersion}"
+  s.dependency dependencyName, *dependencyRequirements
   install_modules_dependencies(s)
 end

package/README.md

@@ -1,93 +1,263 @@
 # react-native-acoustic-connect-beta
 
+React Native plugin for the Acoustic Connect SDK. Captures user interactions,
+screen replays, and analytics events on iOS and Android. Supports optional push
+notifications via the Connect backend.
+
+For the full product overview see the
+[Connect SDK overview on the developer portal](https://developer.goacoustic.com/acoustic-connect/docs/connect-sdk-overview).
+
 ## Requirements
 
-- React Native v0.78.0 or higher using new architecture
-- Node 20.0.0 or higher
-- Does not support expo
+- React Native 0.82.x – 0.85.x with the new architecture
+- React 19.1.1 or newer (or whatever your RN version pins)
+- Node 20 or newer
+- 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)`
+- **Expo is not supported by this package.** Expo apps should use the sibling
+  Config Plugin (tracked separately under PES-4002 / CA-137701).
 
 ## Installation
 
 ```bash
-// To add to your package
-npm add react-native-acoustic-connect-beta react-native-nitro-modules
-// To install on your application and view debug information during install
-npm install --foreground-scripts --force
-
+npm install react-native-acoustic-connect-beta react-native-nitro-modules
+cd ios && pod install
 ```
-## Overview
 
-[Go to overview](https://developer.goacoustic.com/acoustic-connect/docs/connect-sdk-overview)
+The plugin reads a `ConnectConfig.json` from your project root at install time
+(iOS via the podspec, Android via `config.gradle`) and bakes the values into the
+native bundles. **`ConnectConfig.json` is the single source of truth** — there
+is no runtime override path. A minimal config looks like:
 
----
+```json
+{
+  "Connect": {
+    "AppKey": "your-app-key",
+    "PostMessageUrl": "https://collector.example.com/collectorPost",
+    "KillSwitchUrl": "https://collector.example.com/collector/switch/your-app-key",
+    "useRelease": false,
 
-## Getting started
+    "PushEnabled": false,
+    "iOSPushMode": "automatic",
+    "iOSAppGroupIdentifier": null,
+    "AndroidNotificationIconResName": null
+  }
+}
+```
 
-**This module uses only enhanced replay.
+Field summary (see [API reference](#api-reference) for full semantics):
 
-[Connect Install Documentation](https://developer.goacoustic.com/acoustic-connect/docs/react-native-integration)
+| Field | Default | Purpose |
+| --- | --- | --- |
+| `AppKey` | _(required)_ | Your Connect application key. |
+| `PostMessageUrl` | _(required)_ | Collector endpoint URL. |
+| `KillSwitchUrl` | _(optional)_ | Kill-switch endpoint URL. |
+| `useRelease` | `false` | `true` selects the release AcousticConnect iOS pod over the debug variant. |
+| `iOSVersion` | `""` | Pin a specific iOS pod version; empty = newest in the supported range. |
+| `AndroidVersion` | `""` | Pin a specific Android Connect SDK version; empty = newest in the supported range. |
+| `PushEnabled` | `false` | Master switch. On Android, also gates the `connect-push-fcm` artifact inclusion. |
+| `iOSPushMode` | `"automatic"` | iOS-only: `"automatic"` (SDK owns APNs delegate) or `"manual"` (app owns it). Ignored when `PushEnabled` is `false`. |
+| `iOSAppGroupIdentifier` | `null` | iOS App Group shared with the Notification Service / Notification Content extension. |
+| `AndroidNotificationIconResName` | `null` | Drawable resource name (no extension) for the Android notification small icon. |
 
----
-# Demo
-## Sample Code with integrated
-### Using NativeBase v3 KitchenSink
-![demo](https://github.com/go-acoustic/react-native-acoustic-connect/blob/main/Example/nativebase-v3-kitchensink/assets/demo.png)
+## Quick start
 
-* NativeBase-KitchenSink taken from https://github.com/GeekyAnts/nativebase-v3-kitchensink which is at Example/nativebase-v3-kitchensink. 
+### 1. Initialise the SDK
 
-[Installation instructions](https://developer.goacoustic.com/acoustic-connect/docs/build-a-sample-react-native-app)
----
+The SDK **auto-initialises** at module load time using the values from
+`ConnectConfig.json`. For most apps there is no JS-side init code to write —
+just import the package and you're done:
 
-# Notes
-There are several know issues between npm install versus yarn install. Since yarn is a Facebook tool. It normally has fixes patched for installing dependancies.
+```ts
+// index.js
+import AcousticConnectRN from 'react-native-acoustic-connect-beta'
+// SDK is already initialising on the main actor / main looper. No further
+// setup required.
+```
 
-## Troubleshooting
+For consent-gated apps (GDPR, CCPA, COPPA), use the lifecycle pair:
+
+```ts
+import AcousticConnectRN from 'react-native-acoustic-connect-beta'
 
-### Issues installing
+// At app start, if you don't yet have user consent:
+AcousticConnectRN.disable()
+
+// Later, after the user opts in:
+AcousticConnectRN.enable()
 ```
-npm add react-native-nitro-modules         
-npm ERR! code ERESOLVE
-npm ERR! ERESOLVE could not resolve
-npm ERR! 
-npm ERR! While resolving: @expo/webpack-config@19.0.1
-npm ERR! Found: expo@52.0.46
-npm ERR! node_modules/expo
-npm ERR!   peer expo@"*" from expo-font@13.0.4
-npm ERR!   node_modules/expo-font
-npm ERR!     expo-font@"~13.0.4" from expo@52.0.46
-npm ERR!     peer expo-font@"*" from @expo/vector-icons@14.1.0
-npm ERR!     node_modules/@expo/vector-icons
-npm ERR!       @expo/vector-icons@"^14.0.0" from expo@52.0.46
-npm ERR!       1 more (the root project)
-npm ERR!     1 more (the root project)
-npm ERR!   peer expo@"*" from expo-file-system@18.0.12
-npm ERR!   node_modules/expo-file-system
-npm ERR!     expo-file-system@"~18.0.12" from expo@52.0.46
-npm ERR!   6 more (expo-asset, expo-pwa, expo-keep-awake, expo-constants, ...)
-npm ERR! 
-npm ERR! Could not resolve dependency:
-npm ERR! peer expo@"^49.0.7 || ^50.0.0-0" from @expo/webpack-config@19.0.1
-npm ERR! node_modules/@expo/webpack-config
-npm ERR!   @expo/webpack-config@"^19.0.1" from the root project
-npm ERR! 
-npm ERR! Conflicting peer dependency: expo@50.0.21
-npm ERR! node_modules/expo
-npm ERR!   peer expo@"^49.0.7 || ^50.0.0-0" from @expo/webpack-config@19.0.1
-npm ERR!   node_modules/@expo/webpack-config
-npm ERR!     @expo/webpack-config@"^19.0.1" from the root project
-npm ERR! 
-npm ERR! Fix the upstream dependency conflict, or retry
-npm ERR! this command with --force or --legacy-peer-deps
-npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
-npm ERR! 
-npm ERR! 
-npm ERR! For a full report see:
-npm ERR! .npm/_logs/2025-05-24T00_43_01_748Z-eresolve-report.txt
-
-npm ERR! A complete log of this run can be found in: .npm/_logs/2025-05-24T00_43_01_748Z-debug-0.log
+
+`enable()` and `disable()` are both parameterless — all configuration comes
+from `ConnectConfig.json`. They're idempotent at the native layer; calling
+`enable()` on an already-running SDK is a no-op.
+
+### 2. Add the `<Connect>` wrapper (declarative, in your tree)
+
+Wrap your `NavigationContainer` in `<Connect>` to enable navigation tracking,
+touch capture, and optional keyboard / dialog interception. The wrapper does
+not own SDK lifecycle — that's been done in step 1 — so it can mount, unmount,
+or remount freely without disrupting the session.
+
+```tsx
+import { useNavigationContainerRef, NavigationContainer } from '@react-navigation/native'
+import { Connect } from 'react-native-acoustic-connect-beta'
+
+export default function App() {
+  const navigationRef = useNavigationContainerRef()
+  return (
+    <Connect
+      navigationRef={navigationRef}
+      captureKeyboardEvents
+      captureDialogEvents
+    >
+      <NavigationContainer ref={navigationRef}>
+        {/* your screens */}
+      </NavigationContainer>
+    </Connect>
+  )
+}
 ```
 
-fix issue or you use the following to solve depencencies issues
+`<Connect>` is optional. Apps that only need custom event logging (no automatic
+screen / touch / keyboard tracking) can skip it entirely.
+
+### 3. Log events (imperative, anywhere)
+
+```ts
+import AcousticConnectRN from 'react-native-acoustic-connect-beta'
+
+// Custom application event
+AcousticConnectRN.logCustomEvent('checkout_started', { cartId: 'abc' }, 1)
+
+// Force a logical screen name (e.g. for non-NavigationContainer screens)
+AcousticConnectRN.setCurrentScreenName('CheckoutScreen')
+
+// Manual exception capture
+AcousticConnectRN.logExceptionEvent(
+  'Payment failed',
+  err.stack ?? '',
+  /* unhandled */ false
+)
 ```
+
+Dialog tracking helpers (`useDialogTracking`, `DialogListener`,
+`withAcousticAutoDialog`) instrument React Native `Alert.alert(...)` and custom
+dialogs automatically. See the
+[developer portal](https://developer.goacoustic.com/acoustic-connect/docs/react-native-integration)
+for details.
+
+## API reference
+
+### `AcousticConnectRN.enable(): boolean`
+
+Re-enables the SDK after a prior `disable()`. Reads all configuration from
+`ConnectConfig.json`. Returns `true` on accepted dispatch; `false` only when
+the platform can't satisfy a precondition (e.g. Android without an
+`Application` context yet). Idempotent — the native SDK short-circuits if it's
+already running.
+
+> The SDK also auto-initialises at module load using the same configuration,
+> so you typically don't need to call `enable()` at all. The method exists to
+> pair with `disable()` for opt-out / consent flows.
+
+### `AcousticConnectRN.disable(): boolean`
+
+Stops data capture, flushes pending messages, releases push state. Idempotent.
+
+### Push configuration (`ConnectConfig.json`)
+
+| Field | Type | Default | Semantics |
+| --- | --- | --- | --- |
+| `PushEnabled` | boolean | `false` | Cross-platform master switch. On Android, drives `connect-push-fcm` artifact inclusion at build time. |
+| `iOSPushMode` | `"automatic"` / `"manual"` | `"automatic"` | iOS-only. Ignored when `PushEnabled` is `false`. |
+| `iOSAppGroupIdentifier` | string \| null | `null` | iOS App Group shared with NSE / NCE for rich push payloads. |
+| `AndroidNotificationIconResName` | string \| null | `null` | Drawable resource name for the Android notification small icon. |
+
+#### iOS push modes
+
+- `"automatic"` — the iOS Connect SDK manages APNs token registration internally. The host app only requests user permission via `UNUserNotificationCenter`; token delivery and forwarding to the Connect backend are handled by the SDK.
+- `"manual"` — the host app owns APNs delegate callbacks (`application(_:didRegisterForRemoteNotificationsWithDeviceToken:)`) and forwards tokens explicitly via `ConnectSDK.shared.push.didRegisterWithToken(token)`.
+
+#### Android push
+
+The `iOSPushMode` field is iOS-only; Android push is gated solely by
+`PushEnabled`. On Android, FCM requires a `FirebaseMessagingService` subclass
+that the host app declares in its `AndroidManifest.xml`, so push is always
+app-driven. The host app is responsible for:
+
+- shipping `google-services.json` in `android/app/`,
+- implementing `FirebaseMessagingService.onNewToken(...)`,
+- forwarding the FCM token to the Connect SDK.
+
+The Android push-forwarding API itself is wired under follow-up work — until
+that lands, `PushEnabled: true` on Android only changes which artifact is on
+the classpath; the host-side token forwarding API is not yet exposed.
+
+### `<Connect>` props
+
+| Prop | Type | Required | Description |
+| --- | --- | --- | --- |
+| `children` | `ReactNode` | yes | Your `NavigationContainer` (or any subtree). |
+| `navigationRef` | `RefObject` | recommended | Ref from `useNavigationContainerRef()`. Enables screen-name tracking. |
+| `captureKeyboardEvents` | `boolean` | yes | Capture iOS/Android keyboard show/hide events. |
+| `captureDialogEvents` | `boolean` | no (default `false`) | Auto-track `Alert.alert(...)` calls. |
+
+### Other methods
+
+The plugin exposes the full Connect SDK surface — custom events, signals,
+exceptions, location, screen layout, click / text-change events, dialog events,
+and config-item getters/setters. Signatures are stable across platforms; see
+`src/specs/react-native-acoustic-connect.nitro.ts` for the typed Nitro spec and
+the
+[developer portal](https://developer.goacoustic.com/acoustic-connect/docs/react-native-integration)
+for end-to-end recipes.
+
+## Migration from earlier versions
+
+See [Migration-Guide.md](./Migration-Guide.md) for the steps to move from the
+legacy `NativeModules.AcousticConnectRN` interface to the current ESM exports
+and the `<Connect>` component.
+
+## Troubleshooting
+
+### `npm install` peer-dependency conflicts
+
+If `npm install` errors out on a peer-dependency resolution involving Expo or
+older `react-native-nitro-modules` versions, retry with:
+
+```bash
 npm install react-native-nitro-modules --legacy-peer-deps
 ```
+
+This usually only happens when an existing project pulls in stale Expo
+transitives. Permanent fix: align RN, React, and Nitro versions with the
+[Requirements](#requirements) section above.
+
+### iOS — `pod install` fails with `[Connect] requires AcousticConnect >= 2.0.5`
+
+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
+`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
+`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
+separately if you need it.
+
+### Gradle can't find `node`
+
+Common when Gradle is launched outside an NVM-loaded shell. Either:
+
+- Stop the daemon (`./gradlew --stop`) and re-run `npm run android` from a
+  shell where `which node` resolves, or
+- Symlink node onto a stable PATH: `ln -sf "$(which node)" /opt/homebrew/bin/node`.
+
+---
+
+For more, see the
+[Connect React Native integration guide](https://developer.goacoustic.com/acoustic-connect/docs/react-native-integration)
+and the
+[sample app walk-through](https://developer.goacoustic.com/acoustic-connect/docs/build-a-sample-react-native-app).

package/android/build.gradle

@@ -152,6 +152,23 @@ allprojects {
     }
 }
 
+// Read consumer config at script-evaluation time so the right Connect Android
+// artifact is selected without depending on config.gradle's text-rewriting
+// pass (which only matches the analytics artifact name). Both `PushEnabled`
+// and `AndroidVersion` are read directly here:
+//   - `PushEnabled` picks between the analytics-only and push-fcm artifacts.
+//   - `AndroidVersion` (when set) pins the version against the active artifact.
+import groovy.json.JsonSlurper
+def acousticConfigFile = new File("$rootDir/../ConnectConfig.json")
+def acousticConfig = acousticConfigFile.exists()
+  ? new JsonSlurper().parse(acousticConfigFile)
+  : [Connect: [:]]
+def acousticPushEnabled = (acousticConfig.Connect?.PushEnabled ?: false).toString().toBoolean()
+def acousticVersionPin = (acousticConfig.Connect?.AndroidVersion ?: '').trim()
+def acousticVersion = acousticVersionPin.isEmpty() ? '+' : acousticVersionPin
+def acousticArtifact = acousticPushEnabled ? 'connect-push-fcm' : 'connect'
+println "AcousticConnectRN: PushEnabled=$acousticPushEnabled, artifact=io.github.go-acoustic:$acousticArtifact:$acousticVersion"
+
 dependencies {
   // Provided by the host app at runtime — compileOnly avoids version conflicts
   //noinspection GradleDynamicVersion
@@ -160,8 +177,36 @@ dependencies {
   // Provided by the host app via react-native-nitro-modules peer dependency
   compileOnly project(":react-native-nitro-modules")
 
-  // Connect SDK — version overridden by config.gradle based on ConnectConfig.json
-  implementation 'io.github.go-acoustic:connect:10.4.29'
+  // Connect Android SDK — analytics-only artifact OR push variant, never both.
+  // The push-fcm artifact transitively brings in the core analytics module;
+  // declaring both as direct dependencies would risk duplicate-class errors
+  // and ambiguous version resolution. The selection is structural and gated
+  // at build time by `ConnectConfig.json -> Connect.PushEnabled` — a customer
+  // who didn't opt in for push can't accidentally pull in FCM transitives,
+  // and a customer who did opt in gets the right module without a second
+  // toggle.
+  //noinspection GradleDynamicVersion
+  implementation "io.github.go-acoustic:$acousticArtifact:$acousticVersion"
+
+  // Version range enforced by the RN bridge. Lower bound prevents downgrades
+  // to releases that lack APIs this bridge calls; upper bound prevents a
+  // future 12.x major (with potentially breaking changes) from being picked
+  // up automatically by Gradle's `+` resolver. Both halves are `strictly` so
+  // an attempted override via `Connect.AndroidVersion` fails loudly at
+  // resolution time rather than surfacing as a runtime `ClassNotFoundException`
+  // or method-missing error. Constraints are declared for both artifact
+  // names — Gradle only enforces the one that resolves into the graph, so
+  // the unused entry is inert.
+  constraints {
+    implementation('io.github.go-acoustic:connect') {
+      version { strictly '[11.0.11, 12.0.0)' }
+      because 'AcousticConnectRN requires Connect Android SDK in [11.0.11, 12.0.0). Bump the upper bound after validating compatibility with a new major.'
+    }
+    implementation('io.github.go-acoustic:connect-push-fcm') {
+      version { strictly '[11.0.11, 12.0.0)' }
+      because 'connect-push-fcm tracks the same release line as the core connect artifact.'
+    }
+  }
 }
 
 if (isNewArchitectureEnabled()) {

package/android/gradle.properties

@@ -1,5 +1,5 @@
 AcousticConnectRN_kotlinVersion=2.0.21
-AcousticConnectRN_minSdkVersion=23
-AcousticConnectRN_targetSdkVersion=34
-AcousticConnectRN_compileSdkVersion=34
+AcousticConnectRN_minSdkVersion=26
+AcousticConnectRN_targetSdkVersion=36
+AcousticConnectRN_compileSdkVersion=36
 AcousticConnectRN_ndkVersion=27.1.12297006

package/android/src/main/assets/ConnectAdvancedConfig.json

@@ -24,7 +24,7 @@
     "IpPlaceholder": "N/A",
     "KillSwitchAsync": true,
     "KillSwitchDelay": 300,
-    "LibraryVersion": "11.0.9-beta",
+    "LibraryVersion": "11.0.12-beta",
     "LogFullRequestResponsePayloads": true,
     "MessageTypeHeader": "WorklightHit",
     "MessageTypes": "4,5",

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

@@ -1,4 +1,4 @@
-#Tue Apr 28 02:21:07 PDT 2026
+#Tue May 26 07:16:53 PDT 2026
 UseWhiteList=true
 PrintScreen=3
 UseRandomSample=false

package/android/src/main/assets/TealeafAdvancedConfig.json

@@ -24,7 +24,7 @@
     "IpPlaceholder": "N/A",
     "KillSwitchAsync": true,
     "KillSwitchDelay": 300,
-    "LibraryVersion": "10.4.28-beta",
+    "LibraryVersion": "10.4.29-beta",
     "LogFullRequestResponsePayloads": true,
     "MessageTypeHeader": "WorklightHit",
     "MessageTypes": "4,5",

package/android/src/main/java/com/acousticconnectrn/AcousticConnectRNPackage.java

@@ -12,9 +12,6 @@
 
 package com.acousticconnectrn;
 
-import android.os.Handler;
-import android.os.Looper;
-import android.util.Log;
 import androidx.annotation.Nullable;
 import androidx.annotation.NonNull;
 
@@ -22,7 +19,6 @@ import com.facebook.react.bridge.NativeModule;
 import com.facebook.react.bridge.ReactApplicationContext;
 import com.facebook.react.module.model.ReactModuleInfoProvider;
 import com.facebook.react.TurboReactPackage;
-import com.margelo.nitro.NitroModules;
 import com.margelo.nitro.acousticconnectrn.AcousticConnectRNOnLoad;
 
 import java.util.HashMap;
@@ -41,34 +37,15 @@ public class AcousticConnectRNPackage extends TurboReactPackage {
   }
 
   static {
+    // Nitro's C++ factory (AcousticConnectRNOnLoad.cpp) constructs instances
+    // of HybridAcousticConnectRN itself via a zero-arg constructor, lazily on
+    // first JS call. Earlier versions of this file spun up a background
+    // thread to poll NitroModules.getApplicationContext() and eagerly
+    // construct one instance — that workaround was masking the symptom of
+    // the bridge holding a stored ReactApplicationContext field that Nitro's
+    // factory then passed as null. The bridge now resolves the React context
+    // on-demand from NitroModules.applicationContext (nullable, guarded), so
+    // no eager construction is needed.
     AcousticConnectRNOnLoad.initializeNative();
-    try {
-      // Start a background thread to wait for the context
-      new Thread(() -> {
-        ReactApplicationContext reactContext = null;
-
-        // Poll until NitroModules.getApplicationContext() is not null
-        while (reactContext == null) {
-          reactContext = NitroModules.getApplicationContext();
-          if (reactContext == null) {
-            try {
-              Thread.sleep(100); // Sleep for 100ms before checking again
-            } catch (InterruptedException e) {
-              Log.e("AcousticConnectRNPackage", "Thread interrupted while waiting for ReactApplicationContext.", e);
-              return;
-            }
-          }
-        }
-
-        // Post initialization logic to the main (UI) thread
-        ReactApplicationContext finalReactContext = reactContext;
-        new Handler(Looper.getMainLooper()).post(() -> {
-          HybridAcousticConnectRN hybridInstance = new HybridAcousticConnectRN(finalReactContext);
-          Log.i("AcousticConnectRNPackage", "HybridAcousticConnectRN initialized successfully.");
-        });
-      }).start();
-    } catch (Exception e) {
-      Log.e("AcousticConnectRNPackage", "Failed to initialize HybridAcousticConnectRN.", e);
-    }
   }
 }