react-native-webrtc / react-native-webrtc/react-native-callkeep
Disconnect receiver's call when sender cuts the call
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 send call to receiver from firebase notification and call start ringing.
When the sender cuts the call, receiver's call should disconnect.
- Reproduced on:
- Android
Steps to Reproduce
when callkeep setup developed call keep screen appears on screen and during this process when sender cuts the call the receiver's call screen should disappear.
Versions
- Callkeep:4.3.3
- React Native:0.69.3
- Phone model: samsung Galaxy Tab 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 tracing the Android ConnectionService and CallKeep setup used after a Firebase notification starts ringing, then reproduce the sender-cuts-call flow on the listed Samsung Galaxy Tab A configuration. Done means the receiver's CallKeep screen and active call both disappear when the sender ends the call.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, firebase, 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