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

RNCallkeep.displayIncomingCall got 4 arguments,expected 4

Open
#714 0 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 11- [ ] Android

Description

I just implemented a feature that displays incoming calls when a button is clicked, but it throws an error like this.

Steps to Reproduce

Versions

4.3.3- Callkeep:
0.67- React Native:

11 - Android:
Poco x2- Phone model:

Logs

Screenshot_2023-07-12-13-52-29-641_app smartbuildings

 <TouchableOpacity
                        style={styles.notifyIcon}
                        onPress={() => {
                          const options = {
                            ios: {
                              appName: "Example",
                              supportsVideo: true,
                              displayCallReachabilityTimeout: 1000,
                            },
                            android: {
                              alertTitle: "Permissions required",
                              alertDescription:
                                "This application needs to access your phone accounts",
                              cancelButton: "Cancel",
                              okButton: "ok",
                              imageName: "phone_account_icon",
                              additionalPermissions: [
                                PermissionsAndroid.PERMISSIONS.READ_PHONE_STATE,
                                PermissionsAndroid.PERMISSIONS.CALL_PHONE,
                                PermissionsAndroid.PERMISSIONS.RECORD_AUDIO,
                                PermissionsAndroid.PERMISSIONS.READ_CONTACTS,
                                PermissionsAndroid.PERMISSIONS.READ_CALL_LOG,
                              ],
                              foregroundService: {
                                channelId: "com.company.my",
                                channelName: "Foreground service for my app",
                                notificationTitle:
                                  "My app is running on background",
                                notificationIcon:
                                  "Path to the resource icon of the notification",
                              },
                              displayCallReachabilityTimeout: 30000,
                            },
                          };
                          RNCallKeep.setup(options).then((accepted) => {
                            console.log(accepted, "acceptcall ios");
                          });

                          RNCallKeep.displayIncomingCall(
                            ramdomUuid().toLowerCase(),
                            "1231231231",
                            "1231231231",
                            "number",
                            true
                          );
                        }}
                      >
Trigger Call
                      </TouchableOpacity>

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 by reproducing the Android 11 failure from the RNCallKeep.displayIncomingCall call shown in the issue, using the listed React Native and CallKeep versions. Trace the displayIncomingCall API entry point and compare the supplied arguments with the accepted signature. Done means the reproduction no longer reports an argument-count error and the incoming call display behavior is verified.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, react-native
Domain
mobile
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.