Reverse engineering the log to get the source code is not that easy 😉. You'd better post the code yourself.

As @robnotyou noted, if you type func view…, then it works and even provide template once you have accepted the proposal. But it is important it makes the difference between a mere call to the API and the declaration of API override.

Sorry, I missed your question. Code completion just tells you what is the API (or your own function or var) that could match. It does not intent to give a code template. Note that when you type super.vi… in the override, it is logical it proposes viewDidLoad().

I clarified the point. When I typed appearance.bar… I got a completion proposal but with a warning of deprecation that I ignored. I could then type appearance.barStyle = . and get the constants proposals. But later, that cause a compiler error…

But this seems to work:           self.navigationController?.navigationBar.barStyle = UIBarStyle.blackTranslucent. But as it is deprecated since iOS 13, you should use :           self.navigationController?.navigationBar.barStyle       = UIBarStyle.black           self.navigationController?.navigationBar.isTranslucent       = true. I also found this comprehensive analysis of the changes since iOS 13 :        h t t p s : / / sarunw.com/posts/uinavigationbar-changes-in-ios13/

I'm confused now: the screenshot is a real one, captured in Xcode. But now, I cannot repeat it ! All I can set is the backgroundColor:           let appearance = UINavigationBarAppearance()           appearance.backgroundColor = .green

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.