Breaking: Flutter Shifts to Swift Package Manager as Default Dependency Manager
In a major shift for Flutter developers, the upcoming stable release (version 3.44) will replace CocoaPods with Swift Package Manager (SwiftPM) as the default dependency manager for iOS and macOS apps. The move eliminates the need for Ruby and CocoaPods installations, streamlining the build process for all Flutter projects targeting Apple platforms.
"This change simplifies the developer experience by tapping into Apple's native dependency management ecosystem," said a Flutter engineering lead. "We're committed to ensuring a smooth transition before CocoaPods support is fully retired." CocoaPods will enter read-only mode on December 2, 2026, with no new versions or pods allowed after that date.
Immediate Impact for App Developers
For most app developers, the migration is handled automatically by the Flutter CLI. Running or building an iOS/macOS app will trigger an update to the Xcode project, switching to SwiftPM. However, if a project depends on plugins that haven't yet adopted SwiftPM, Flutter will temporarily fall back to CocoaPods for those specific dependencies while issuing a warning.
"If a critical plugin hasn't migrated, app developers should file an issue with the maintainer or find an alternative," the lead added. "We recommend checking your plugin list early." A temporary opt-out is available by setting enable-swift-package-manager: false in the pubspec.yaml file's flutter section, but this is discouraged and should be accompanied by a bug report.
Plugin Developers Face Urgent Deadline
Plugin authors must add SwiftPM support immediately, as CocoaPods support will eventually be removed entirely. Currently, only 61% of the top 100 iOS plugins have migrated. Packages without SwiftPM support will receive lower pub.dev scores to encourage adoption.
"We need the remaining 39% to onboard quickly to avoid build breaks for app developers," warned a Flutter developer advocate. Migrated plugins must now include FlutterFramework as a dependency in their Package.swift file—a new requirement for those who participated in the 2025 pilot. Detailed guidance is available in the Flutter migration docs for plugin developers.
Background
CocoaPods has been the standard dependency manager for iOS/macOS in Flutter for years, but its community-driven maintenance mode signaled the need for a transition. Apple's Swift Package Manager offers tighter integration with Xcode and the broader Swift ecosystem, making it the natural replacement. The read-only deadline of December 2, 2026, provides a window for migration, but Flutter's default change accelerates adoption.
What This Means
For app developers, the immediate benefit is a cleaner setup without Ruby dependencies. For plugin developers, the pressure is on: failure to adopt SwiftPM risks breaking builds for thousands of apps. The shift also aligns Flutter with modern Apple tooling, potentially improving stability and performance. However, early adopters may encounter edge cases—Flutter advises reporting issues promptly via GitHub. Ultimately, this change signals the end of an era for CocoaPods in the Flutter ecosystem, paving the way for a more unified dependency management experience.