I've recently had an issue with SPM not being able to resolve the dependency graph, complaining that a framework (of my own design) used in my Xcode iOS app project contains an incompatible dependency.
**Showing All Messages** : the package ...[...] @ 0.7.0 contains incompatible dependencies: ohhttpstubs[https://github.com/AliSoftware/OHHTTPStubs.git] @ feature/spm-support
Besides the very cryptic message (ohhttpstubs doesn't have dependencies, so it can't clash with anything I already had in the app, while already working in the framework by itself), I couldn't find any other info. Also, it seemed strange that both my app and my framework depended on Alamofire and SPM managed to resolve that without hiccups.
As a Hail Mary sort of thing, I tried removing the
Package.resolved file from my framework... and all problems went away. Still, this feels as a bug.
Bonus question: would it be possible to somehow exclude the dependencies of test targets defined by other dependencies from the final resolved tree? At first thought it wouldn't make much sense to have those in an app since you won't use then in your app build.
Package.resolved worked when using the framework as a local package, but when switching back to the hosted repo, it still fails with the same error. Very strange.