Filter Xcode build output to remove noisy warnings #1468
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When building and Xcode project (macOS or iOS) on Xcode 14, and you have a passcode locked device (such as a phone or iPad) connected to your laptop, Xcode generates dozens of warnings about that device, even though you're not targeting that device.
Xcode 15 adds a new spicy contribution to the mix - a DVTAssertions warning that "createItemModels creation requirements should not create capability item model for a capability item model that already exists.". Whatever that means.
This PR adds an output filter so these warnings aren't surfaced to the end user. The filter is disabled in verbose mode.
Fixes #377.
PR Checklist: