Flutter’s Shift from CocoaPods to Swift Package Manager: What You Need to Know

Starting with Flutter 3.44, the default dependency manager for iOS and macOS apps changes from CocoaPods to Swift Package Manager (SwiftPM). This move ends the need for Ruby or CocoaPods installations, simplifies workflows, and aligns with Apple’s supported ecosystem. CocoaPods enters maintenance mode, becoming read‑only on December 2, 2026. While existing builds continue, no new pods will appear after that date. Below are answers to common questions about this transition.

What exactly is changing with CocoaPods and Flutter?

Flutter 3.44 makes Swift Package Manager the default for managing iOS and macOS dependencies, replacing CocoaPods. CocoaPods is now in maintenance mode, and its registry will be read‑only after December 2, 2026. After that date, no new versions or pods can be added. Existing projects that rely on CocoaPods will still build, but they won’t receive updates. Flutter’s shift ensures apps can access the larger Swift package ecosystem and remain supported by Apple’s evolving tools.

Flutter’s Shift from CocoaPods to Swift Package Manager: What You Need to Know

Why is Flutter switching to Swift Package Manager?

Swift Package Manager is Apple’s native dependency management solution, fully supported and integrated into Xcode. By adopting SwiftPM, Flutter removes the need for Ruby installations and CocoaPods setup, making the development process more straightforward. CocoaPods is no longer actively developed (maintenance mode) and will stop receiving updates. Moving to SwiftPM future‑proofs Flutter apps, gives them access to the wide Swift package ecosystem, and ensures continued dependency updates after CocoaPods’ registry becomes read‑only.

How does this affect app developers?

For app developers, the Flutter CLI manages the transition automatically. When you run or build your iOS or macOS app, the CLI updates the Xcode project to use Swift Package Manager. If any of your plugins haven’t adopted SwiftPM yet, Flutter shows a warning listing those dependencies and temporarily falls back to CocoaPods for them. Because CocoaPods support will eventually be removed, you should request Swift support from plugin maintainers or find alternatives if a plugin breaks your build.

What if SwiftPM causes a breaking issue in my project?

If you encounter a problem, you can temporarily disable SwiftPM. Open your pubspec.yaml file, go to the flutter section, and under config set enable-swift-package-manager: false. After opting out, please file a bug report using the Flutter GitHub issue template. Include error details, your plugin list and versions, and copies of your Xcode project files. This helps resolve issues before CocoaPods support is completely removed.

What do plugin developers need to do?

Plugin authors who maintain iOS or macOS plugins must add Swift Package Manager support if they haven’t already. This involves creating a Package.swift file and moving source files to match the standard Swift package structure. If you migrated during the 2025 pilot, you now need one additional step: add FlutterFramework as a dependency in your Package.swift. Full migration details are in the Flutter migration docs. Currently, 61% of the top 100 iOS plugins have migrated. To encourage adoption, packages without SwiftPM support receive lower pub.dev scores until they migrate.

When is the final deadline for CocoaPods?

CocoaPods’ registry becomes permanently read‑only on December 2, 2026. After that date, no new pods or versions can be added, and existing ones cannot be updated. While projects using CocoaPods will still build, they won’t receive any new dependencies or security patches. Flutter plans to remove CocoaPods fallback support entirely by that time, so migrating plugins and apps before the deadline is essential.

Tags: