Sorry I don't have an answer, I think it's a great question. I played with your example code and I'm just as puzzled. I hope someone else can answer.

I just pasted your code into Xcode, ran it, and started clicking around. It seems a bit bogged down, because it can take over a second to change the VeryComplexView when I click on the different numbers in the left nav. But, the memory use is staying around 100-150MB. I'm running macOS 11.2.3, so maybe you could try upgrading to that?

Apparently, I can't edit questions here like you can on StackOverflow. This is not caused by Xcode 12.5 exactly, it happened because I followed the suggestion to enable the "Hardened Runtime". So my question is really: can you unit test when the "Enable Hardened Runtime" build setting is "YES"?

Here's a simulator screenshot (iPhone SE). I've marked about where the border is, for the touch events. In my real app, with wider text, it's even further to the right, so that touching the first column of text actually spins the second picker.

Due to some problem with git, I'd lost the Info.plist definitions of the "Document Types" and "Exported Type Identifiers". Once I added those back, this error disappeared.

But the passed-in closure is meant to run on the main actor, and it is, it's just that the complier doesn't seem to understand that.

I wonder if there are any updates for this for swift-tools-version:5.5 (October 2021). I'd like to put metal shaders in a Swift package.

My app starts fine, but if I stop on a breakpoint, the first load of the left panel (variables) takes a long time - about 10 seconds on a new MBPro. Once it's loaded things seem okay. Well I have other issues, like variables that I can't see or print, but that's not a speed issue.

Did you ever find an answer? I have the same question. I have a popover that changes width and height and I'd like them to animate.

I think so, but I'm not sure exactly what you're trying to do. Here, I copied the code from the documentation for EditButton, and added some ability to select by tapping the text. (Probably you want to render the selection in a different way, not just green text, but I did that for simplicity.) struct ContentView: View {     @State private var fruits = [         "Apple",         "Banana",         "Papaya",         "Mango"     ]     @State private var selected = Set<String>()     var body: some View {         NavigationView{             List {                 ForEach(fruits, id: \.self) { fruit in                     Text(fruit)                         .foregroundColor( selected.contains(fruit) ? Color.green : nil )                         .onTapGesture { toggleSelected(fruit) }                 }                 .onDelete { self.deleteFruit(at :$0) }                 .onMove { self.moveFruit(from: $0, to: $1) }             }             .navigationTitle("Fruits")             .toolbar { EditButton() }         }     }     func toggleSelected(_ fruit: String) {         if selected.contains(fruit) { selected.remove(fruit) }         else { selected.insert(fruit) }     }     func deleteFruit(at: IndexSet) { fruits.remove(atOffsets: at) }     func moveFruit(from: IndexSet, to: Int) { fruits.move(fromOffsets: from, toOffset: to) } }

I have the opposite situation - I see a review in the "Connect" app on my iPad, but not in the App Store. I'm don't know why.

When I do "New" > "Playground..." in Xcode 13, I have a choice between iOS and macOS. I'm not sure how to change it after the fact, but maybe you need to make a new Playground and choose macOS?

I submitted feedback with example project: FB9892547.

Yeah, I need this too. I need to decide whether the ScrollView or the contained view should handle a drag event. It was possible in UIKit with the touchesShouldCancel method.

My problem was caused by something dumb that I left out of my question, because I was trying to simplify it to post here. My UIScrollView was actually inside a SwiftUI view hierarchy, using UIViewRepresentable. Higher in that view hierarchy, there was a SwiftUI List, which also has scrolling. I had forgotten about that List because I was using it for it's layout appearance, grouping items into sections, but not for its scrolling. Once I got rid of that List, everything worked as expected.