Here’s more context should you be interested: github.com/pointfreeco/...

If it’s reconstructed from system fields only with `CKRecord.encodeSystemFields(with:)` and `CKRecord.init(coder:)`, the ancestor will contain just the metadata.

I found that if the record you upload was created from a complete archive using `CKRecord.encode(with:)` or fetched directly from CloudKit, the ancestor record is fully populated.

Turns out the behavior isn’t related to encryption after all, but rather to how the record sent to CloudKit is constructed.

In my tests, it seems to include values for encrypted fields but not for unencrypted ones. Though, I couldn’t find any documentation confirming this.

Any hints would be much appreciated. Thanks! 🙏

@jollycoder.com Hi Tim, if I remember correctly, you might know a thing or two about CloudKit. Do you happen to recall whether the `CKError` for `serverRecordChanged` should include an `ancestorRecord` with all fields populated? Or is it just the system ones (i.e. metadata)?

I secured my Bluesky account a while back, but I went all-in on Mastodon with the Swift dev community there.

This post by @mijustin.bsky.social makes it appealing, comparing it to the early days of Twitter:
justinjackson.ca/twitter-blue...

Guess I’ll see how it plays out over the next few months…