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.
App crashes after displayIncomingCall with 'NSInvalidArgumentException'
See original GitHub issueBug report
Description
After calling RNCallKeep.displayIncomingCall(...) the incoming call screen is displayed and then the app immediately crashes.
Steps to Reproduce
Pass null as the localizedCallerName parameter.
Examples:
RNCallKeep.displayIncomingCall(uuid, handle);
// OR
RNCallKeep.displayIncomingCall(uuid, handle, null);
Versions
- Callkeep: 3.0.8
- React Native: 0.59.10
- iOS: 13.2.3
- Android:
- Phone model: iPhone XS
Logs
2019-12-03 22:50:30.308216-0700 Peerlogic Beta[705:91446] [RNCallKeep][reportNewIncomingCall] uuidString = fa95c080-1659-11ea-9e54-4fee64a62c6b
2019-12-03 22:50:30.317210-0700 Peerlogic Beta[705:91237] *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '*** -[__NSPlaceholderDictionary initWithObjects:forKeys:count:]: attempt to insert nil object from objects[3]'
*** First throw call stack:
(0x1c1bb3ab0 0x1c18cd028 0x1c1c0c550 0x1c1c16370 0x1c1a9a540 0x1c1a8bdec 0x100ccf7b8 0x1cfd49464 0x102011e1c 0x10201327c 0x10202132c 0x1c1b2ee0c 0x1c1b29b68 0x1c1b29084 0x1cbd77534 0x1c5c99670 0x10061d0f0 0x1c19a8e18)
libc++abi.dylib: terminating with uncaught exception of type NSException
React Native Environment Info
System:
OS: macOS 10.15.1
CPU: (8) x64 Intel(R) Core(TM) i7-8559U CPU @ 2.70GHz
Memory: 226.40 MB / 16.00 GB
Shell: 5.7.1 - /bin/zsh
Binaries:
Node: 10.17.0 - ~/.nvm/versions/node/v10.17.0/bin/node
Yarn: 1.19.2 - /usr/local/bin/yarn
npm: 6.11.3 - ~/.nvm/versions/node/v10.17.0/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman
SDKs:
iOS SDK:
Platforms: iOS 13.2, DriverKit 19.0, macOS 10.15, tvOS 13.2, watchOS 6.1
IDEs:
Android Studio: 3.4 AI-183.6156.11.34.5522156
Xcode: 11.2.1/11B500 - /usr/bin/xcodebuild
npmPackages:
react: 16.9.0 => 16.9.0
react-native: jbroquist/react-native#fishhook-fix => 0.59.10
npmGlobalPackages:
react-native-cli: 2.0.1
react-native-rename: 2.4.1
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (1 by maintainers)
Top Results From Across the Web
Developers - App crashes after displayIncomingCall with ...
App crashes after displayIncomingCall with 'NSInvalidArgumentException '
Read more >App crashes with error "Fatal Exce… | Apple Developer Forums
App crashes with error "Fatal Exception: NSInvalidArgumentException -[<NSTextContentStorage: 0x281dc68a0> locationFromLocation:withOffset:] ...
Read more >objective c - App crash: NSInvalidArgumentException in iOS 8
In your case there seems to be some issue due to which numberOfSectionsInTableView (which is a tableView delegate method) is getting called on...
Read more >My App Crashed, Now What? - Kodeco
In this tutorial, you'll learn what makes your app crash and how to fix it when it does.
Read more >How to Fix the Top 5 iOS Crashes - Instabug Blog
Broken down it is a signal (SIG) sent to interrupt the code when a segmentation violation (SEGV) occurs. This happens when your app...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I worked around this by passing an empty string as the
localizedCallerNameparameter:It might be worth noting this in the documentation as the parameter is listed as optional.
Fixed in #166