Fatal error: Unexpectedly found nil while unwrapping an Optional value

You force-unwrapped an optional that was nil.

Why this happens

Swift uses optionals to represent values that might be absent. When you use ! to force-unwrap an optional, you’re telling the compiler “I guarantee this has a value.” If it’s actually nil at runtime, Swift crashes immediately. This commonly happens with unconnected IBOutlets, failed type casts, and dictionary lookups that return nil.

Fix 1: Use optional binding

// ❌ Force unwrap — crashes if nil
let name: String? = nil
print(name!)

// ✅ Safe unwrap
if let name = name {
    print(name)
}

// ✅ Guard let
guard let name = name else { return }
print(name)

Fix 2: Use nil coalescing

let name: String? = nil
print(name ?? "Unknown")

Fix 3: Optional chaining

let length = name?.count  // Returns nil if name is nil

Alternative solutions

For IBOutlets that crash on access, verify the connection in Interface Builder. A disconnected or misnamed outlet will be nil at runtime:

// ❌ Implicitly unwrapped — crashes if not connected
@IBOutlet var label: UILabel!

// ✅ Check before using
guard let label = label else {
    fatalError("label IBOutlet is not connected in storyboard")
}

Prevention

• Avoid ! force-unwraps entirely. Use if let, guard let, or ?? as a habit.
• Enable the “Strict Concurrency Checking” build setting — it catches more optional-related issues at compile time.

Related: Kotlin: NullPointerException fix · C#: NullReferenceException fix · Android: NetworkOnMainThreadException fix