I'm building an app in Apple Virtualization but I can no longer generate images after updating to macOS Sequoia. It's a simple function that will create thumbnails in either HEIF or JPEG, but neither work now. I get these warnings every time: CGImageProviderGetContentHeadroom: Bad headroom value 0.000000 for SDR, returning 1.0 NSBundle file:///System/Library/PrivateFrameworks/MetalTools.framework/ principal class is nil because all fallbacks have failed IOServiceMatchingfailed for: AppleM2ScalerParavirtDriver <<<< VTParavirtualization >>>> VTParavirtualizationReplyClerkWaitForReply signalled err=-19092 (kVTParavirtualizationTimeoutErr) (timeout waiting for pending reply) at VTParavirtualization. c: 3804 writeImageAtIndex:1077: *** CMPhotoCompressionSessionAddImage: err = unknown error [-19092] (codec: 'hvc1') The operation couldn't be completed. (CINonLocalizedDescriptionKey error 3.) Will this be resolved in Xcode 16 or macOS Sequoia?

Some of my models have many-to-many relationships. For example, when I add a file to a directory, a model is created from that in addition to any relationships it may contain. I’ve incorporated SwiftData History into my front end and backend projects and it’s able to show me what has been inserted, updated, and even deleted after the file is removed from the directory. Which only returns the identifiers I’ve set to become tombstone values. All working as expected and my client can now sync with the server. I can add and remove the same file repeatedly and I’m able to retrieve all the transactions. However if I add another file and then fetch transactions, it crashes at .fetchHistory(_:). The errors say they cannot find the property of a model it has a many-to-many relationship with. I omitted appending any relationships, but the errors start pointing to properties belonging to the model itself. I’ve only managed to get this functioning by setting the @Relationship macro to a single model. Previously, I had this macro with its delete rule and inverse on other types. But doing so would crash the same way immediately and wouldn’t let me fetch history at all. Since it crashes at fetching the history, I’m unable to proceed and the options appear to be limited for what I can do before I fetch them. Does SwiftData History not work with many-to-many relationships or is this a bug?