Thread 1: signal SIGABRT (app crashes with "libc++abi: terminating")
The app deliberately aborted — an uncaught exception, failed assertion or fatalError. The console above the crash has the real message.
Seen on:
iOS
Meaning
SIGABRT is the symptom. Common causes: unconnected IBOutlets (NSUnknownKeyException), storyboard/identifier mistakes, missing Info.plist privacy strings, force casts, or NSInvalidArgumentException from unrecognized selectors. Add an Exception Breakpoint to stop where it’s thrown.
Common causes
- Uncaught Objective-C exception (NSUnknownKeyException, NSInvalidArgumentException)
- Storyboard/XIB outlet or identifier mismatch
- Missing usage description in Info.plist
- fatalError / precondition failure
⚡ Quick fix
- Read the console output above “libc++abi: terminating”
- Add an Exception Breakpoint (Breakpoint navigator → + → Exception Breakpoint)
- Fix the outlet/identifier/plist entry named in the message
Detailed fix by platform
Xcode
# Breakpoint navigator → + → Exception Breakpoint… (All exceptions, On throw)
How to diagnose
- Console — Reason line (*** Terminating app due to uncaught exception)
- Breakpoint — Where is it thrown?
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
- ArithmeticException java.lang.ArithmeticException: / by zero
- attempted to access privacy-sensitive data without a usage description This app has crashed because it attempted to access privacy-sensitive data without a usage description
- Could not cast value of type Swift: Could not cast value of type 'X' to 'Y'
Most viewed in iOS
Other ways to find it
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
Was this page helpful?
Report a correction or suggest an improvement
Last updated 7 Oct 2026