You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix: sync callkit audio config with webrtc config (#2095)
## 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
<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## 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.
<sub>✏️ Tip: You can customize this high-level summary in your review
settings.</sub>
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
---------
Co-authored-by: Artem Grintsevich <greenfrvr@gmail.com>
Co-authored-by: jdimovska <jona.dimovska@hotmail.com>
Co-authored-by: Oliver Lazoroski <oliver.lazoroski@gmail.com>
0 commit comments