Maybe they want us to take a break. Stretch, relax, go for a walk. Breathe some fresh air. Maybe take the rest of the day off.

Be sure to file a feedback request on this specific issue.

Hmmmmm... that would be an interesting project...

Yup. Xcode 13.2 downloaded from the releases page crashes on startup with a message like Application Specific Information: Swift/arm64e-apple-macos.swiftinterface:13494: Fatal error: Duplicate values for key: 'https://github.com/Quick/Nimble' ProductBuildVersion: 13C90 Not sure if this is related...

Thank you. I will try this.

The Xcode 13.2 from the dev portal was working for me last night. Now when I open my workspace with Xcode it crashes on startup with an error like Swift/arm64e-apple-macos.swiftinterface:13494: Fatal error: Duplicate values for key: 'https://github.com/Quick/Nimble' I've filed a FB request for this, number FB9808715.

No, actually, some of us are still having problems with that version of Xcode, like crashing when building or just starting Xcode.

I just downloaded Xcode 13.1 and I still get the same crash when I try to load my workspace: Swift/NativeDictionary.swift:743: Fatal error: Duplicate values for key: 'https://github.com/Quick/Nimble' Maybe this is a Monterey 12.1 issue? This was working last night. Then I updated to 12.1 overnight. Now it's not working. sigh

Nope. Still broken! Is this a macOS 12.1 issue???

FYI I was able to "fix" the problem I was having by doing rm -rf /Users/msa/Library/Developer/Xcode/DerivedData/*

Thank you, Frank! I didn't notice those properties before. I'm accepting your answer as the correct one. Though this opinion has no bearing on the correctness of your answer, I think that deprecating the RAW filter's introspective key-value API in favor of a "static", property-based API is a mistake. I see a place for both kinds of APIs, where each complements the other. If you believe there's still a non-deprecated API that would allow developers to read and write RAW filter input keys at runtime, I would love to hear. I hope the deprecated API remains indefinitely supported in the future, even if Apple discourages its use.

Is there a way to accomplish this running tests in Xcode without using a test plan?