ios - 如何修复 CloudKit 仪表板中的 ZONE_NOT_FOUND 错误？

Question

在我的应用程序中，我使用 CloudKit 来同步核心数据数据(创建项目时选中了“使用核心数据”和“使用 CloudKit”复选框)。

在 AppDelegate.swift我没有更改下面的代码 核心数据栈 标记。在代码中，我没有在任何地方指定区域。

在开发过程中，我使用相同的 iCloud 帐户在我的设备上测试了应用程序。同步运行良好。测试后，我将开发模式部署到生产模式。后来，我在 App Store 上发布了一个应用程序。

现在在 CloudKit 仪表板中，在生产 > 遥测模块中我看到 ZONE_NOT_FOUND错误计数大约等于我的用户数。



我在我的 friend 设备上测试了我的应用程序(现在直接从 App Store 下载)——同步工作，但要注意:她的设备也在开发过程中使用(我将它们连接到我的 Mac 并从 Xcode 构建和安装应用程序多次)。

另一个注意事项:当我转到 CloudKit 仪表板中生产部分的数据模块时，在区域菜单中，我看到 2 个选项:

com.apple.coredata.cloudkit.zone

_defaultZone

当我按“查询记录”时，我只在 com.apple.coredata.cloudkit.zone 时看到我的数据行。选择。
AppDelegate.swift :

import UIKit
import CoreData
import StoreKit

@UIApplicationMain
class AppDelegate: UIResponder, UIApplicationDelegate {



func application(_ application: UIApplication, didFinishLaunchingWithOptions launchOptions: [UIApplication.LaunchOptionsKey: Any]?) -> Bool {
    // Register for Remote Notifications
    application.registerForRemoteNotifications()

    // Override point for customization after application launch.

    return true
}

// MARK: UISceneSession Lifecycle

func application(_ application: UIApplication, configurationForConnecting connectingSceneSession: UISceneSession, options: UIScene.ConnectionOptions) -> UISceneConfiguration {
    // Called when a new scene session is being created.
    // Use this method to select a configuration to create the new scene with.
    return UISceneConfiguration(name: "Default Configuration", sessionRole: connectingSceneSession.role)
}

func application(_ application: UIApplication, didDiscardSceneSessions sceneSessions: Set<UISceneSession>) {
    // Called when the user discards a scene session.
    // If any sessions were discarded while the application was not running, this will be called shortly after application:didFinishLaunchingWithOptions.
    // Use this method to release any resources that were specific to the discarded scenes, as they will not return.
}

// MARK: - Core Data stack

lazy var persistentContainer: NSPersistentCloudKitContainer = {
    /*
     The persistent container for the application. This implementation
     creates and returns a container, having loaded the store for the
     application to it. This property is optional since there are legitimate
     error conditions that could cause the creation of the store to fail.
    */
    let container = NSPersistentCloudKitContainer(name: "AppTitle")

    guard let description = container.persistentStoreDescriptions.first else {
        fatalError("No Descriptions found")
    }
    description.setOption(true as NSObject, forKey: NSPersistentStoreRemoteChangeNotificationPostOptionKey)

    container.loadPersistentStores(completionHandler: { (storeDescription, error) in
        if let error = error as NSError? {
            // Replace this implementation with code to handle the error appropriately.
            // fatalError() causes the application to generate a crash log and terminate. You should not use this function in a shipping application, although it may be useful during development.

            /*
             Typical reasons for an error here include:
             * The parent directory does not exist, cannot be created, or disallows writing.
             * The persistent store is not accessible, due to permissions or data protection when the device is locked.
             * The device is out of space.
             * The store could not be migrated to the current model version.
             Check the error message to determine what the actual problem was.
             */
            fatalError("Unresolved error \(error), \(error.userInfo)")
        }
    })

    container.viewContext.automaticallyMergesChangesFromParent = true
    container.viewContext.mergePolicy = NSMergeByPropertyObjectTrumpMergePolicy

    NotificationCenter.default.addObserver(self, selector: #selector(self.processUpdate), name: .NSPersistentStoreRemoteChange, object: nil)

    return container
}()

// MARK: - Core Data Saving support

func saveContext () {
    let context = persistentContainer.viewContext
    if context.hasChanges {
        do {
            try context.save()
        } catch {
            // Replace this implementation with code to handle the error appropriately.
            // fatalError() causes the application to generate a crash log and terminate. You should not use this function in a shipping application, although it may be useful during development.
            let nserror = error as NSError
            fatalError("Unresolved error \(nserror), \(nserror.userInfo)")
        }
    }
}

@objc
func processUpdate(notification: NSNotification) {
    operationQueue.addOperation {
        // process notification
        let context = self.persistentContainer.newBackgroundContext()
        if context.hasChanges {
            do {
                try context.save()
            } catch {
                let nserror = error as NSError
                fatalError("Unresolved error \(nserror), \(nserror.userInfo)")
            }
        }
    }
}

lazy var operationQueue: OperationQueue = {
    var queue = OperationQueue()
    queue.maxConcurrentOperationCount = 1
    return queue
}()

}

这个错误让我很担心，当应用程序已经在生产中时我能做些什么来修复它，让它消失？

Answer 1

鉴于事实:

CoreData+CloudKit 同步工作

ZONE_NOT_FOUND发生错误 正是 每个用户一次

和假设:

您自己没有直接查询该区域。

我不会太担心这个错误。

我的想法:

最有可能的是，在安装后首次使用时，CoreData+CloudKit 集成正在检查常规区域 com.apple.coredata.cloudkit.zone 的存在。用于通过查询进行同步。当集成达到 ZONE_NOT_FOUND错误，它将创建它。

通过查询所有区域并检查结果，Apple 可能会更加优雅。但是，如果您已经配置了很多区域，则试错法具有性能优势。

也就是说，我坚信您对此无能为力。

如果每个用户的错误率增加，我仍然会关注它。

但是，如果用户退出 iCloud 和/或删除他们的私有(private)数据库，仍然可以解释轻微的增加。

祝你好运!