When you moved a Core Data app to SwiftData, did concurrency behave the same under load?

Migrating from Core Data to SwiftData can introduce subtle concurrency issues that don't surface in testing but cause stale UI data under load. The key mistake is assuming SwiftData's actor isolation behaves identically to Core Data's managed object contexts. The fix involves forcing explicit refresh points and controlling data access on the main actor. SwiftData abstracts concurrency complexity but does not eliminate the underlying threading hazards.