react-native-webrtc / react-native-webrtc/react-native-callkeep
different casing for callUUIDs in endCall vs getCalls
Open
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 511
- Avg merge
- 9h 12m
- Merged PRs (30d)
- 2
Description
RNCallKeep.addEventListener('endCall', data => {
console.log(`in endCall: ${data.callUUID}`);
RNCallKeep.getCalls().then(calls => {
calls.forEach(c => console.log('in getCalls', c.callUUID));
See for yourselves. endCall has the uuid in lowerCase, getCalls in upperCase
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 comparing the callUUID values exposed by the endCall event and RNCallKeep.getCalls(), using the example in the issue as the reproduction. Trace where each entry point supplies the UUID and determine the intended casing. Done means both APIs expose callUUID consistently, with a regression check covering the reported difference.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, ios, react-native
- Domain
- api, mobile
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100