mac-capture: Fix incorrect enum comparison #12035
Open
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.
Description
macOS Audio Capture was using the incorrect capture type enum member to check the capture method on initialization. Because the default was zero, and because the incorrect enum would typically be zero-initialized anyway, this went unnoticed. The correct member enum is being used everywhere else in macOS Audio Capture.
Motivation and Context
AppleClang in Xcode 16.3 flags this as a non-matching enum type in the comparison, breaking the build. For some reason earlier AppleClang in earlier SDKs did not flag this as a warning.
Fixes #12034.
How Has This Been Tested?
Verified the build now works locally with Xcode 16.3 and that macOS Audio Capture still works as intended.
Types of changes
Checklist: