Chiming in again with some findings. Reverting to Xcode 26.1 solved the package issue for me I'm using Tahoe 26.3.1 - I have a coworker with same project and Xcode 26.3.1, but using Tahoe 26.1 that does not have the problem. Using Is_kevin's approach using xcodebuild -resolvePackageDependencies, albeit with cleaning the package cache first worked for me on Xcode 26.3.1 too, but is cumbersome
Topic:
Developer Tools & Services
SubTopic:
Xcode
Tags: