react-native-webrtc / react-native-webrtc/react-native-callkeep

How do you determine if 'didLoadWithEvents' was Accepted or Rejected?

Open
#377 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Java
Stars
1.1k
Forks
511
Avg merge
9h 12m
Merged PRs (30d)
2

Description

Bug report

I need to check if didLoadWithEvents via RNCallKeep.addEventListener('didLoadWithEvents', foo);
Has an event RNCallKeepDidDisplayIncomingCall and if the incoming call was Accepted or Rejected. As I need to do different logic based on if the call was Rejected or Accepted.

Here are all the events from didLoadWithEvents
 [
{"data": 
     {
"callUUID": "fa0b33a2-e373-4d01-a114-91a2a6abf27e", 
"error": "", 
"fromPushKit": "1", 
"handle": "onasi", 
"hasVideo": "1", 
"localizedCallerName": 
"onasi", 
"payload": 
[Object], 
"supportsDTMF": 
"1", "supportsGrouping":
 "1", 
"supportsHolding": "1", "supportsUngrouping": "1"
}, "name": "RNCallKeepDidDisplayIncomingCall"}
]

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the RNCallKeep.addEventListener('didLoadWithEvents', foo) usage and the RNCallKeepDidDisplayIncomingCall payload shown in the issue. Determine whether the available event data identifies an accepted or rejected call, then document the existing behavior or define the missing change and its completion criteria.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, 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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.