Fix: Decouple SwiftData cache failures from data loading#245
Open
Crafter-feng wants to merge 2 commits into
Open
Fix: Decouple SwiftData cache failures from data loading#245Crafter-feng wants to merge 2 commits into
Crafter-feng wants to merge 2 commits into
Conversation
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.
Problem
On iOS 26 (and other versions), SwiftData local SQLite store fails to open with NSCocoaErrorDomain Code=256 during runtime fetch operations. API data loads into memory correctly, but the subsequent SwiftData cache sync error propagates and marks the entire data request as failed. Related: #224, #232
Fix
Change all 30 SwiftData operations from try to try? (29 sync* calls + 1 modelContext.fetch). This makes local caching best-effort:
Changes
GrocyViewModel.swift: 30 try -> try?build.yml: GitHub Actions workflow for automated builds