I REALLY want to disable these unwanted and distracting animations in the Navigation bar with the title text and the back button when navigating to a new view and after tapping the back button. This "sudden flying static text" is unwanted, startling and distracting to the viewer. It serves NO USEFUL PURPOSE AT ALL in creating a helpful user interface for the user. Why Apple UI designers think this is a good thing clearly shows that Apple has lost the plot when it comes to solid UI and UX design. Sudden unexpected motion of UI elements that have no purpose flying across the screen are startling and draw the user's attention away from the task they are trying to accomplish. The flying and resizing title text and back button when coupled with a removal of a border between the title bar and the control content below it remove clear delineation of separation between the Navigation region and the content below it. When you REMOVE CLEAR VISUAL INDICATORS from content, you don't make the UI more understandable to users, you muddy the waters and make it more vague to them. A good UI has VISUAL STANDARDS that TELEGRAPH THE FUNCTIONALITY OF THE ELEMENTS TO THE USERS so that they do not have be guessing if they can or should be interacting with elements. User interface elements ONLY should start animating when the effect HELPS THE USER UNDERSTAND THE PURPOSE OF THE UI ELEMENT and therefore HELPS THE USER FOCUS ON THE TASK THEY ARE TRYING TO ACCOMPLISH AND COMPLETE IT. Gratuitous animation - and especially motion - for no purpose, pulls the eye to the motion. In doing that, pulls the user's attention and concentration away from the task they are trying to complete. Therefore sudden startling animation like that in the title bar is counter to useful when this happens every time a screen changes. There's simply NO useful purpose to it. We want to focus on creating useful, predictable and informative user interfaces for our users, not interfaces with trendy techniques simply because everyone else is using them. Techniques like sudden motion are used by Casinos to startle their customers and take over their attention. This is the ANTITHESIS to the principles that Apple's foundation UI elements should contain. Especially considering that Apple gives them to their developers for us to make (hopefully) useful user interfaces for our clients and users. Apple needs to STOP adding such purposeless (and counterproductive) trends such at these to their UI elements. And in the meantime we need standardized methods to TURN THESE COUNTERPRODUCTIVE UNWANTED DISTRACTING ANIMATIONS OFF. And hopefully, never ever see them again. People who are designing foundation class user interface elements should know better. Apparently, they don't and we are the ones suffering their poor decisions. How these made it out the door means that no one with any sense is watching the shop and the amateurs are at the wheel in the UI/UX department.

I NEVER want to see these unwanted animations of the title bar text flying off the screen. Why isn't there an NSDefault option to make sure that the item's unwanted and unasked for extraneous distracting new animations are disabled? And disabled through a standard mechanism such as Defaults. I want to make sure that the animation in the nav bar is disabled and always so. Seeing items randomly flying off of the screen is a visual distraction that adds unhelpful noise to the UI. It distracts the user. It doesn't help them accomplish their task. This push in the UI team to animate EVERYTHING - whether it serves a useful purpose or not - is taking Apple far away from setting the standard in user interface experiences that HELP the user. There is NO useful purpose that helps the user accomplish their task by having a STATIC user interface element fly off the screen (or fly on the screen for that matter). It's a distraction - not a helpful aid. Unwanted and unexpected motion is a VISUAL DISTRACTION to users. ESPECIALLY among UI elements that are static… until they suddenly start flying across the screen. It serves no purpose at all to help the user accomplish their task and sudden motion actively pulls the user's attention AWAY from what they are trying to focus on. Sudden unexpected motion is bad, startling, distracting and should be actively avoided in productive user interfaces. For the love of useful interfaces, let us developers - THROUGH A STANDARD MECHANISM - turn OFF this insipid "flying static UI text". No one wants it. No asked for it. It serves no constructive purpose to the user at all. Now, as developers, how the hell do we turn this unwanted animation OFF in the Navigation title bar?

This is a misleading error. Upon reading it, our first reaction is to search for those headers or to define where they are. That's the wrong approach. You need to set several values version in the Architectures section of Build Settings if you can open the project in Xcode. This is what allowed me to compile Apple's Bonjour DNS-SD project in Xcode. Base SDK, Architectures. Those were all I needed to update to get the build to function. Base SDK: macosx Architectures: $(ARCHS_STANDARD) Valid Architectures: i386 x86_64

Running in Xcode 13.4 and iOS 13.0 is required if you want to run in the Simulator. Not sure which, but later versions will not trigger 2FA. Tested using Sim 15.5. Even when using 13.0, the 2FA is a clunky process. The second time it worked.

FYI, since I'm running into this too, these notes may be helpful https://support.apple.com/en-us/HT211025 TLS server certificates issued on or after September 1, 2020 00:00 GMT/UTC must not have a validity period greater than 398 days. Connections to TLS servers violating these new requirements will fail.  Best of luck to anyone who is running into these issues too.

Well, it appears that there is another AWWDCRA cert that is required. One that expires on Feb 7, 2023 and one that expires on Feb 19, 2030. Copy and paste the following link to see. i.imgur.com/XiicKhc.png Installing the cert below made my freshly created certs become trusted. https://developer.apple.com/support/expiration/

The same thing just happened to me and freshly made dev and distro certs are all not trusted. Even reinstalled the Apple WWDRCA cert and all of my dev and distro certs are "not trusted" with "no root certificate found". My dec Common Name: Apple Worldwide Developer Relations Certification Authority Organizational Name: G3 Organization: Apple Inc. Does that mean that the root cert needs to be in the keychain? Because it is and it's valid. There are no certs that are expired or certs with custom trust settings in my keychain.

I'm afraid that I don't have an answer.

Don't use it. It's monumentally screwed up. I've seen massive problems with > 4 devices. It's a massive waste of time.

As indicated by others, set the Codegen for your CoreData entities in your CoreData xcdatamodel file to Manual/None, If you do not, you may get these build errors. <unknown>:0: error: filename "SomeAwesomeEntity+CoreDataClass.swift" used twice: <unknown>:0: error: filename "SomeAwesomeEntity+CoreDataProperties.swift" used twice: