react-native-webrtc / react-native-webrtc/react-native-callkeep
Call not ending on remote device if call was declined too fast on iOS
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 511
- Avg merge
- 9h 12m
- Merged PRs (30d)
- 2
Description
Has anyone else experienced that if let's say someone calls an iOS phone (in my case an android phone was the emitter) and the iOS device declines the call too fast, like less then 2 seconds, sometimes the call ended event is not fired on the caller's device. So it will continuously ring. This isn't happening always, but when it happens it is annoying.
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 reviewing the issue report and the repository's iOS CallKit and Android ConnectionService integration points. Reproduce a call that is declined on iOS in under two seconds, then trace whether the caller receives the call-ended event. Done means the caller stops ringing reliably after the rapid decline case.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, ios, react-native
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100