react-native-webrtc / react-native-webrtc/react-native-callkeep
Question: How to handle an inbound call thats been displayed but ended before reconnection
Open
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 511
- Avg merge
- 9h 12m
- Merged PRs (30d)
- 2
Description
I have an issue where the push is sent to the device but the call is ended before the device can reconnect. So the inbound call just continuously rings, I was just wondering how others are handling it.
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
No file, test, or entry point is named in the issue. First clarify the expected behavior when an inbound call ends before reconnection, then identify the relevant call lifecycle entry point and define done as preventing the call from ringing continuously after it has ended.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, ios, react-native
- Domain
- audio-video-rtc, mobile
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100