react-native-webrtc / react-native-webrtc/react-native-callkeep
RNCallKeepBackgroundMessage documentation needed
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 511
- Avg merge
- 9h 12m
- Merged PRs (30d)
- 2
Description
Help needed
-
I've checked the example to reproduce the issue.
-
Reproduced on:
-
Android
-
iOS
Description
The headless task RNCallKeepBackgroundMessage for android handles calls from the native dialer. Calls from the native dialer on iOS work like a charm. The app launches and the listener "didLoadWithEvents" has the call data.
On Android RNCallKeepBackgroundMessage is fired and I can start a call, but the headless task is destroyed before I can register if the call is active or failed. How do you cope with calls from the native dialer on Android? I can't find any documentation for RNCallKeepBackgroundMessage.
Versions
- Callkeep: 4.3.12
- React Native: 0.71
- iOS: 16
- Android: 11
- Phone model: OnePlus 6T
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 RNCallKeepBackgroundMessage entry point and the example linked in the issue, focusing on Android native-dialer calls and the headless task lifecycle. Compare this with the described iOS didLoadWithEvents behavior, then document how to handle active or failed calls before the task is destroyed. Done means the Android usage and lifecycle are clear to users.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, react-native
- Domain
- documentation, mobile
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100