1
votes

In my app I use CloudKit to sync Core Data data ("Use Core Data" and "Use CloudKit" checkboxes were checked when creating a project).

In AppDelegate.swift I did not change code below Core Data stack mark. In code I don't specified zone anywhere.

During development I tested app on my devices using same iCloud account. Sync worked well. After testing I deployed my Development schema to Production schema. Later, I published an app on App Store.

Now in CloudKit Dashboard, in Production > Telemetry module I see ZONE_NOT_FOUND errors with a count that equals to approximately number of my users.

ZONE_NOT_FOUND error in CloudKit Dashboard

I tested my app (now downloaded directly from App Store) on my friend devices — sync working, but one note: her devices were used during development, too (I connected them to my Mac and build and install app from Xcode a number of times).

Another note: when I go to Data module in Production section in CloudKit Dashboard, in Zone menu I see 2 options:

  1. com.apple.coredata.cloudkit.zone
  2. _defaultZone

And when I press "Query Records", I see my data rows only when com.apple.coredata.cloudkit.zone selected.

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
}()

}

This error worries me, what can I do when app already in production to fix it, make it go away?

1

1 Answers

1
votes

Given the facts:

  • CoreData+CloudKit sync is working
  • The ZONE_NOT_FOUND error occurs exactly once per user

And the assumption:

  • That you yourself are not querying for the zone directly.

I would not be too concerned about this error.

My thoughts:

  • Most likely, upon first usage after install, the CoreData+CloudKit integration is checking the existence of the conventional zone com.apple.coredata.cloudkit.zone used for syncing by querying it. When the integration hits the ZONE_NOT_FOUND error, it will create it.

  • Apple could be more graceful by querying all zones and checking the result. However, if you had plenty zones already configured, the trial-and-error methodology has a performance advantage.

That is, I strongly believe that you cannot do much about it.

I would still keep an eye on it if the error per user ratio increases.

However, a slight increase can still be explained if a user signs out of of iCloud and/or deletes their private database.

Best of luck!