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.
Emergency help. SIGABRT: __NSCFNumber > Could not cast value of type '__NSCFNumber' (0x1f1c58d28) to 'NSString' (0x1f1c58cf8). > NSString
See original GitHub issueWe got this error 3 days ago. Our app is working normally in prod so far and no new updates. @MrHertal 😦
`SIGABRT: __NSCFNumber > Could not cast value of type ‘__NSCFNumber’ (0x1f1c58d28) to ‘NSString’ (0x1f1c58cf8).
NSString`
Issue Analytics
- State:
- Created 2 years ago
- Reactions:3
- Comments:10 (2 by maintainers)
Top Results From Across the Web
Could not cast value type '__NSCFNumber' to 'NSString'
The error is saying that your quantity is Number and you cannot directly convert number to String , try like this. newDetail.
Read more >Could not cast value of type '__NS… | Apple Developer Forums
Please help, I get the error: Could not cast value of type '__NSCFString' (0x10f0444a0) to 'NSNumber' (0x10e64c488). I am trying to loop through...
Read more >Fatal Error: Could not cast value of type '__NSCFNumber' to ...
Which causes a crash when the dictionary is bridged to Swift: Could not cast value of type '__NSCFNumber' (0x7fff8ea49558) to 'NSString' ( ...
Read more >Could not cast value of type '__nscfnumber' (0x1b4520df0) to ...
You cannot cast dissimilar types. If one is an integer and the other is a string then you must convert one of the...
Read more >Could not cast value type '__NSCFNumber' to 'NSString'-swift
Coding example for the question iOS Swift: Could not cast value type '__NSCFNumber' to 'NSString'-swift.
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
This should work now with v1.8.1 (see https://github.com/MrHertal/react-native-twilio-phone/pull/74)
The bug was due to the fact that in its incoming push, Twilio sends a
twi_answer_timeoutfield as an integer but the module code was expecting a string … while on the Android side,twi_answer_timeoutis indeed a string 😭This is not a good firecracker solution. But it works fine for me. cc: @MrHertal