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

*didLoadWithEvents* is not working.

Open
#311 18 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've checked the example to reproduce the issue.

  • Reproduced on:

  • Android

  • iOS

Description

Hi there, I'm facing the same issue as described in #107, and try to add didLoadWithEvents event right after RNCallkeep.setup(); method. But the listener is not working.

Steps to Reproduce

  setUpCallKeep = () => {
    RNCallKeep.setup(callKeepOptions);
    RNCallKeep.setAvailable(true);
    RNCallKeep.addEventListener('didLoadWithEvents', (e) => {
      console.log('Navigation -> e', e);
    });
  };

this listener is not working even if the app was opened by call keep, nor when i accept or reject the call during the JS initialization.

Versions

- Callkeep:^3.1.1
- React Native:0.63.1
- iOS:13.5
- Android: - 
- Phone model: iPhone 7

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 linked example and the RNCallKeep.setup(), setAvailable(), and addEventListener('didLoadWithEvents') flow on iOS. Reproduce the reported cases during JavaScript initialization, including opening, accepting, or rejecting a call, then verify that the event is delivered with the expected data.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.