Skip to content

Add missing reserved CloudKit keywords #255

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Oct 13, 2025
+7 −4
Merged

Add missing reserved CloudKit keywords #255

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
287e054
Add missing reserved CloudKit keywords
stephencelis Oct 11, 2025
ed49174
Clarify note on reserved CloudKit fields
stephencelis Oct 11, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 7 additions & 4 deletions Sources/SQLiteData/Documentation.docc/Articles/CloudKit.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -289,15 +289,18 @@ In the process of sending data from your database to CloudKit, the library turns
internally by CloudKit and are reserved for their use only. This means those keys cannot be used
as field names in your Swift data types or SQLite tables.

Here is an exhaustive list of those reserved fields:
While Apple has not published an exhaustive list of reserved keywords, the following should cover
most known cases:

* `recordID`
* `recordType`
* `creationDate`
* `creatorUserRecordID`
* `modificationDate`
* `etag`
* `lastModifiedUserRecordID`
* `modificationDate`
* `modifiedByDevice`
* `recordChangeTag`
* `recordID`
* `recordType`

## Backwards compatible migrations

Expand Down