We are investigating one completed CloudKit Development test in a separate test container using only synthetic data.
Shortly before an iOS client attempted to fetch a record from the public database’s default zone, that synthetic record was visible in CloudKit Console.
The native client returned:
CKErrorDomain code 11 (unknownItem)- Underlying
CKInternalErrorDomain code 2003 - Sanitized diagnostic:
record_not_found - No record
We verified that the client’s intended container, database, zone and record name matched the reference.
A CloudKit Console event showed RecordFetch, operation-level SUCCESS, and approximately 171 ms execution time. However:
- The event was correlated by context and timestamp, not by a directly matched client operation or request ID.
- The available event did not expose a per-record result or an authorization decision.
- Earlier Console visibility does not establish availability or client access at the exact time of the fetch.
The cause therefore remains unresolved. We have not established that a permissions restriction caused the error.
We understand that Apple documents unknownItem for a nonexistent record and permissionFailure for insufficient permission to fetch or save data. We also understand that operation-level success and per-record fetch success are distinct.
Our questions are:
- Can a public-database read restriction cause an existing record to be reported to a native client as
unknownItem, rather thanpermissionFailure? If so, is this documented behavior? - What does operation-level
SUCCESSmean specifically for aRecordFetchevent in CloudKit Console? Can that event still contain an unsuccessful individual record lookup? - Which supported diagnostics can distinguish a missing or unavailable record from an authorization-based visibility restriction?
- Can Apple determine the authorization outcome of an existing request from retained diagnostics, and which correlation identifiers are required?
- What evidence is sufficient to verify server-enforced read restrictions in Development while preserving the existing roles and leaving production untouched?
We are seeking clarification of the existing evidence, not proposing another reproduction attempt. No customer data, credentials or production records are involved.