删除并重新部署应用程序后,iOS CoreData + iCloud中的错误消息 [英] Error messages in iOS CoreData + iCloud after deleting and redeploying app

查看:233
本文介绍了删除并重新部署应用程序后,iOS CoreData + iCloud中的错误消息的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

应用程序从一开始就放在iCloud中,因此我有机会用数据填充它,并看到在其他设备上发生的同步。
但是,在一个设备上删除和重新部署应用程序后,我开始遇到问题。

The application has been put in iCloud since the beginning, so I have the opportunities to fill it with data, and see synchronization happening on other devices. However I am starting to have problems after deleting and redeploying the application on one device only.

特别是,在启动时,现在需要花很多时间:

In particular, at startup, it's taking a lot at this point:

NSLog(@"add coordinator");
if (![__persistentStoreCoordinator addPersistentStoreWithType:NSSQLiteStoreType configuration:nil URL:storeURL options:options error:&error]) {
    NSLog(@"Unresolved error %@, %@", error, [error userInfo]);
    abort();
}
NSLog(@"finish");

我可以在控制台中看到添加协调器,然后它似乎永远处于暂停状态。

I can see "add coordinator" in console, then it seems to be in pause forever. Instead by activating core data logging, I can see that is doing a lot of select and update.

然后,显示每个事务编号的日志错误消息的无限列表:

Then an infinite list of log error messages for each transactionNumber is shown:

CoreData: Ubiquity: Error importing transaction log: <PFUbiquityTransactionLog: 0x1929e350>
    transactionLogLocation: <PFUbiquityLocation: 0x17bf1c40>: /private/var/mobile/Library/Mobile Documents/6G8M57K6MU~myapp/mobile.63606F7B-D6A9-5937-9160-126AC1315EBF/myAppCloud/3IEWV8FXM6GJ58H5PkyqFsyuoUZ2qIOuJOfon1QIYC4=/035A5A1C-F893-4B67-A784-866A4DE1B3F1.1.cdt
    transactionNumber: 1
, exception: -[__NSCFDictionary setObject:forKey:]: attempt to insert nil key
-[_PFUbiquityRecordsImporter operation:failedWithError:](839): CoreData: Ubiquity:  Import operation encountered an error: Error Domain=NSCocoaErrorDomain Code=134060 "The operation couldn’t be completed. (Cocoa error 134060.)" UserInfo=0x194c9f40 {exception=-[__NSCFDictionary setObject:forKey:]: attempt to insert nil key} while trying to import the log file at the URL: <PFUbiquityTransactionLog: 0x1929e350>
    transactionLogLocation: <PFUbiquityLocation: 0x17bf1c40>: /private/var/mobile/Library/Mobile Documents/6G8M57K6MU~myapp/mobile.63606F7B-D6A9-5937-9160-126AC1315EBF/myAppCloud/3IEWV8FXM6GJ58H5PkyqFsyuoUZ2qIOuJOfon1QIYC4=/035A5A1C-F893-4B67-A784-866A4DE1B3F1.1.cdt
    transactionNumber: 1

然后我说,

推荐答案

苹果工程师回复了我的问题到我在Apple Dev论坛上做的一篇文章,说这是一个已知的bug,已经在即将到来的iOS 6上修复。

An Apple engineer replied me to a post I did on Apple Dev forum, stating that this is a known bug that has been fixed on forthcoming iOS 6.

所以,没有解决方案,并重新启动。
在这一点上,我想我会发货CoreData没有iCloud。

So, there's no solution than scratching all data on devices and start again. At this point, I suppose I will ship with CoreData without iCloud.

这篇关于删除并重新部署应用程序后,iOS CoreData + iCloud中的错误消息的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆