How to fix NSCloudSharingConflictError
This iCloud sharing error means two changes collided on a shared item. Fetching the latest version and resolving before saving fixes it. Jump to your situation below or work through the methods in order.
This iCloud sharing error means two changes collided on a shared item. Fetching the latest version and resolving before saving fixes it. Jump to your situation below or work through the methods in order.
NSCloudSharingConflictError is an Apple Foundation error (code 5123) meaning a conflict occurred while saving changes to a shared iCloud item (the CKShare or its root CKRecord). It happens when two devices or participants change the same shared item at close to the same time, so the change you are trying to save is based on an out-of-date version and the server rejects it to avoid overwriting the other change. Apple's guidance is to fetch the server's current version first, then resolve the conflict, either by merging automatically or by presenting the difference so the user chooses, and retry the save. For an end user this means refreshing the shared item, keeping one version, and saving again. Ensuring all participants are on a stable connection reduces repeat collisions. Because the block is a version mismatch, syncing to the latest and re-saving resolves it.
Shared iCloud items are edited by more than one device or person. This error means your save was based on a version that is no longer current, because someone else changed the item first, so the server refuses it rather than lose their change.
The resolution follows Apple's own guidance: pull down the server's latest version, reconcile it with your change, and save again. In everyday terms, refresh the shared item, decide which version to keep, and re-save on a stable connection.
“A sharing conflict is exactly what it sounds like, two edits landing on the same shared item and the server refusing to let one silently clobber the other. The right move, and Apple says this too, is to fetch the current version first, then reconcile, either merge it or let the user pick which version wins, and save again. For a normal user that is just: refresh the shared file, keep the version you want, and re-save. Doing it on a solid connection stops it looping.”
NSCloudSharingConflictError is a version conflict on a shared iCloud item. Fetch the server's current version first, resolve the conflict by merging or choosing which version to keep, then retry the save. Editing on a stable connection reduces repeat collisions.
If conflicts recur even after refreshing, the shared item's local cache may be stale; for an app, re-fetching the CKShare and root record clears it, and for a user, removing and re-adding the shared item forces a clean copy. You can also submit your error to us for a tailored fix.
