Fix crash when CloudKit returns records without fields#3
Merged
Merged
Conversation
CloudKit's records/lookup endpoint can return records without a "fields" key (e.g. not-found or deleted records), causing a keyNotFound decoding error. This adds a custom Decodable init that defaults fields to an empty dictionary, and filters out fieldless records from lookupRecords so the get command correctly falls through to uniqueIdentifier search. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
asabirov
force-pushed
the
fix/handle-missing-fields-in-record-lookup
branch
from
84098f4 to
33c0ca5
Compare
asabirov
pushed a commit
that referenced
this pull request
Apr 8, 2026
Extract BearCLICore library and add test infrastructure
This was referenced Apr 8, 2026
Closed
Closed
asabirov
added a commit
that referenced
this pull request
Apr 8, 2026
Add custom CKRecord decoder that handles missing/empty fields gracefully instead of crashing on decode. Add tests for record decoding edge cases. (reimplements PR #3)
asabirov
added a commit
that referenced
this pull request
Apr 8, 2026
Add custom CKRecord decoder that handles missing/empty fields gracefully instead of crashing on decode. Add tests for record decoding edge cases. (reimplements PR #3)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
records/lookupcan return records without afieldskey (not-found/deleted records), causing akeyNotFounddecoding crashDecodableinit forCKRecordthat defaultsfieldsto[:]when missinglookupRecordssogetcorrectly falls through touniqueIdentifiersearchBearNoteedge casesTest plan
swift test— all 7 tests passswift run bcli get <invalid-id>— returns clean "Note not found" instead of decoding crash