© 2026 Hashnode
When building a multi-module iOS app using Swift Package Manager, importing third-party libraries like Firebase directly into multiple feature modules quickly becomes messy. It leads to duplicated configurations, tight coupling, and hard-to-maintain ...

Ever wondered how your favorite music streaming app ensures smooth audio playback with tools like AudioKit? Or how does it handle all those network requests efficiently using Alamofire? Managing these libraries manually would be chaotic—how do develo...

Introduction Hi folks, today we're diving into the importance of modularization in Swift application development. Later in this post, I'll walk you through creating your own package using Swift Package Manager and how to integrate it into other Xcode...

What is SPM? Swift Package Manager, is Apple’s tool for easily adding libraries and frameworks to your project. Introduced in 2015, it’s loved for its simplicity. Compared to CocoaPods, SPM’s integration is straightforward, and it’s widely adopted, s...

Ideally, you would not require conditional logic in your production code to check if tests are running or the main app target is running. But, there are situations where you can't get around it in case of Integration tests or UI Tests. There are vari...

If you have used SPM to create the command line application before Swift 5.9.0, the project structure used to be as follows: Package.swift README.md .gitignore Sources/ Sources/SamplePackage/main.swift Tests/ Tests/LinuxMain.swift Tests/SamplePackage...

Third-party SDKs may use Swift packages to vent their binary frameworks from a server that requires authentication. In Xcode Cloud you will encounter the error Could not resolve package dependencies: failed downloading ... if you don't provide the ne...
