Swift 向现有Coredata/iCloud应用程序添加集成的步骤

短版本（TLDR）： 将集成集成到已设置为通过iCloud Drive与iCloud同步CoreData的应用程序中的一般步骤是什么？我不知道我将如何使用集成来促进同步过程

长版本： 我是一个新手程序员，我在iCloud/CoreData同步方面遇到了一个大难题（见这里）

除了云同步之外，我的应用程序工作得非常好。所有东西都正确配置为与icloud drive同步——99%的时间都能正常工作——但我会收到一些随机破坏我的应用程序的错误，这些错误来自苹果方面的代码（“图书管理员返回了一个严重错误…”）

我的所有数据都在coredata（sqlite）中，我的应用程序在Swift 2中编程

似乎是一个有助于解决我问题的选择。然而，我完全不知道如何将它集成到我的项目中。我完全被分解整个应用程序的过程所淹没。谁能为我提供一些需要采取的步骤的指导？手册和github自述非常深入，但我不知道我要做什么。压倒性的：(

如果有帮助，下面是我的AppDelegate文件，我希望所有的工作都需要在这里完成

//MARK: General
func backgroundThread(delay: Double = 0.0, background: (() -> Void)? = nil, completion: (() -> Void)? = nil) {
    dispatch_async(dispatch_get_global_queue(Int(QOS_CLASS_USER_INITIATED.rawValue), 0)) {
        if(background != nil){ background!(); }

        let popTime = dispatch_time(DISPATCH_TIME_NOW, Int64(delay * Double(NSEC_PER_SEC)))
        dispatch_after(popTime, dispatch_get_main_queue()) {
            if(completion != nil){ completion!(); }
        }
    }
}


func applicationWillResignActive(application: UIApplication) {
    // Sent when the application is about to move from active to inactive state. This can occur for certain types of temporary interruptions (such as an incoming phone call or SMS message) or when the user quits the application and it begins the transition to the background state.
    // Use this method to pause ongoing tasks, disable timers, and throttle down OpenGL ES frame rates. Games should use this method to pause the game.
}
//

func applicationDidEnterBackground(application: UIApplication) {
    // Use this method to release shared resources, save user data, invalidate timers, and store enough application state information to restore your application to its current state in case it is terminated later.
    // If your application supports background execution, this method is called instead of applicationWillTerminate: when the user quits.
    self.saveContext()

}

func applicationWillEnterForeground(application: UIApplication) {
    // Called as part of the transition from the background to the inactive state; here you can undo many of the changes made on entering the background.
    currentiCloudToken = NSFileManager.defaultManager().ubiquityIdentityToken

}

func applicationDidBecomeActive(application: UIApplication) {
    // Restart any tasks that were paused (or not yet started) while the application was inactive. If the application was previously in the background, optionally refresh the user interface.

}

func applicationWillTerminate(application: UIApplication) {
    // Called when the application is about to terminate. Save data if appropriate. See also applicationDidEnterBackground:.
    // Saves changes in the application's managed object context before the application terminates.
    self.saveContext()
}

// MARK: - Core Data stack

lazy var managedObjectModel: NSManagedObjectModel = {
    // The managed object model for the application. This property is not optional. It is a fatal error for the application not to be able to find and load its model.
    let modelURL = NSBundle.mainBundle().URLForResource("Model", withExtension: "momd")!
    return NSManagedObjectModel(contentsOfURL: modelURL)!
    }()

lazy var persistentStoreCoordinator: NSPersistentStoreCoordinator? = {
    // The persistent store coordinator for the application. This implementation creates and return a coordinator, having added 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.
    // Create the coordinator and store
    var coordinator: NSPersistentStoreCoordinator? = NSPersistentStoreCoordinator(managedObjectModel: self.managedObjectModel)


    let documentsDirectory = NSFileManager.defaultManager().URLsForDirectory(NSSearchPathDirectory.DocumentDirectory, inDomains: NSSearchPathDomainMask.UserDomainMask).last as NSURL!

    let storeURL = documentsDirectory.URLByAppendingPathComponent("ArrivedAlive.sqlite")

    var error: NSError? = nil
    var failureReason = "There was an error creating or loading the application's saved data."
    let storeOptions = [NSPersistentStoreUbiquitousContentNameKey: "ArrivedAliveStore", NSMigratePersistentStoresAutomaticallyOption: true, NSInferMappingModelAutomaticallyOption: true]

    do {
        try coordinator!.addPersistentStoreWithType(NSSQLiteStoreType, configuration: nil, URL: storeURL, options: storeOptions)
    } catch var error1 as NSError {
        error = error1
        coordinator = nil
        // Report any error we got.
        var dict = [String: AnyObject]()
        dict[NSLocalizedDescriptionKey] = "Failed to initialize the application's saved data"
        dict[NSLocalizedFailureReasonErrorKey] = failureReason
        dict[NSUnderlyingErrorKey] = error
        error = NSError(domain: "YOUR_ERROR_DOMAIN", code: 9999, userInfo: dict)
        // Replace this with code to handle the error appropriately.
        // abort() 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.
        NSLog("Unresolved error \(error), \(error!.userInfo)")
        abort()
    } catch {
        fatalError()
    }

    return coordinator
    }()


lazy var managedObjectContext: NSManagedObjectContext? = {
    // Returns the managed object context for the application (which is already bound to the persistent store coordinator for the application.) This property is optional since there are legitimate error conditions that could cause the creation of the context to fail.
    let coordinator = self.persistentStoreCoordinator
    if coordinator == nil {
        return nil
    }
    var managedObjectContext = NSManagedObjectContext(concurrencyType: NSManagedObjectContextConcurrencyType.MainQueueConcurrencyType)

    managedObjectContext.mergePolicy = NSMergeByPropertyObjectTrumpMergePolicy
    managedObjectContext.persistentStoreCoordinator = coordinator

    return managedObjectContext
    }()

// MARK: - Core Data Saving support

func saveContext () {
    if let moc = self.managedObjectContext {
        var error: NSError? = nil
        if moc.hasChanges {
            do {
                try moc.save()
            } catch let error1 as NSError {
                error = error1
                // Replace this implementation with code to handle the error appropriately.
                // abort() 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.
                NSLog("Unresolved error \(error), \(error!.userInfo)")
                abort()
            }
        }
    }
}

---

谢谢！

事实上，在堆栈中添加集成并不需要太多工作。但是，由于您“经验不足”，我建议您不要尝试更改现有堆栈

相反，我建议你重写你的堆栈。它没有那么多的代码。使用这个例子作为你的指南，因为这个应用程序使用iCloud作为它的后端

---

堆栈设置完成后，除了确定何时要同步外，应用程序中无需更改其他内容。

您是否认为“CoreData:Ubiquity:Library”等错误导致启动下载时返回了严重错误error Domain=brCloudDocErrorDomain Code=6”和“CoreData:Ubiquity:Library在开始下载时返回了一个严重错误。错误域=BRCloudDocsErrorDomain Code=5”“URL处没有文档”“将按照该示例进行修复？我的印象是，在幕后发生了一些我无法从这些错误中修复的事情！此外，您还提到了“同步时”“以前，这一切都是由iCloud自己处理的，所以这正是我最困惑的领域：（我之所以提到这一点，是因为您可以将同步设置为在每次保存时自动启动、定期启动和/或手动启动。只需将该实现用作参考，您就会完全了解我所说的内容。谢谢Jody-我感谢您的答复。澄清一下-您认为集成将有助于解决我在我的报告中列出的上述错误吗第一条评论？还是我的一厢情愿？我已经广泛使用了合奏，这是非常棒的。但是，我个人没有使用过iCloud后端，所以我无法回答。我知道iCloud后端被很多人使用，除了最初的设置工作和我正在做的一样。我强烈建议阅读《快速入门》在花了大约3个小时强调实现集成后，我能够在大约45分钟内执行所有更改！您的框架太棒了！！谢谢您！