“SwiftData inheritance relationship”

In any SwiftData project with undo enabled, I noticed that repeatedly undoing and redoing a change will cause memory to continuously climb. The larger the change, the more memory is consumed. This is surprising to me. I confirmed this on iOS and macOS using Xcode 15.4 and 16 beta. To reproduce, simply add undo/redo functionality to any project and repeatedly undo/redo a change. Memory consumption will climb continuously and will not get released. In Paul Hudson's SwiftData tutorials, he has an entire section about the numerous tricks required to get SwiftData relationships to work correctly. Does anyone know if SwiftData also requires tricks to get the UndoManager to work correctly?

If use a SortDescriptor for a model and sort by some attribute from a relationship, in DEBUG mode it all works fine and sorts. However, in release mode, it is an instant crash. SortDescriptor(.name, order: .reverse) ---- works SortDescriptor(.assignedUser?.name, order: .reverse) ---- works in debug but crash in release. What is the issue here, is it that SwiftData just incompetent to do this?

Hi, I am creating (or trying to) my first app using SwiftData - and I have questions :-) The main question I can't get my head wrapped around is the following: Let's say I have the sample below... @Model class Person { @Relationship(inverse:Hat.owner) var hat:Hat } @Model class Hat { var owner:Person? } It looks like I am creating a strong reference cycle between the person and the hat objects? And in fact I am seeing these kinds of reference cycles when I look at the memory debugger. Many code samples I have seen so far use this type of relationship declaration... And I am wondering: Am I missing something? Admittedly I don't find many discussions about memory leaks caused by SwiftData despite the syntax being used in many examples? So what is the situation? Did Apple just miss to explain that the inverse: declaration causes memory leaks or is there some kind of magic that I should understand?

Recently I updated my device OS to the iOS16 version and observed one discrepancy in the native PHPhotoPicker Component in my application. In the Previous version (i.e iOS 15.3), PHPhotoPicker inherits the application's navigation bar color (screenshot attached for reference) However, In the iOS 16 version, PHPhotoPicker's navigation bar color does not change according to the application theme, And PHPhotoPicker displays with its default UI (screenshot attached for it)

When open a CoreData relationship in the Data Model inspector, it shows an option to set the relationship as transient. Apple Core Data Programming Guide havent explained how transient relationship works. Can you please explain, how transient relationship works?

Hi,I'm new in Core data.What I want to achive is have to entities - Documents and Sales.Sales should have: price, productname, qtyDocuments should have: date, documentkind, number etc.What I want is create a relationship between them, because every document will have one or more sales, these are going to be the product items.I know how to achive this when I bind one to one, but when Documents should have more than one Sales....?Is this the right aproach?

Hi, I encountered the issue, that unless an inverse relationship is modelled, the relationship is not persisted. This can be reproduced with the sample code below: Press the Add Person button twice Then press the Add group button You now can see that the group has to member, but once you restart the app the members a gone. Once an inverse relationship is added (see commented code) the relationships are persisted. Any idea if this is intended behaviour? import SwiftData import SwiftUI // MARK: - Person - @Model class Person { var name: String // uncomment to make it work @Relationship(.nullify) var group: Group? init(name: String) { self.name = name } } // MARK: - Group - @Model class Group { var name: String // uncomment to make it work @Relationship(.nullify, inverse: Person.group) public var members: [Person] @Relationship(.nullify) public var members: [Person] // comment to make it work init(name: String) { self.name = name } } // MARK

I have a site with forms that uses jQuery UI ThemeRoller (http://jqueryui.com/themeroller/) for theming, and on Safari Preview and iOS 10, the labels have suddenly turned white.The work on all other browsers (as they have for years).When I inspect, it appears that the body color is being overridden by the ui-composition-content class, when previously it was not.My workaround is to add a specific color tag for the labels, to reset them to body (which is what they should be):label { color: #000000; }Any ideas on why the new Safari is no longer rendering as expected ?

I have an ShoppingItem Entity(attributes: name, id, unit, qty, description) and another entity ShoppingList(attributes: listDate, listName) and a relationship property : items which is many-to-many relationship. The use case is : _The items that are selected by the user have to be updated to the list on the particular date. let myList = GroceryList(context: CoreDataManager.shared.viewContext) myList.name = One more List myList.madeOn = Date() 1. myList.mutableSetValue(forKey: groceryItems).add(selectedGroceryItems) CoreDataManager.shared.save() selectedGroceryItems is of type struct ItemEntityViewModel { let groceryItem: GroceryItem var itemEntityid: NSManagedObjectID { return groceryItem.objectID } var id: UUID { return groceryItem.id ?? UUID() } var name: String { return groceryItem.name ?? } var category: String { return groceryItem.category ?? Not available } var unit: String? { return groceryItem.unit ?? } var qty: Double? { return Double(groceryItem.qty) } } line 1 throws exception a