Did you ever see navigation break because of async timing?

A subtle iOS/SwiftUI navigation bug where async work outlives the screen that triggered it. When a view loads data with await and then pushes the next screen, the navigation state update can be silently ignored if the task completes after the view has already disappeared. The fix is moving async work into the parent view model so the task lifecycle is properly managed.