AppIntent中Core Data查询在App后台运行时崩溃问题求助

问题描述 #

当App在后台运行时，执行AppIntent的Core Data查询会触发EXC_BREAKPOINT崩溃；但App完全关闭时查询正常。尝试用performAndWait包裹查询后，在排序访问isArchived时依然崩溃。

现有代码 #

Core Data处理类 #

class HomesHandler: NSObject, ObservableObject {
    static let shared = HomesHandler()
    
    let objectContext = PersistenceController.shared.container.viewContext

    func fetchAllHomes() -> [Home] {
        let request: NSFetchRequest<Home> = Home.fetchRequest()
        
        // PERFORM FETCH
        do {
            return try objectContext.fetch(request)
        } catch let error {
            print("Error fetching Homes: \(error.localizedDescription)")
            return []
        }
    }
}

AppIntent查询代码 #

struct HomeIntentQuery: EntityPropertyQuery {
    // Populates the list when the user taps on a parameter that accepts a Home.
    func suggestedEntities() async throws -> [HomeIntentEntity] {
        // Fetch All Homes
        // Sorted by non-archived first
        let allHomes = HomesHandler.shared.fetchAllHomes().sorted(by: { !$0.isArchived && $1.isArchived })
        
        // Map Core Data to AppEntity
        return allHomes.map { home in
            HomeIntentEntity(id: home.id,
                             title: home.wrappedTitle,
                             isArchived: home.isArchived)
        }
    }

    // …

Intent实体定义 #

struct HomeIntentEntity: AppEntity, Identifiable {
    // Required to conform to Identifiable
    var id: UUID
    
    // Properties mirrored from Core Data
    @Property(title: "Title") var title: String
    @Property(title: "Is Archived") var isArchived: Bool
    
    
    // …
}

Core Data持久化控制器 #

struct PersistenceController {
    static let shared = PersistenceController()

    let container: NSPersistentContainer

    // An initializer to load Core Data,
    // optionally able to use an in-memory store.
    init(inMemory: Bool = false) {
        // Access actual Core Data file
        container = NSPersistentContainer(name: "MeterStats")
        
        if inMemory {
            container.persistentStoreDescriptions.first!.url = URL(fileURLWithPath: "/dev/null")
        }
        
        container.loadPersistentStores(completionHandler: { (storeDescription, error) in
            if let error = error as NSError? {
                fatalError("Core Data Loading Error: \(error), \(error.userInfo)")
            }
        })
        container.viewContext.automaticallyMergesChangesFromParent = true
    }
}

解决方案 #

崩溃核心原因是Core Data上下文线程安全违规：AppIntent的suggestedEntities()运行在后台队列，但直接使用了绑定主线程的viewContext，且在上下文线程外访问托管对象属性，触发线程安全检查崩溃。

正确处理步骤 #

1. 为AppIntent创建专用后台上下文
   避免直接使用viewContext，从持久化容器创建私有队列上下文，确保所有Core Data操作在指定线程执行。
2. 在上下文队列内完成所有托管对象操作
   查询、排序、属性读取都必须在上下文的队列闭包内完成，托管对象及其属性仅能在创建它们的上下文线程中访问。
3. 复制属性到值类型后返回
   将Core Data托管对象的属性提取到普通结构体（如HomeIntentEntity）后再传递到队列外，避免持有托管对象引用。

修改后的代码示例 #

更新HomesHandler的查询方法

class HomesHandler: NSObject, ObservableObject {
    static let shared = HomesHandler()
    
    private let container = PersistenceController.shared.container

    func fetchAllHomes() async throws -> [HomeIntentEntity] {
        // 创建私有队列后台上下文
        let backgroundContext = container.newBackgroundContext()
        backgroundContext.automaticallyMergesChangesFromParent = true
        
        return try await backgroundContext.perform {
            let request: NSFetchRequest<Home> = Home.fetchRequest()
            // 直接在请求中添加排序，比fetch后再排序更高效
            request.sortDescriptors = [
                NSSortDescriptor(keyPath: \Home.isArchived, ascending: true)
            ]
            
            let homes = try backgroundContext.fetch(request)
            // 在上下文队列内完成属性读取与映射
            return homes.map { home in
                HomeIntentEntity(
                    id: home.id,
                    title: home.wrappedTitle,
                    isArchived: home.isArchived
                )
            }
        }
    }
}

更新AppIntent的查询实现

struct HomeIntentQuery: EntityPropertyQuery {
    func suggestedEntities() async throws -> [HomeIntentEntity] {
        return try await HomesHandler.shared.fetchAllHomes()
    }

    // …
}

崩溃原因补充 #

• 直接用viewContext在后台队列执行fetch：viewContext绑定主线程，后台调用属于线程违规。
• 使用performAndWait但外部访问属性：闭包执行完成后，托管对象回到非上下文线程，此时读取属性触发线程安全检查崩溃。
• Alex Hay的示例能正常运行，是因为在perform闭包内完成了所有托管对象操作与映射，未在外部持有或访问托管对象。

内容的提问来源于stack exchange，提问作者alexkaessner