Fixed it. Turns out that a few years ago, a User-Defined build setting for CONFIGURATION_TEMP_DIR had been defined in our project. Removing this setting, and falling back to the default value got our project running again with no issues. I'm not sure why this setting had been defined originally, but apparently Xcode 13.3 just doesn't like it anymore. This line also affected another project of ours, that doesn't use storyboards, but does have an Apple Watch app. In that case, the crash was similar, with the error stating that an Interface.plist file could not be found. Apple's (archived) doc on the setting.

Small update: I opened the workspace of a project I had a previously configured workflow running in using Xcode 13.2 beta 2 (13C5081f). My workflows are now visible in the Reports Navigator. Right-clicking one and selecting "View in App Store Connect" will take me to the workflow on App Store Connect. However, if I click away from the page in my browser, the framework no longer shows as a project on App Store Connect. The new beta of Xcode will also allow me to start creating a new workflow for a product, including the ones that fail in Xcode 13.1

Based on the release notes, this looks like it's been fixed in the Xcode 13.2 beta. Fixed an issue where availability checks in iPhone and iPad apps running on a Mac with Apple silicon always returned true, which caused iOS apps running in macOS Big Sur to see iOS 15 APIs as available and crash when trying to use those APIs. These availability checks now return the correct result for apps compiled with Xcode 13.2. (83378814)

I would also be interested in this, as my team also uses Github Enterprise in an enterprise network. FB9462204