ReadMeFeed / Community knowledge

#swift-package-manager

Real questions. Useful conversations. Find the people who know your stack.

Article0 replies3,839 followingPosted 19 May 2026, 10:53 UTC74.6K views1,606 votes

Add a Local Swift Package to an Xcode App Target Without a Git Remote

Learn how to link a local Swift package into an Xcode app target using filesystem references, validate the build, and recover from common path and resolution errors.

Community & Careers · Guide

swift-package-manager

xcode local-package

Tasadduq Burneyowner

Started19 May 2026, 10:53 UTC

Level 38Owner34,775 rep points

Community & Careers

Question1 answer1 comment4,881 followingPosted 25 Dec 2025, 05:45 UTC79.6K views1,679 votes

owner commented

"Dependencies could not be resolved" after swift package update: safe rollback of Package.resolved and build cache

After running swift package update on a Swift 5.9 project, dependency resolution fails with an unsatisfiable-constraints error from the resolver, and I want to return to the previously working dependency graph without guessing at versions. My understanding is that Package.resolved records the exact pinned versions, so restoring the committed copy of that fil

Community & Careers · Editorial question

dependency-resolution swift-package-manager

swift

Community & Careers

Question1 answer3,630 followingPosted 18 Sept 2025, 06:15 UTC53.3K views1,861 votes

owner answered

Xcode and Swift Package Manager dependency resolution and DerivedData invalidation

Integration between Xcode and Swift Package Manager governs how dependencies are resolved and reused across builds. Xcode uses Package.swift manifests and the persisted Package.resolved file to reproduce builds, with compiled artifacts cached in DerivedData until the manifest or resolved file changes. The goal is reproducible dependency resolution for low-fr

Community & Careers · Editorial question

dependency-resolution swift-package-manager

xcode

Community & Careers

Question1 answer1,605 followingPosted 10 Jan 2025, 08:18 UTC106.8K views2,754 votes

helper answered

Swift Package Manager cache invalidation after Package.swift dependency version change

Swift Package Manager caches resolved dependencies and built artifacts locally to speed up repeated builds. The documented behavior for when those caches are invalidated after a manual edit to Package.swift is not fully specified. The goal is to clarify the configuration transition that determines whether derived artifacts are reused or rebuilt after a depen

Community & Careers · Editorial question

build-artifacts cache-invalidation swift-package-manager

Community & Careers

Question1 answer3,069 followingPosted 14 Jan 2024, 16:32 UTC38.4K views2,848 votes

owner answered

Xcode ↔ Swift Package Manager: Conflict Resolution for Shared Dependencies

Xcode ↔ Swift Package Manager: Conflict Resolution for Shared Dependencies In a workspace that imports two Swift packages, each declaring a dependency on a different major version of the same third‑party library, Xcode’s resolver consistently selects the highest available version. This behavior is not documented in the public Xcode or Swift Package Manager g

Community & Careers · Editorial question

dependency-resolution swift-package-manager

xcode

Community & Careers

Question1 answer1,559 followingPosted 19 May 2022, 04:08 UTC81.1K views3,832 votes

helper answered

Swift Package Manager binary targets vs manual XCFramework integration

Integrating Pre-compiled Binaries Xcode allows the inclusion of proprietary libraries through two primary methods: integrating binary targets via the Swift Package Manager (SPM) or manually embedding XCFrameworks into the project structure. While SPM binary targets simplify dependency resolution and versioning through the Package.swift manifest, the underlyi

Community & Careers · Editorial question

swift-package-manager

xcode dependency-management