SwiftUI List performance

Herewith an update from us on the Local Network Privacy issues that we and our users are experiencing. Over the past period we have done many tests with various combinations of machines and OS'es. Long story short Local Network Security settings seem to behave different between applications that have been either Downloaded, AirDropped or tranferred over a USB Drive. Airdropping the application to the machine gives the expected behavior. Installing the application by downloading it or by installing it over a USB drive gives broken behavior for Local Network Access. Deleting the application and then Airdropping the Application can fix the behavior. Having multiple versions of the same application on the machine breaks Local Network Access. Airdropping gives an additional warning on first launch, so could this be Gatekeeper related? Reproduction These are the steps where you would be able to recreate the issue, we've done this multiple times on multiple different machines on multiple OS versions. The latest OS t

Hi Kevin, Thank you for the suggestion. We have performed the over-retaining experiment by adding an extra retain() to the OSAction at the start of the UserProcessBundledParallelTasks loop. Unfortunately, the result remains the same: the DEXT still triggers a Corpse crash immediately upon calling the completion signal in the asynchronous path. As the legacy mode (UserProcessParallelTask) remains 100% stable under our newly serialized queue configuration, we have decided to revert to the legacy path for now to continue our product development while we wait for investigation on the bug report (FB21636775). Any further insights into why the asynchronous completion fails specifically in Bundled mode would be greatly appreciated. Best Regards, Charles

Hi Albert, thank you for replying. Here is my Richnote class: import SwiftUI import SwiftData @Model final class Richnote { @Attribute(.externalStorage) var content : AttributedString var createdAt: Date = Date() init(content: AttributedString) { self.content = content } }

Thanks a lot for responding. Thanks for the post, it’s hard not seeing the code and how you're setting constrains in code. Would you be so kind to provide your code where you setting the constraints so developers here can see it? [..] it is generally not a good idea (and will lead to crashes) to directly modify the frame or bounds of a view that is managed by Auto Layout in my opinion. Initially I did not involve Autolayout at all explicitly. What I had was a small container view controller with something like this (no explicit constraints): @implementation SmallInfoWrapperViewController -(void)viewDidLayout { [super viewDidLayout]; NSRect bounds = self.view.bounds; CGFloat lineHeight = 1.0; self.separator.frame = NSMakeRect(0.0,bounds.size.height-lineHeight,bounds.size.width,lineHeight); BOOL separatorVisible = !self.separator.isHidden; CGFloat wrappedViewHeight = bounds.size.height; if (separatorVisible) { wrappedViewHeight -= lineHeight; } self.wrappedView.frame = NSMakeRect(0.0,0.0,bounds.size.width, wrap

Thanks for the post, it’s hard not seeing the code and how you're setting constrains in code. Would you be so kind to provide your code where you setting the constraints so developers here can see it? What do you mean by legal? it is generally not a good idea (and will lead to crashes) to directly modify the frame or bounds of a view that is managed by Auto Layout in my opinion. In my experience any method that directly or indirectly causes setNeedsLayout() or setNeedsDisplay() or changes the frame or bounds of a view that is managed by Auto Layout, may likely trigger the same infinite loop and exception. I think AppKit's layout cycle (especially with Auto Layout) translatesAutoresizingMaskIntoConstraints creates weird fixed width and height constraints leading to Unable to simultaneously satisfy constraints warnings isn’t? When you then add a view add an explicit Auto Layout constraints to a view hierarchy where translatesAutoresizingMaskIntoConstraints is true for some views, you often end up with conflicti

I'm also running into this issue, it's very annoying because I'm trying to learn swiftui to build an app. I submitted a bug report right before commenting & boosting so hopefully this gets fixed sooner rather than later!

@ranjith_keerthi I need way more information about the issue and the link to the AASA file and the app. Can you provide me that publicly or do you want to send me that privately? swcd logs might show if it successfully fetched your apple-app-site-association file, or if there were parsing errors, network issues, or certificate problems. Messages like Domain not associated with app or No app for URL are strong indicators of a setup problem. Double-check that your domain is listed correctly, prefixed with applinks: (e.g., applinks:yourdomain.com). Can you provide me the app and the AASA link and a description of the issue and we will take it from that? Is everything working on a physical device? Albert Pascual
  Worldwide Developer Relations.