How to distinguish between using CocoaPods and Swift Package Manager for dependency management in a project?

CocoaPods and Swift Package Manager (SPM) are two popular tools for managing dependencies in iOS projects, but they differ in their integration and configuration methods.

• CocoaPods:

  • Uses a Podfile to describe dependencies.
  • After installing dependencies, it creates a .xcworkspace file, which should be opened instead of .xcodeproj.
  • Dependencies are downloaded and integrated into the project through a separate workspace.
  • Requires installation via RubyGems (gem install cocoapods).

• Swift Package Manager:

  • Built into Xcode (starting from Xcode 11).
  • Dependencies are added through the Xcode menu (File → Swift Packages → Add Package Dependency) or via Package.swift in server-side projects.
  • Does not require a separate workspace, integrates directly into the project.
  • Uses a declarative manifest Package.swift.

How to distinguish:

• If the project has a Podfile and uses .xcworkspace, then CocoaPods is used.
• If dependencies are added through Xcode and there is no Podfile, but there is a Package.resolved and Package.swift, then Swift Package Manager is used.