react-native-webrtc / react-native-webrtc/react-native-callkeep
The answerCall and rejectedCall event listeners are automatically triggered as soon as incoming call received on Android
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 I get an incoming call, my event listeners for answerCall, endCall are automatically triggered on Android. This doesn't happen on iOS. What should be the reason for this?
Steps to Reproduce
- Trigger a call from a device.
- Receive an incoming call notification on android.
- The
addEventListenerforanswerCallandendCallis automatically triggered. Basically for me therejectedCallis triggered and thereby the call instance is dropped from the caller's end.
Versions
- Callkeep:^4.3.3
- React Native:0.70.4
- iOS:16.0
- Android: 9
- Phone model: Redmi Y2
Logs
Paste here
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 with the linked example and trace the Android handling around addEventListener for answerCall, endCall, and rejectedCall. Reproduce the incoming-call flow on Android 9, capture the missing logs, and confirm that these listeners fire only after the corresponding user action rather than when the notification is received.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, java, 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