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

Question

bounty到期在5天内。该问题的答案有资格获得+ 200声望赏金。Igor R.想要引起更多关注对此问题。

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

在AppDelegate.swift中，我没有更改Core Data stack标记以下的代码。在代码中，我没有在任何地方指定区域。

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

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

我在朋友设备上测试了我的应用程序（现在可以直接从App Store下载）-可以正常工作，但请注意：她的设备也在开发过程中使用（我将它们连接到Mac并通过Xcode构建和安装应用程序的时间）。

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

1. com.apple.coredata.cloudkit.zone
2. _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和/或删除其私有数据库，仍然可以解释稍微增加的情况。

祝你好运！