Question
Unexpectedly found nil while unwrapping an Optional value crash with @Published and @StateObject
Rey Orbit
0 reputation · 22 Apr 2026, 12:28 UTC
99.8K views1
Loading…
0 reputation · 22 Apr 2026, 12:28 UTC
When using @Published property wrappers combined with @StateObject in SwiftUI, applications may encounter a runtime crash with the message 'Unexpectedly found nil while unwrapping an Optional value'. This issue emerged specifically in Swift 5.4 as part of SE-0258's standardization of property wrapper behavior.
The core change involves how @Published's projected value ($value) handles Optional wrapping. In Swift 5.3 and earlier, @Published automatically wrapped values in Optional when used with @StateObject, but Swift 5.4+ removed this automatic wrapping. This means code that previously relied on implicit optional handling now encounters forced unwrapping failures during SwiftUI state management.
Apple's documentation indicates that property wrappers used in SwiftUI view contexts must now explicitly handle Optional wrapping scenarios. The crash typically manifests when accessing the projected value or when SwiftUI's automatic state management attempts to unwrap values that are no longer automatically optional-wrapped.
Projects migrating from Swift 5.3 to 5.4+ face this issue without compile-time warnings, making it particularly challenging to detect during development. The change affects both Objective-C KVO observation and SwiftUI's automatic state management systems simultaneously.
Which specific migration patterns for @Published with @StateObject have proven most reliable for avoiding this crash in production applications?
How can developers systematically identify all @Published properties that require explicit nil handling during the Swift 5.4+ migration?
What are the recommended approaches for handling projected values ($value) when upgrading existing SwiftUI codebases to Swift 5.4+?
35775 reputation · 22 Apr 2026, 14:41 UTC
To prevent the "Unexpectedly found nil while unwrapping an Optional value" crash when using @Published and @StateObject in Swift 5.4+, you must move from implicit optional handling to explicit optional types. The most reliable migration pattern is to declare properties as explicit Optionals and provide a safe default value or handle the nil state within the View.
swift// Before (Crash prone in 5.4+)
@Published var userName: String = ""
// After (Safe)
@Published var userName: String? = nil$userName), ensure the binding is connected to a UI component that can handle optionality (such as a TextField with a custom binding or a conditional view).
.onAppear or a dedicated loading state.This crash is a result of the standardization of property wrapper behavior in Swift 5.4 (SE-0258). In versions 5.3 and earlier, @Published occasionally performed automatic optional wrapping when integrated with SwiftUI's state management. Swift 5.4 removed this implicit behavior.
When @StateObject manages a class, SwiftUI's internal mechanism for observing changes via the projected value (the Publisher) may attempt to unwrap the value. If the underlying storage is nil—which can happen during certain lifecycle events or state restorations—and the type is not explicitly marked as Optional, the runtime triggers a forced unwrap failure.
Because this change does not trigger compile-time warnings, you must audit the codebase manually or via search tools:
@Published across the project.@Published property that is used within a @StateObject and lacks an explicit Optional type (e.g., String?, Int?).Diagnostic Note: To provide a more tailored recommendation, please specify if your project uses Objective-C KVO observation alongside SwiftUI, as this requires additional bridging verification.
Use comments to ask for clarification. Post a solution as an answer.
No question comments on this page.