react-native-webrtc / react-native-webrtc/react-native-incall-manager
No audio on iOS after first webrtc call
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 597
- Forks
- 201
- Avg merge
- 2h 42m
- Merged PRs (30d)
- 1
Description
There was a very strange bug in our application related to react-native-incall-manager and @livekit/react-native-webrtc. It appeared only after we migrated from react-native-webrtc to @livekit/react-native-webrtc
On iOS, first webrtc connection has no issues whatsoever, but every consequent connection has no sound for remote audio stream and doesn't send bytes for local audio stream.
We couldn't figure out exact reason, however restarting in-call manager after every call has helped to mitigate the issue
useEffect(() => {
InCallManager.stop()
InCallManager.start({ media: "video" })
}, [])
Versions of our dependencies:
"react-native-incall-manager": "^4.2.1",
"@livekit/react-native": "^2.7.4",
"@livekit/react-native-webrtc": "^125.0.9",
"livekit-client": "^2.13.3",
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing consecutive iOS WebRTC calls with the listed react-native-incall-manager and LiveKit dependency versions, focusing on the InCallManager lifecycle after the first call. Compare behavior with and without the reported stop/start sequence. Done means subsequent calls preserve remote audio and send local audio without requiring that workaround.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ios, react-native
- Domain
- audio-video-rtc, mobile-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100