fix: sync callkit audio config with webrtc config

[santhoshvai]

Overview

When CallKit activates the audio session and we must forward this via audioSessionDidActivate, WebRTC:

• Increments its internal activation count
• Sets isActive = YES
• Clears any interruption state
• Notifies delegates that audio can resume

This ensures WebRTC knows the session is already active and won't try to activate it again.

In this PR, we ensure that callkit audio config matches with our intended webrtc audio config. To avoid clashes and that webrtc audio unit always starts/resumes.

Why this matters:

1. WebRTC stores its own configuration preferences in RTCAudioSessionConfiguration.webRTC()
2. When WebRTC later needs to reconfigure audio (e.g., after interruptions), it uses these stored settings
3. If you only configure AVAudioSession directly without updating WebRTC's stored config, there could be mismatches during audio route changes or interruptions

Summary by CodeRabbit

• Chores
  • Added WebRTC dependency to improve audio session management across the platform.
  • Enhanced audio configuration handling to align with industry standards.
  • Simplified internal audio session lifecycle event handling for improved stability.
  • Updated package dependencies to support latest WebRTC integration.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[changeset-bot]

⚠️ No Changeset found

Latest commit: 7b3cf05

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

• 🔍 Trigger a full review

📝 Walkthrough

Walkthrough

The PR integrates WebRTC audio session management into the calling packages. It adds the stream-react-native-webrtc dependency, refactors AudioSessionManager to use RTCAudioSession APIs instead of manual AVAudioSession configuration, forwards CallKit lifecycle events from CallingxImpl to RTCAudioSession, adds conditional bypass logic in StreamInCallManager when CallingX is active, and removes redundant audio session event handling from setupCallingExpEvents.

Changes

Cohort / File(s)	Summary
Dependency declarations packages/react-native-callingx/Callingx.podspec, packages/react-native-callingx/package.json	Adds stream-react-native-webrtc as CocoaPods dependency, devDependency (v137.1.0), and peerDependency (>=137.1.0)
CallingX audio session integration packages/react-native-callingx/ios/AudioSessionManager.swift	Replaces manual AVAudioSession configuration with RTCAudioSession.sharedInstance() API calls; applies WebRTC-derived sample rate and IO buffer duration via lock/unlock pattern
CallingX lifecycle event forwarding packages/react-native-callingx/ios/CallingxImpl.swift	Adds RTCAudioSession lifecycle forwarding in didActivate/didDeactivate handlers; manages idle timer state via UIApplication on main thread
StreamInCallManager WebRTC integration packages/react-native-sdk/ios/StreamInCallManager.swift	Applies WebRTC configuration (sample rate and IO buffer duration) to AVAudioSession during audio session category setup
StreamInCallManager bypass logic packages/react-native-sdk/src/utils/internal/registerSDKGlobals.ts	Adds Platform-aware bypass checks for CallKit/CallingX in StreamInCallManager setup/start/stop methods to prevent conflicting audio session management
Audio session event cleanup packages/react-native-sdk/src/utils/push/setupCallingExpEvents.ts	Removes didActivateAudioSession/didDeactivateAudioSession event listeners and handlers (now handled by CallingxImpl)

Sequence Diagram

sequenceDiagram
    participant CallKit
    participant CallingxImpl
    participant RTCAudioSession
    participant StreamInCallManager
    participant AVAudioSession

    CallKit->>CallingxImpl: didActivate audioSession
    CallingxImpl->>RTCAudioSession: audioSessionDidActivate()
    CallingxImpl->>AVAudioSession: manage idle timer
    CallingxImpl->>CallingxImpl: emit didActivateAudioSession

    Note over StreamInCallManager: registerSDKGlobals checks<br/>shouldBypassForCallKit()

    alt CallingX is managing audio
        StreamInCallManager->>StreamInCallManager: bypass setup/start/stop
    else CallingX inactive
        StreamInCallManager->>RTCAudioSession: apply WebRTC config
        RTCAudioSession->>AVAudioSession: configure sample rate & IO buffer
    end

    CallKit->>CallingxImpl: didDeactivate audioSession
    CallingxImpl->>RTCAudioSession: audioSessionDidDeactivate()
    CallingxImpl->>AVAudioSession: restore idle timer
    CallingxImpl->>CallingxImpl: emit didDeactivateAudioSession

Loading

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Possibly related PRs

• fix: always forward callkit audio events to webrtc #2089 – Forwards CallKit didActivate/didDeactivate audio session events to RTCAudioSession, paralleling the integration pattern in this PR.
• feat: stereo audio output support RN-332 #2038 – Modifies iOS audio session handling in StreamInCallManager to configure and use WebRTC's RTCAudioSession, directly related to the same integration goals.

Suggested reviewers

• oliverlaz
• greenfrvr

Poem

🐰 Whiskers twitch with WebRTC delight,
Audio sessions now flow just right,
CallKit and RTCAudioSession align,
No more conflicts—the harmony's fine!
The streams flow smoother, bugs take flight. 🎧

🚥 Pre-merge checks | ✅ 1 | ❌ 2

❌ Failed checks (2 warnings)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The pull request description is missing entirely. The template requires at least an Overview section and implementation notes, but no description was provided by the author.	Add a pull request description following the repository template, including an Overview section explaining the changes and Implementation notes detailing how the audio config synchronization was achieved.
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (1 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately describes the main objective of the changeset: synchronizing CallKit audio configuration with WebRTC configuration, which is reflected throughout all modified files.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[santhoshvai]

@coderabbitai full review

[coderabbitai]

✅ Actions performed

Full review triggered.

[coderabbitai]

Actionable comments posted: 1

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)

packages/react-native-callingx/ios/AudioSessionManager.swift (1)

3-39: RTCAudioSessionConfiguration API is not available in stream-react-native-webrtc v137.x—refactor to use AVAudioSession directly or Stream's callManager.

RTCAudioSessionConfiguration was removed in react-native-webrtc 111.x and is not present in v137.x. The calls to RTCAudioSessionConfiguration.webRTC(), .setWebRTC(), and related configuration will fail at runtime.

Two recommended approaches:

1. Use Stream's callManager (preferred): configure audio via callManager.start({ audioRole: "communicator", deviceEndpointType: "speaker" }) and callManager.stop(). This is Stream SDK's supported pattern and avoids manual WebRTC audio management.
2. Use AVAudioSession directly (if manual control is required): configure category, mode, and options on AVAudioSession.sharedInstance() and set active state appropriately for background operation. Avoid the removed RTCAudioSessionConfiguration API entirely.

Additionally, ensure background audio capability is enabled in Info.plist (Background Modes: Audio, AirPlay, and Picture in Picture) to maintain the audio connection in background as mentioned in the design notes.

🤖 Fix all issues with AI agents

In `@packages/react-native-sdk/src/utils/internal/registerSDKGlobals.ts`:
- Around line 30-49: Wrap each call to StreamInCallManagerNativeModule in
try/catch so native errors don’t bubble up: in the setup, start, and stop
methods (while keeping the shouldBypassForCallKit() early-return) surround calls
to setDefaultAudioDeviceEndpointType and setup inside a try/catch in setup, and
wrap StreamInCallManagerNativeModule.start() and
StreamInCallManagerNativeModule.stop() each in their own try/catch; on catch,
log a non-fatal warning (e.g., console.warn or processLogger.warn) with a clear
tag like "[StreamInCallManager.<method>]" and the error, then continue.