An error that is returned when the network is available but cannot be accessed.
- iOS 8.0+
- macOS 10.10+
- Mac Catalyst 13.0+
- tvOS 9.0+
- watchOS 3.0+
Network failure errors can be retried immediately, but your app should implement a backoff timer so that it doesn't attempt the same operation repeatedly.
If the network is unavailable, your app should start monitoring for network reachability and wait to reissue the operation until the network is available again. See
CFNetworkErrors for more information about these errors.
An error indicating that a record or share cannot be saved because doing so would cause the same hierarchy of records to exist in multiple shares.
An error indicating that the content of the specified asset file was modified while being saved.
An error that is returned when the specified container is unknown or unauthorized.
An error indicating that the operation could not be completed on the given database.
An error indicating that the server rejected the request because of a conflict with a unique field.
An error indicating that the current user is not authenticated, and no user record was available.
An error indicating that some items failed, but the operation succeeded overall.
An error indicating that the user did not have permission to perform the specified save or fetch operation.
An error that is returned when saving the record would exceed the user’s current storage quota.
An error that is returned when the target of a record's parent or share reference is not found.
An error indicating that the record was rejected because the version on the server is different.
An error indicating that a share cannot be saved because too many participants are attached to the share.
An error that is returned when the specified record does not exist.
An error indicating that the server is too busy to handle the zone operation.
An error indicating that the specified record zone does not exist on the server.