Post

Replies

Boosts

Views

Activity

Reply to SwiftData iOS18: "Could not materialize Objective-C class named "Set" from declared attribute value type "Set<String>" of attribute named..."
With that minimal example, (now testing on beta 6), if you add some items, after ~45 seconds those faults appear in the logs. This happens consistently, though doesn't seem to affect functionality. In beta 6, my larger app seems to be able to function fine while still emitting these log lines (previously it would fail to save new models in the context)
Aug ’24
Reply to Xcode 16 Beta 3: "Cannot expand accessors on variable declared with 'let'"
Thank you for confirming the change. Is this going to be a documented limitation of SwiftData? It is useful to be able to express the immutability of particular model attributes. I can understand if SwiftData may now be unable to handle that immutability constraint, but that change seems like it should be a documented property of SwiftData and not just a compiler error. If it isn't a SwiftData design decision but a limitation of macros I would encourage the restoration of the previously shipping behavior.
Jul ’24
Reply to SwiftData iOS18: "Could not materialize Objective-C class named "Set" from declared attribute value type "Set<String>" of attribute named..."
With that minimal example, (now testing on beta 6), if you add some items, after ~45 seconds those faults appear in the logs. This happens consistently, though doesn't seem to affect functionality. In beta 6, my larger app seems to be able to function fine while still emitting these log lines (previously it would fail to save new models in the context)
Replies
Boosts
Views
Activity
Aug ’24
Reply to SwiftData background inserts using ModelActor do not trigger SwiftUI @Query view updates, but background deletes do
This seems to be working for me on iOS17, but regressed in iOS 18 betas (as of beta 5). Filed as FB14750050 I've tried fetching the items from the main context, but it doesn't seem to force a redraw.
Topic: UI Frameworks SubTopic: SwiftUI Tags:
Replies
Boosts
Views
Activity
Aug ’24
Reply to Xcode 16 Beta 3: "Cannot expand accessors on variable declared with 'let'"
Thank you for confirming the change. Is this going to be a documented limitation of SwiftData? It is useful to be able to express the immutability of particular model attributes. I can understand if SwiftData may now be unable to handle that immutability constraint, but that change seems like it should be a documented property of SwiftData and not just a compiler error. If it isn't a SwiftData design decision but a limitation of macros I would encourage the restoration of the previously shipping behavior.
Replies
Boosts
Views
Activity
Jul ’24