SwiftUI List performance

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.

same issue on my self-hosted server via fastlane. Build stucked for 4h and no results. Just wrote infinity: [11:15:51]: Waiting for the build to show up in the build list - this may take a few minutes (check your email for processing issues if this continues) [15:38:00]: Waiting for the build to show up in the build list - this may take a few minutes (check your email for processing issues if this continues) But sometimes it can successfully upload new build... Xcode 26.2.

@giantramen I faced the same issue with my app, which also uses Unity. I was able to resolve it and run tests on the simulator by disabling the Thread Performance Checker in the test scheme.

If I use transform-origin: top; instead of transform-origin: bottom; I get better Performance.