Solved. Type the word you want to filter out and press Return. A popup menu triangle appears before the word that, when opened, offers 4 choices: Contains, Does Not Contain, Begins With, Ends With. Still wish new Xcode features had some standard place to find descriptions.

I have this same problem. Where is this feature (new in Xcode 14) documented?

This is also happening for me, both projects downloaded from GitHub using Xcode's "Clone..." menu item as well as directly from the command line in Terminal.

I had this same error on macOS Monterey 12.6.2 with Xcode 13.4, Xcode 14.0.1 and Xcode 14.2 installed. Changing the default Xcode (Xcode / Preferences / Locations - "Command Line Tools:) from the latest (14.2) to 13.4 and trying again was successful. With 14.2 as the default: sudo gem install cocoapods -v 1.11.2 => #fail sudo gem install cocoapods => #fail (different error message) After changing to 13.4 as the default: sudo gem install cocoapods -v 1.11.2 => success, and pod --version => 1.11.2

The feature is still available in the 'Commit' window when you're saving your entire project back into source control (menu 'Source Control', menu item 'Commit...'). The arrangement of controls along the bottom of the window is also the same as before. It seems this new, changed interface only appears in the side-by-side 'Code Review' window. Not as useful if you just want to compare and perhaps revert changes in a single file. I second the motion that Apple make the old behavior available as an option to this new "improved" design.

The link to Xcode 13 Release Notes given above is to the beta version and no longer works. The current link is: https://developer.apple.com/documentation/xcode-release-notes/xcode-13-release-notes

Thanks, it was an issue with Finder reporting sizes. Using the 'du' command in Terminal gives me consistent numbers (with slight differences): % du -s Xcode_12* MacBook Pro  31958304 Xcode\_12.2.0.app 32572544 Xcode\_12.3.0.app MacBook Air 31821984 Xcode\_12.2.0.app 32289672 Xcode\_12.3.0.app I would have been less gun-shy except I've been having problems with earlier versions of Xcode on both Macs (crashes, freezes, file corruptions, etc.). Now that a day has passed both Macs are giving me more believable Finder sizes. "What a difference a day makes." Thanks again for your help.

This just started happening to me two days ago. It's an old Xcode project (2014!) that uses MapKit, last updated in June 2018. I run it to compare its behavior with the new app I'm working on that replaces it. I was running it off and on for weeks without trouble in iOS 13.x Simulator, using GPX files to simulate user location (including moving locations). I have multiple copies of Xcode installed (every major point release from 11.7 back to 11.2) as well as two versions of Xcode 12 (beta 6 replacing beta 4). None of this seemed to bother it. Then the problem started happening with no precipitating event I can identify, and now I find any copy of the project (even a fresh clone from source control) has the exact same behavior, so whatever this is, it's external to the Xcode project itself. And it happens in every Xcode version I've tried, all the way back to 11.2. (But not, at least yet, on devices, just Simulator.) Specs: macOS Catalina 10.15.4 (19E266) on a MacBook Pro (13-inch, 2019, Four Thunderbolt 3 ports); 2.8 GHz 4-core i7; 16 GB of RAM, 1TB of SSD, Xcode 11.6 (and other versions). Fortunately I have an older Mac with older macOS (Mojave) and Xcode (11.3.1) that doesn't (yet) show this bug, so I can rely on that for now. But I hope this does get fixed so I can return to comparing old and new code on the same machine.

Thank you. This is just the sort of information I was hoping I could find on my own by searching. Now that the link has been pointed out to me, it shows up at the top of my search ("Xcode 12 split-view controller") where it was not showing at all before ("Xcode 12 master detail missing template").

Found the answer. Operator error. (Of course.) Xcode's exception-breakpoints editor changed in version 11. It added a 'Condition' file that was not present in Xcode 10. The new field is highlighted on open. The text cursor is blinking. It commands your attention. (A screenshot would help here.) Entering 'po $arg1' here looks so similar to what I recall from past Xcodes that I failed to recognize this is not where it belongs. And the misplaced command behaves as I've described. Unrecognized when an exception is throw, recognized when I move the stack selection to the exception code itself. So the fix is, as you described, clicking the 'Add Action' button and entering 'po $arg1' as a new Debugger Command. Thanks for your help, Quinn.

Four years later (2020) this is a different problem with a different fix (at least in my experience). I work almost entirely in Objective-C, writing apps for iOS. For years I've had the command po $arg1 saved as a user breakpoint so that when Xcode threw an exception it would print the exception message to its console. At some point after I began using Xcode 11, this started failing with the message Stopped due to an error evaluating condition of breakpoint 1.1: "po $arg1" Couldn't parse conditional expression: error: use of undeclared identifier 'po' After a fresh dive into the Googleverse today, I stumbled upon an answer. Xcode 11's debugger stops with its stack-view selection on the line of my code that threw the exception [self.termsVC.presentingVC presentViewController:nav animated:YES completion:nil]; Here 'po $arg1' fails as I've described (for me). If I select the top line in the stack view (in the exception code, where the debugger is actually stopped)objc_exception_throw and repeat the command, it works as before (lldb) po $arg1 The specified modal presentation style doesn't have a corresponding presentation controller. Yet Xcode's stack view was always selecting my code, not the exception code. That hasn't changed. What changed was Xcode 11's ability to evaluate "po $arg1" from that line. Details: MacBook Pro (13-inch 2019), 16GB RAM, macOS Mojave 10.14.6, Xcode 11.3.1. Both iOS Simulator and devices. Happens both in new projects created with Xcode 11 and older projects created with Xcode 9 and earlier. Was happening in earlier versions of Xcode 11 and in earlier versions of Mojave. Not yet tested in Catalina.