I'm seeing some weird behaviour with the Xcode 13 Betas. My project builds with no errors. Then indexing kicks in (or at least what I think is indexing) and I'm hit with a heap of "Cannot find type 'x' in scope" errors. This is in my Swift code for bridged Objective C types. This behaviour is new in the Xcode 13. It doesn't happen in Xcode 12. My usual goto for this type of Xcode weirdness is cleaning the build folder and removing any derived data. However this offers only temporary respite. Once a successful build is complete and indexing occurs I'm again hit with hundreds of these seemingly phantom scope errors. Xcode 13 Release Notes do mention the following. Improved reliability and addressed instances where the build succeeded, but the editor showed unexpected live issues. Radar number supplied is 71098549. No idea if this is related to what I'm seeing. Any ideas?