When onboarding engineers into async SwiftUI code,what kind of bug tends to slip through at thestart

When onboarding engineers into async SwiftUI code, a common bug involves adding async tasks directly inside view lifecycle methods. While tests pass, under real load tasks overlap and cancel incorrectly, causing stale UI state. The fix is isolating all async logic behind a single coordinator, removing direct async calls from views entirely, which makes behavior predictable and eliminates race conditions.