react-native-webrtc / react-native-webrtc/react-native-callkeep
Callkeep remains active after killing the application from task manager (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
-
Everything works fine so far, but while on a call on Android the callkeep remains active with SIP call after killing the application from the task manager.
-
Reproduced on Android:
-
Received an incoming call
-
Answered
-
kill the app from the task manager
-
call remains active
-
expected behaviour: The call keep should kill itself
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 Android sequence described: receive and answer a call, then kill the app from the task manager. Trace the Android ConnectionService lifecycle used by the project and determine why the call remains active; done means the call is ended when the application is killed.
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
- Mostly clear
- Newbie friendliness
- 35/100