react-native-webrtc / react-native-webrtc/react-native-callkeep
Connecting the call on system managed CallKeep (Android)
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 511
- Avg merge
- 9h 12m
- Merged PRs (30d)
- 2
Description
Hey everyone, I was able to implement Callkeep on iOS without too much friction but i was wondering how did you manage to connect it on Android? I use React Native WebRTC but the issue is that i wasn't able to get the app launched when answering calls, the only headless task that fires when the app is killed is ReactNativeFirebaseMessagingHeadlessTask but RNCallKeepBackgroundMessage never fires, I was wondering what could i be doing wrong or if anyone else knows the solution for this problem?
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 behavior around RNCallKeepBackgroundMessage when the app is killed, alongside ReactNativeFirebaseMessagingHeadlessTask and the React Native WebRTC setup described in the issue. Reproduce an answered call on Android and determine why the expected background message does not fire; done means the app launches and the call connects when answering.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, react-native
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100