客户端oplock错误,在CloudKit中保存记录

时间:2016-03-15 13:13:52

标签: ios cloudkit

我有一个oplock错误,从节省时间到CloudKit。我似乎无法找到原因,但我怀疑当我从CloudKit仪表板手动编辑CKRecords然后从应用程序中获取并修改该记录时,就会发生这种情况。有没有人对oplock意味着什么以及我应该从哪里开始寻找解释?

这是错误

Error Error saving record <CKRecordID: 0x79c42d60; 418deec9-ee5e-46b8-8877-606c14a5fe92:(_defaultZone:__defaultOwner__)> to server: client oplock error updating record

这是我的代码,请注意即使我没有更改记录

也会出现错误
    [self.publicDB saveRecord:self.currentUser completionHandler:^(CKRecord *record, NSError *error)
 {


     if(error)
     {
         NSLog(@"Error %@", error.localizedDescription);
     }

     else
     {
         NSLog(@"Saved access to Cloudkit");

     }

 }];

2 个答案:

答案 0 :(得分:13)

您收到此错误是因为服务器上的用户记录版本比您尝试更新的版本更新。如果您使用错误代码 rawValue 14 )并将其映射到 CKErrorCode 枚举,您会看到它映射到:

CKErrorCode.ServerRecordChanged /* The record was rejected because the version
                                   on the server was different */

这就是为什么@shawnynicole上面的答案在尝试保存用户记录之前解决了fetchRecordWithId的问题。

我发现如果解析所有CloudKit错误代码非常有用,并根据Apple的评论添加到消息说明中...否则会收到错误消息,例如:&#34;客户端oplock错误更新记录&#34; !!

CKError代码&amp;注释可以在CloudKit标题中找到:

public enum CKErrorCode : Int { 
  case InternalError /* CloudKit.framework encountered an error.  This is a non-recoverable error. */
  case PartialFailure /* Some items failed, but the operation succeeded overall */
  case NetworkUnavailable /* Network not available */
  case NetworkFailure /* Network error (available but CFNetwork gave us an error) */
  case BadContainer /* Un-provisioned or unauthorized container. Try provisioning the container before retrying the operation. */
  case ServiceUnavailable /* Service unavailable */
  case RequestRateLimited /* Client is being rate limited */
  case MissingEntitlement /* Missing entitlement */
  case NotAuthenticated /* Not authenticated (writing without being logged in, no user record) */
  case PermissionFailure /* Access failure (save or fetch) */
  case UnknownItem /* Record does not exist */
  case InvalidArguments /* Bad client request (bad record graph, malformed predicate) */
  case ResultsTruncated /* Query results were truncated by the server */
  case ServerRecordChanged /* The record was rejected because the version on the server was different */
  case ServerRejectedRequest /* The server rejected this request.  This is a non-recoverable error */
  case AssetFileNotFound /* Asset file was not found */
  case AssetFileModified /* Asset file content was modified while being saved */
  case IncompatibleVersion /* App version is less than the minimum allowed version */
  case ConstraintViolation /* The server rejected the request because there was a conflict with a unique field. */
  case OperationCancelled /* A CKOperation was explicitly cancelled */
  case ChangeTokenExpired /* The previousServerChangeToken value is too old and the client must re-sync from scratch */
  case BatchRequestFailed /* One of the items in this batch operation failed in a zone with atomic updates, so the entire batch was rejected. */
  case ZoneBusy /* The server is too busy to handle this zone operation. Try the operation again in a few seconds. */
  case BadDatabase /* Operation could not be completed on the given database. Likely caused by attempting to modify zones in the public database. */
  case QuotaExceeded /* Saving a record would exceed quota */
  case ZoneNotFound /* The specified zone does not exist on the server */
  case LimitExceeded /* The request to the server was too large. Retry this request as a smaller batch. */
  case UserDeletedZone /* The user deleted this zone through the settings UI. Your client should either remove its local data or prompt the user before attempting to re-upload any data to this zone. */
}

答案 1 :(得分:5)

我也遇到了这个错误。

我通过确保始终先调用saveRecord,然后在fetchRecordWithID完成处理程序中调用fetchRecordWithID来解决此问题。

请注意CKErrorCodeUnknownItem将返回saveRecord以获取新记录。务必妥善处理错误。我绕过了这个错误,以便我的代码继续到saveRecord,这会将记录插入到CloudKit中(假设var obj = JsonConvert.DeserializeObject<List<RootObject>>(responseText); var traces = obj.Select(item => new Dictionary<string, string> { { "date", item.trace.details.date }, { "type", item.trace.details.type } }); 当然没有错误)。