客户端 oplock 错误，将记录保存在 CloudKit

Question

我有一个从节省时间到 CloudKit 时发生的 oplock 错误。我似乎无法找出原因，但我怀疑当我从 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");

     }

 }];

Answer 1

我也有这个错误。

我通过确保总是先调用 fetchRecordWithID，然后在 fetchRecordWithID 完成处理程序中调用 saveRecord 来解决它。

请注意，fetchRecordWithID 将 return CKErrorCodeUnknownItem 用于新记录。请务必正确处理错误。我绕过了这个错误，这样我的代码将继续到 saveRecord，这会将记录插入 CloudKit（当然前提是 saveRecord 没有错误）。

Answer 2

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

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

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

我发现解析所有 CloudKit 错误代码并根据 Apple 的评论添加到消息描述中是否很有帮助...否则您会收到如下错误消息："client oplock error updating record"！！

CKError 代码和注释可以在 CloudKit headers:

中找到

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. */
}

客户端 oplock 错误，将记录保存在 CloudKit

Client oplock error, saving records in CloudKit

ios

cloudkit