I’ve run into this exact issue a handful of times—SPM works flawlessly from the command line, but Xcode just refuses to recognize imported dependencies. More often than not, it’s either a caching glitch or Xcode not properly syncing with SPM’s configuration. Here are the solutions that have consistently worked for me:

1. Regenerate the Xcode Project File #

Sometimes opening Package.swift directly in Xcode leaves behind stale cache. Instead, let SPM build the Xcode project from scratch:

swift package generate-xcodeproj

Open the generated .xcodeproj file instead of the raw Package.swift—this ensures Xcode uses SPM’s exact configuration to set up the project structure, and your dependencies should show up correctly.

2. Clear Xcode Cache and Restart #

Xcode’s derived data cache can cause all sorts of weird issues. Try this:

• Close Xcode completely
• Navigate to Xcode > Preferences > Locations > Derived Data, find the folder path, and delete the entire Derived Data directory
• Reopen your project and wait for Xcode to reindex and reload all dependencies

3. Double-Check Your Package.swift Configuration #

Even though command-line builds work, it’s worth verifying your dependencies are linked to the right target. Make sure your executable target explicitly lists the dependencies it needs:

let package = Package(
    name: "YourExecutableName",
    dependencies: [
        // Your declared dependencies, e.g.:
        // .package(url: "https://github.com/SwiftyJSON/SwiftyJSON.git", from: "5.0.0"),
        // .package(url: "https://github.com/your-repo/ScannerUtils.git", from: "1.0.0"),
    ],
    targets: [
        .executableTarget(
            name: "YourExecutableName",
            dependencies: [
                "SwiftyJSON",
                "ScannerUtils",
                "TelegramBot" // Ensure all required dependencies are listed here
            ]),
    ]
)

If a dependency isn’t in the executableTarget’s dependencies array, Xcode won’t associate it with your target.

4. Force Xcode to Update Package Dependencies #

If you’re working directly with the Package.swift file in Xcode:

• Go to File > Packages > Update to Latest Package Versions from the top menu
• Alternatively, right-click the Packages folder in your project navigator and select Update Package
  This forces Xcode to re-fetch and re-link all dependencies, which often resolves missing module issues.

5. Verify Swift Version Consistency #

Mismatched Swift versions between your command line and Xcode can cause dependency compilation discrepancies. Check:

• Command line: Run swift --version
• Xcode: Go to Xcode > About Xcode to see the included Swift version
  If they don’t match, set Xcode’s Swift version to match the command line in Build Settings > Swift Compiler - Language > Swift Language Version.

These steps should cover most cases where Xcode can’t find SPM modules despite successful command-line builds. For me, regenerating the Xcode project or clearing the cache usually fixes it right away.

内容的提问来源于stack exchange，提问作者Egor Kolyshkin