Same here. Using Xcode 14.2 on an Intel MacBook Pro on macOS Monterey 12.7.6 I create a new iOS app project and run on Simulator. Then I embed the single view controller on storyboard in a Navigation Controller and run again and get the same error as others report. Then I copy the project to another Mac (Intel MacBook Air on macOS Ventura 13.6.7 and run on Xcode 14.3 and it works flawlessly. (same project, different Xcode version). For what it's worth, that's my experience. Edit: This is an Objective-C project, not Swift; all my work I done in Objective-C.

Thanks, drewster! That fixes it, both ways (in my code and/or patching it in Mantle's code). Much appreciated!

I'm seeing the exact same message in Xcode's console pane while parsing JSON into custom data objects using the open source library Mantle (version 2.1.6 using CocoaPods). This is an iOS MapKit app showing whale-sighting annotations. Each sighting JSON has latitude, longitude, and other numeric and text values, all represented as strings. This started happening with Xcode 15; the same code showed no such errors in Xcode 13 and Xcode 14.

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.