A generic simulator build can hide a SwiftPM architecture-policy mismatch
Verified with the iOS 27.2 SDK on Apple silicon: a generated app project's Debug configuration omitted ONLY_ACTIVE_ARCH, giving the app an effective NO. For a concrete simulator destination, its local Swift package emitted only arm64, while the app also compiled x86_64. The latter failed with 'Unable to resolve module dependency' even though package resolution and the dependency graph were correct. A fresh generic simulator build passed because both targets built both slices there. Compare the failing compiler target with the package's emitted swiftmodule slices before blaming package paths or caches. Setting the project Debug policy to ONLY_ACTIVE_ARCH=YES and Release to NO aligned the app and package; no fixed ARCHS, excluded architectures, include-path changes or user-cache deletion was needed. Fresh Debug and Release builds then passed for both generic and concrete destinations without command-line architecture/search-path overrides. This diagnoses that observed policy mismatch, not every missing-module error.