Did you check on Xcode 13 RC ? Do you call func trimmingCharacters(in set: CharacterSet) -> String yourself or is it a system call ? Are you using PrivateFrameworks ?

What is it you cannot make work ? Open a new thread and post the complete code of your class with a detailed explanation of what doesn't work. For sure someone will help you.

What is changing, if your doc were already in the cloud ? Nothing new, no new risk. If you are scared, disable iCloud options to keep data on your phone only…

They do not look at pictures. It computes a "compressed signature" from the image (which by no way can be seen or even decoded to get the original image in anyway). And compares to the signatures of other images from databases to find matches. All they can say is: you have a photo which signature matches what is in the database. Then of course they can see this photo in the database. But no photo that is not in the database can be visualised.

14.8 security was a rush release. I would not assume it to be available on 15 beta. Anyway, if you're concerned about your data, follow Reck41 advice.

You've probably hit a system limit. But why do you need to dispatch ? Aren't you already in the main thread ?

Yes, it is possible. See what I posted before (with the screenshot).

Yes, view based is much simpler !

The detailed explanation you got in         https://stackoverflow.com/questions/69160053/why-do-animations-not-work-when-deselecting-a-uitableviewcell-in-a-uitableview-a     seems relevant: it is a question of how update events are queued in the system. And dispatch changes the way it is handled.

Yes, it is view based. Could you post the complete code of your test, so that we can reproduce ?

TableView may work even with delegate not defined. Did you set the delegate ? In addition, please show the code of IBAction. Sender must be        (_ sender: NSTextField)

TapGesture will activate when you tap anywhere in the picker, on a row which may be different from selection, isn't it ? And tapping will not change the selection. That could be misleading. Or pickerTapped must first identify which row was tapped, which is not so easy. Or limit the tap to the center of the picker which is where the selection is.

"MacCatalyst but I am aware that it's not always the most easy"     you're right, but it was designed for this exact goal. It's complex because bridging the 2 OS is not that easy. Maybe, instead of trying to adapt your code you should redesign your app with MacCatalyst. Good luck.

OK, you now use the same context.

Did you ask the question on the Swift Forum ?