Flutter 3.44 to Default to Swift Package Manager, Phasing Out CocoaPods by 2026
Breaking: Flutter Abandons CocoaPods for Swift Package Manager
The Flutter team has announced that starting with the next stable release (version 3.44), Swift Package Manager (SwiftPM) will become the default dependency manager for iOS and macOS apps, replacing CocoaPods. This marks a major shift in the Flutter ecosystem, aiming to simplify setup and align with Apple's preferred tools.
"This transition removes the need for Ruby installations and CocoaPods headaches," a Flutter spokesperson said. "Developers can now rely on a native, Apple-supported solution." Existing CocoaPods builds will still function, but the CocoaPods registry will become permanently read-only on December 2, 2026, halting all new pod submissions.
Background: The End of an Era for CocoaPods
CocoaPods has been the go-to dependency manager for iOS and macOS development for over a decade, but it entered maintenance mode in late 2023. With Apple actively developing Swift Package Manager and integrating it into Xcode, Flutter's move ensures long-term compatibility. The community has been preparing for this shift, with 61% of the top 100 iOS plugins already migrated to SwiftPM.
The December 2026 deadline gives developers a two-year window to migrate. After that, no new versions or pods will be added to the CocoaPods trunk, and Flutter will drop all fallback support.
What This Means for Developers
For app developers, the transition is largely automatic. When you run or build an iOS/macOS app with Flutter 3.44+, the CLI will update your Xcode project to use SwiftPM. If you rely on plugins that haven't migrated yet, Flutter will print a warning listing those dependencies and temporarily fall back to CocoaPods for them—but this fallback will be removed entirely in the future.
"If a plugin breaks because it hasn't adopted SwiftPM, file an issue with its maintainer or find an alternative," the Flutter team advised. To opt out temporarily, set enable-swift-package-manager: false in your pubspec.yaml under the flutter: config: block, but be sure to file a bug report.
App Developers: Migration Steps
No manual intervention is needed for most apps. The Flutter CLI handles project updates automatically. However, if you have custom Xcode project settings, review the official migration docs. If you disable SwiftPM, provide error details, plugin list, and Xcode files to help the team improve the tool before CocoaPods is fully removed.
Plugin Developers: Mandatory SwiftPM Adoption
Plugin authors must add Swift Package Manager support to avoid lower pub.dev scores and eventual build failures. The team reports that 39% of top plugins still lack SwiftPM support. If you already migrated during the 2025 pilot, you now need to add FlutterFramework as a dependency in your Package.swift. Follow the Flutter migration docs for plugins.
"We need the remaining plugins on board so app developers aren’t stuck relying on a deprecated tool," the spokesperson emphasized.
Timeline and Final Word
Flutter 3.44 is expected to ship in the coming weeks. CocoaPods support will be completely removed in a future stable release after the December 2026 registry shutdown. Developers are urged to test their apps with SwiftPM now to ensure a smooth transition.