react-native-webrtc / react-native-webrtc/react-native-callkeep
[iOS] Declining Incoming Call to SIM number triggers `endCall` event
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
When using Callkeep to display an outbound call from our app and an incoming call comes in to the SIM on the phone, CallKit displays the incoming call with the option to decline or answer. Declining the call triggers the RNCallKeep endCall event with the callUUID from the outbound call instead.
This means that declining an inbound call to the phone will end the call in the app as it looks exactly like when a user presses the End Call button on CallKit.
Steps to Reproduce
- Make an outbound call with
RNCallKeep.startCall - Receive an incoming call to the SIM on the phone
- CallKit displays
DeclineandAnsweroptions - Press
Declinefor the call incoming endCallevent is triggered with the callUUID fromRNCallKeep.startCall
Versions
- Callkeep: 4.3.12
- React Native: 0.72.6
- iOS: 17.1
- Android: N/A
- Phone model: iPhone 14 Pro
Logs
N/A
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 the iOS flow with RNCallKeep.startCall, an incoming SIM call, and CallKit's Decline action on the listed versions. Trace how the endCall event receives the outbound callUUID; done means declining the SIM call no longer ends the app's outbound call or emits that UUID as an endCall event.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ios, react-native
- Domain
- mobile-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100