“SwiftData inheritance relationship”

Our team is working on an Authorization Plugin that includes a UI as well, thus it works by creating a subclass of SFAuthorizationPluginView. Some of our users have reported that controls remain on the screen for a period of time even after a successful login. As shown in the attached screenshot, the native, inherited controls are the ones that remain on the screen, our plugin's controls disappear immediately. What I did to investigate this issue further, is that I checked the very basic Apple-provided example (modified by the community to bypass its issues): https://github.com/antoinebell/NameAndPassword Our users reported the exact same behavior once more. Inherited native controls (the back, forward buttons, the bottom 3 buttons ) all remained on the screen for a significant amount of time, even after the PluginDestroy and MechanismDestroy functions have been called. I would like to get confirmation on whether this is indeed an Apple-side issue or if anyone else have met this problem. I a

The Rust programming language is currently trying to replace its synchronization primitives with more efficient, statically initializable ones (see tracking issue). This turned out to be difficult on macOS, as it does neither have these primitives by default like Windows (SRWLock is really efficient and works with condition variables) or have a ready-to-use futex operation like Linux, FreeBSD, etc. A suitable alternative would be to use a parking lot like WebKit did, but that would make it impossible to implement priority-inheriting mutexes, which are somewhat important on an interactive system like macOS with its QoS feature. It turns out however, that macOS actually has a futex-like syscall called ulock_wait/ulock_wake. This syscall, while exposed through libSystem, is unfortunately private and its use has resulted in Apps being rejected from the App Store, which is unacceptable for a standard library like std. Since it is implemented since macOS 10.12, retroactively stabilizing the API would make

I'm totally stumped. I have a new Swift project that embeds my own Swift framework, which has a bunch of base classes for view controllers, etc.I can build and run my local builds just fine. But when I Archive and upload to TestFlight, any build that gets installed fails to run as expected.A few overridden methods for key pieces of my app suddenly fail to get called, as if the normal inheritance chain is broken.For example, in a BaseViewController class, a viewDidLoad() method calls a localize() method.Then I subclass that view controller and override its viewDidLoad() and localize() methods, and make them call super before doing some custom work.In local builds, the subclass's viewDidLoad() and localize() methods get called as expected.But in archived builds, the subclass's localize() method never gets called.Even if I call localize() or self.localize() explicitly from the subclass, only the base class's version of localize() gets called.This is rather embarrassing because when I deploy a build to T

I see that in Xcode 8.3 in the Custom Class Inspector, there is a new option `Inherit from Target` and I'm not sure what does it do? I haven't seen any mention of this in the release note niether?Here's a screenshot

Using the 'Create SwiftData Code...' action in Xcode results in Model that have bi-directional relationships between many of my entities (which is correct - my Core Data model includes this). All of these Relationships are marked as invalid, however, with the following error: Circular reference resolving attached macro 'Relationship' Most ORM's, in my experience, have a way to mark one end of a bidirectional relationship as an 'owner'. Is there something similar available in SwiftData, or is this scenario handled in a different way? Or am I going to need to remove all of my bidirectional relationships?

So, I've had this problem with swift since day 01. I've mentioned it a few times in these forums,a nd I haven't been able to get a satisfactory answer.there's a lot of details, but it resolves to this:a subclass, that overrides a superclass's method, never gets that overridden method called. Instead... The base class's method gets called.earlier in the day, the subclass's method would be called just after launch of the debug, but following something I haven't tied down yet, the base class's method gets called.So I have a base class : BKControlPropsit's got this method :open func mouseDraggedBehavior(event : NSEvent, viewPt : CGPoint){}now there is a successive list of subclasses:BKControlProps BKScrollerProps BKGroupProps BKListPropsScrollerProps overrides that mouseDraggedBehavior method:open override func mouseDraggedBehavior(event : NSEvent, viewPt : CGPoint){ let minOffset : CGFloat = 0.0025 switch scrollValue { case .none: break case .horiz: deltaAggregate += 2 / self.xWorkingLength * event.deltaX if abs

I’m having an issue when two of my SwiftData models have a one-to-many relationship and I have them synced via CloudKit. To be clear, I’ve met all of the requirements to make it iCloud friendly and sync to work. I followed this https://www.hackingwithswift.com/quick-start/swiftdata/how-to-sync-swiftdata-with-icloud, and can confirm I’ve done it correctly because initially I was seeing this crash on startup when I had not: Thread 1: Fatal error: Could not create ModelContainer: SwiftDataError(_error: SwiftData.SwiftDataError._Error.loadIssueModelContainer) This is to say, the problem may be iCloud related but it’s not due to a wrong model setup. Speaking of which, these are models: @Model class Film { var name: String = var releaseYear: Int = 0 var director: Director? = nil init(name: String, releaseYear: Int, director: Director) { self.name = name self.releaseYear = releaseYear self.director = director } } @Model class Director { var name: String = @Relationship(

Hi, guys. if I declared Class B inherit Class A that adopt ObservableObject, Class B has a @Published property, SwiftUI View not updating when the viewModel’s value changes? Is that a bug or something else?