iOS 9 CoreData / ICloud - URL上没有此类文档

时间:2015-10-09 14:13:57

标签: ios swift core-data icloud

更新2

我偶尔也会收到此错误:

CoreData: Ubiquity:  Librarian returned a serious error for starting downloads Error Domain=BRCloudDocsErrorDomain Code=6

我想知道它是否相关?我正在努力提交错误报告,但我会非常感激。

更新

当发生此错误时,我对coredata的行为非常奇怪,因为它无法在相同的上下文中找到相关对象。这绝对是我的应用程序瘫痪

原始问题

我有一个应用程序似乎可以在90%的时间内完美地将CoreData与iCloud无处不在的存储同步。

有时我收到这个错误,事情开始有点疯狂:

CoreData: Ubiquity:  Librarian returned a serious error for starting downloads Error Domain=BRCloudDocsErrorDomain Code=5 "No document at URL"

我已经搜索过有关如何解决此问题的信息,但在找到的其他问题中,我没有看到任何可以帮助我的信息。许多人只是说他们只是放弃了试图修复它。

任何人都可以看到我的核心数据堆栈会导致这个问题吗?!我觉得我正在服用疯狂的药片。

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

1 个答案:

答案 0 :(得分:0)

对于那些在这些问题上挣扎的人 - 让我给你一些好消息:

要解决此问题,请按以下步骤操作:

  1. 下载并实施Ensembles GitHub
  2. 向appDelegate添加非常少量的代码以创建和管理整体对象
  3. 忍受你被压抑的沮丧 - 你已经完成了。
  4. IT修复了所有云同步错误

    它就像魔法一样,我不会更快乐。它基本上像核心数据和iCloud之间的中间人一样,以确保没有人在中间发作。