@telnyx/react-voice-commons-sdk 0.4.0 → 0.4.1

package/CHANGELOG.md

@@ -1,5 +1,16 @@
 # CHANGELOG.md
 
+## [0.4.1] (2026-04-27)
+
+### Bug Fixing
+
+- **Recover from stale TelnyxRTC client on incoming VoIP push.** `SessionManager.handlePushNotification` now calls `client.isFresh(30_000)` before reusing an existing client. If the socket has been silent past the threshold (typical after an iOS app freeze), the client is disposed, state is flipped to `DISCONNECTED`, and the push falls through to the full `_connect()` path so login runs with the new push's `voice_sdk_id`. This resolves the case where an answered call would hang on "connecting" until CallKit timed out, because `processVoIPNotification()` was being called on a socket that had silently died.
+- Widened the reconnect-trigger state check in `handlePushNotification` to include `ERROR`, not only `DISCONNECTED`, so a push that arrives after a failed session re-establishes the connection instead of being dropped.
+
+### Dependencies
+
+- Now requires `@telnyx/react-native-voice-sdk >= 0.4.3`, which adds the `isFresh()` / `connectionIdleMs` API and auto-reconnects on unexpected socket errors. See the [voice-sdk 0.4.3 changelog](../package/CHANGELOG.md#043-2026-04-27) for details.
+
 ## [0.4.0] (2026-04-19)
 
 ### Enhancement

package/lib/internal/session/session-manager.js

@@ -202,6 +202,39 @@ class SessionManager {
     );
     // Store the push notification payload for when the client is created
     this._pendingPushPayload = payload;
+    // If we have a TelnyxRTC instance but its socket isn't fresh — either not
+    // connected at all, or connected but with no traffic for longer than the
+    // threshold — dispose it so we go through the full _connect() path below
+    // instead of calling processVoIPNotification on a stale client.
+    //
+    // This handles two cases iOS gives us with the same code path:
+    //   1. Terminated-then-cold-launched: a client exists (constructed at
+    //      app boot) but its connection was never opened (idleMs=Infinity).
+    //   2. Suspended-then-thawed: a client exists with `connected=true`,
+    //      but the kernel killed the TLS session during freeze without
+    //      notifying the JS WebSocket wrapper, so no error event fired.
+    //
+    // 30s threshold matches the server's keep-alive ping cadence (~20s),
+    // so a live session always remains fresh.
+    const STALE_THRESHOLD_MS = 30000;
+    if (this._telnyxClient) {
+      const client = this._telnyxClient;
+      const isFresh =
+        typeof client.isFresh === 'function'
+          ? client.isFresh(STALE_THRESHOLD_MS)
+          : !!client.connected;
+      if (!isFresh) {
+        try {
+          await this._telnyxClient.disconnect();
+        } catch (err) {
+          console.warn('SessionManager: disconnect of stale client threw:', err);
+        }
+        this._telnyxClient = undefined;
+        if (this.currentState !== connection_state_1.TelnyxConnectionState.DISCONNECTED) {
+          this._connectionState.next(connection_state_1.TelnyxConnectionState.DISCONNECTED);
+        }
+      }
+    }
     // If we don't have a config yet but we're processing a push notification,
     // attempt to load stored config first (for terminated app startup)
     if (!this._currentConfig && !this._telnyxClient) {
@@ -269,11 +302,16 @@ class SessionManager {
       console.log(
         'SessionManager: RELEASE DEBUG - No client available, checking if we can trigger immediate connection'
       );
-      // If we have config (either existing or newly loaded from storage) and are disconnected, trigger immediate connection
-      // The _connect() method will process the pending push payload BEFORE calling connect()
+      // If we have config (either existing or newly loaded from storage) and
+      // are not currently connected/connecting, trigger immediate connection.
+      // We accept DISCONNECTED and ERROR (a socket failure bumps state to
+      // ERROR) so a push after a failed session still re-establishes the
+      // connection. The _connect() method will process the pending push
+      // payload BEFORE calling connect().
       if (
         this._currentConfig &&
-        this.currentState === connection_state_1.TelnyxConnectionState.DISCONNECTED
+        (this.currentState === connection_state_1.TelnyxConnectionState.DISCONNECTED ||
+          this.currentState === connection_state_1.TelnyxConnectionState.ERROR)
       ) {
         console.log(
           'SessionManager: RELEASE DEBUG - Triggering immediate connection for push notification with config type:',

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@telnyx/react-voice-commons-sdk",
-  "version": "0.4.0",
+  "version": "0.4.1",
   "description": "A high-level, state-agnostic, drop-in module for the Telnyx React Native SDK that simplifies WebRTC voice calling integration",
   "main": "lib/index.js",
   "module": "lib/index.js",

package/src/internal/session/session-manager.ts

@@ -178,6 +178,40 @@ export class SessionManager {
     // Store the push notification payload for when the client is created
     (this as any)._pendingPushPayload = payload;
 
+    // If we have a TelnyxRTC instance but its socket isn't fresh — either not
+    // connected at all, or connected but with no traffic for longer than the
+    // threshold — dispose it so we go through the full _connect() path below
+    // instead of calling processVoIPNotification on a stale client.
+    //
+    // This handles two cases iOS gives us with the same code path:
+    //   1. Terminated-then-cold-launched: a client exists (constructed at
+    //      app boot) but its connection was never opened (idleMs=Infinity).
+    //   2. Suspended-then-thawed: a client exists with `connected=true`,
+    //      but the kernel killed the TLS session during freeze without
+    //      notifying the JS WebSocket wrapper, so no error event fired.
+    //
+    // 30s threshold matches the server's keep-alive ping cadence (~20s),
+    // so a live session always remains fresh.
+    const STALE_THRESHOLD_MS = 30000;
+    if (this._telnyxClient) {
+      const client = this._telnyxClient as any;
+      const isFresh =
+        typeof client.isFresh === 'function'
+          ? client.isFresh(STALE_THRESHOLD_MS)
+          : !!client.connected;
+      if (!isFresh) {
+        try {
+          await this._telnyxClient.disconnect();
+        } catch (err) {
+          console.warn('SessionManager: disconnect of stale client threw:', err);
+        }
+        this._telnyxClient = undefined;
+        if (this.currentState !== TelnyxConnectionState.DISCONNECTED) {
+          this._connectionState.next(TelnyxConnectionState.DISCONNECTED);
+        }
+      }
+    }
+
     // If we don't have a config yet but we're processing a push notification,
     // attempt to load stored config first (for terminated app startup)
     if (!this._currentConfig && !this._telnyxClient) {
@@ -255,9 +289,17 @@ export class SessionManager {
         'SessionManager: RELEASE DEBUG - No client available, checking if we can trigger immediate connection'
       );
 
-      // If we have config (either existing or newly loaded from storage) and are disconnected, trigger immediate connection
-      // The _connect() method will process the pending push payload BEFORE calling connect()
-      if (this._currentConfig && this.currentState === TelnyxConnectionState.DISCONNECTED) {
+      // If we have config (either existing or newly loaded from storage) and
+      // are not currently connected/connecting, trigger immediate connection.
+      // We accept DISCONNECTED and ERROR (a socket failure bumps state to
+      // ERROR) so a push after a failed session still re-establishes the
+      // connection. The _connect() method will process the pending push
+      // payload BEFORE calling connect().
+      if (
+        this._currentConfig &&
+        (this.currentState === TelnyxConnectionState.DISCONNECTED ||
+          this.currentState === TelnyxConnectionState.ERROR)
+      ) {
         console.log(
           'SessionManager: RELEASE DEBUG - Triggering immediate connection for push notification with config type:',
           (this._currentConfig as any).type || 'credential'