Post

Replies

Boosts

Views

Activity

Reply to iOS 26 SwiftData crash does not happen in iOS 16
I have double checked my models against the incoming JSON and it all matches up properly. I inserted the recommended code above and it indeed crashes on the modelContext.save but it never gets to the catch. It simply display a SIGABRT stating "An abort signal terminated the process. Such crashes often happen because of an uncaught exception or unrecoverable error or calling the abort() function." Executing the exact same code works perfectly in iOS 18 without any changes. Calling the same endpoint and using the same JSON returned by that endpoint works without a hitch. It seems to me that if the code works in iOS 18 and fails in iOS 26, that seems to be indicative of a change in the framework that I cannot check, no?
Topic: App & System Services SubTopic: iCloud Tags:
Sep ’25
Reply to Crash when adding large JSON data to SwiftData: Could not cast value of type '__NSCFBoolean' to 'NSString'
I have additional information on this issue. When I look at the raw JSON data as received from the API call, all of the data is present, but when I look at the data after I decode it, several fields have empty strings which did have string data in the original response. In particular, display_name, list_name and list_name_encoded all have empty strings. Why would the decoding fail on simple strings and set the value to the default ""? I have uploaded JSONData.json and RawData.JSON to the above GitHub project show the differences.
Jul ’25
Reply to iOS 26 SwiftData crash does not happen in iOS 16
I have double checked my models against the incoming JSON and it all matches up properly. I inserted the recommended code above and it indeed crashes on the modelContext.save but it never gets to the catch. It simply display a SIGABRT stating "An abort signal terminated the process. Such crashes often happen because of an uncaught exception or unrecoverable error or calling the abort() function." Executing the exact same code works perfectly in iOS 18 without any changes. Calling the same endpoint and using the same JSON returned by that endpoint works without a hitch. It seems to me that if the code works in iOS 18 and fails in iOS 26, that seems to be indicative of a change in the framework that I cannot check, no?
Topic: App & System Services SubTopic: iCloud Tags:
Replies
Boosts
Views
Activity
Sep ’25
Reply to Crash when adding large JSON data to SwiftData: Could not cast value of type '__NSCFBoolean' to 'NSString'
I have additional information on this issue. When I look at the raw JSON data as received from the API call, all of the data is present, but when I look at the data after I decode it, several fields have empty strings which did have string data in the original response. In particular, display_name, list_name and list_name_encoded all have empty strings. Why would the decoding fail on simple strings and set the value to the default ""? I have uploaded JSONData.json and RawData.JSON to the above GitHub project show the differences.
Replies
Boosts
Views
Activity
Jul ’25