Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[iOS] displayIncomingCall throws an error: parameter 'localizedName' cannot be nil'

See original GitHub issue

Bug report

[#] I’ve checked the example to reproduce the issue.
Reproduced on:
Android
[#] iOS

Description

When I call RNCallKeep.displayIncomingCall() using parameters described in the read me like below, I get an error saying that parameter 'localizedName' cannot be nil'

Steps to Reproduce

this is how I called the method;

acceptCall = () => {
    const uuid = this.requestedUserUuid;   //     "0731961b-415b-44f3-a960-dd94ef3372fc",
    const handle = 'testemail@email.com'
    const localizedCallerName = 'testNickname';
    const handleType = 'email';
    const hasVideo = false;
    if (Platform.OS === 'android') {
      RNCallKeep.displayIncomingCall(uuid, handle, localizedCallerName);
    } else {
      RNCallKeep.displayIncomingCall(uuid, handle, handleType, hasVideo, localizedCallerName);
    }
  }

Versions

- Callkeep: 3.0.6
- React Native: 0.50.0
- iOS: 13.2
- Android: N/A
- Phone model: iPhone 11

Logs

error

Issue Analytics

State:
Created 4 years ago
Reactions:1
Comments:8

Top GitHub Comments

4reactions

stoyan-friezecommented, Jan 2, 2021

@samad324 I was getting the same issue as you because I was passing a random typed in string as an uuid while I was testing. I fixed it by passing a RFC4122 uuid generated with https://www.npmjs.com/package/react-native-uuid

3reactions

samad324commented, Oct 12, 2020

i’m getting the same issue even i initialized callkeep.

parameter 'UUID' cannot be nil' was thrown while