react-native-webrtc / react-native-webrtc/react-native-callkeep
NSRangeException on getAudioOutput
Open
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 511
- Avg merge
- 9h 12m
- Merged PRs (30d)
- 2
Description
Bug report
-
I've checked the example to reproduce the issue.
-
Reproduced on:
-
Android
-
iOS
Description
NSRangeException on getAudioOutput
Steps to Reproduce
Happens intermittently when working with audio sources
Versions
- Callkeep: 4.3.12
- React Native: 0.68.15
- iOS: 17.0.3
- Android:
- Phone model: iPhone 14 Pro
Logs
CoreFoundation +0x0ed5e0 __exceptionPreprocess
libobjc.A +0x02bbfc objc_exception_throw
CoreFoundation +0x0f8a48 -[__NSArray0 objectAtIndex:]
Mango Voice +0x24f8a8 +[RNCallKeep getAudioOutput] (RNCallKeep.m:192)
Mango Voice +0x24f540 -[RNCallKeep onAudioRouteChange:] (RNCallKeep.m:151)
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 in RNCallKeep.m at getAudioOutput (line 192) and onAudioRouteChange: (line 151), using the provided stack trace to trace the intermittent iOS audio-source failure. Reproduce it with the example and audio-source changes; done means getAudioOutput no longer raises NSRangeException during audio route changes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ios, objective-c, react-native
- Domain
- audio-video-rtc, mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100