Flutter 3.44 Makes Swift Package Manager Default, Puts CocoaPods on Notice

By ● min read

Breaking: Swift Package Manager Now Default in Flutter 3.44

Starting with Flutter 3.44, Swift Package Manager (SwiftPM) becomes the default dependency manager for iOS and macOS apps, replacing CocoaPods. The move eliminates the need for Ruby or CocoaPods installations to run Flutter apps on Apple platforms.

Flutter 3.44 Makes Swift Package Manager Default, Puts CocoaPods on Notice

CocoaPods has officially entered maintenance mode, with its registry set to become permanently read-only on December 2, 2026. While existing builds will continue to work, no new versions or pods will be added after that date.

“Flutter is transitioning to Apple’s supported dependency management solution to ensure continued access to the Swift package ecosystem,” said a Flutter team spokesperson. “This change benefits developers by reducing tooling complexity and aligning Flutter with industry standards.”

Background

CocoaPods has been the default dependency manager for iOS and macOS Flutter apps since the framework’s early days. However, the tool requires Ruby and a dedicated CocoaPods installation, adding overhead for developers.

Swift Package Manager, introduced by Apple in 2019, is now bundled with Xcode and offers tighter integration with native iOS and macOS development. Flutter’s adoption follows a broader industry shift toward SwiftPM across the Apple developer ecosystem.

What This Means

For App Developers

The Flutter CLI handles the migration automatically. When you run or build your iOS/macOS app, the CLI updates your Xcode project to use SwiftPM. If your app uses plugins that haven’t adopted SwiftPM, Flutter prints a warning listing unsupported dependencies and temporarily falls back to CocoaPods for those plugins.

“Eventually CocoaPods support will be removed entirely,” the spokesperson warned. “If a plugin hasn’t updated and breaks your build, file an issue with the maintainer or find an alternative package that supports SwiftPM.”

If SwiftPM causes a critical issue, developers can temporarily disable it in pubspec.yaml:

flutter:
  config:
    enable-swift-package-manager: false

If you opt out, file a bug report with error details, plugin list, and Xcode project files.

For Plugin Developers

Plugin authors must add SwiftPM support if they haven’t already. Currently, 61% of the top 100 iOS plugins have migrated. Packages without SwiftPM support now receive lower pub.dev scores to encourage adoption.

To add support, include a Package.swift file and restructure source files to match Swift package conventions. For those who migrated during the 2025 pilot, a new step requires adding FlutterFramework as a dependency in Package.swift.

Urgent Call to Action

The CocoaPods registry will go read-only in under 18 months. App developers should verify that their plugins support SwiftPM before the December 2026 deadline. Plugin maintainers who have not yet migrated should prioritize adoption to avoid losing pub.dev visibility and to keep their packages compatible.

For detailed migration steps, refer to the Flutter migration docs. The Flutter team urges all developers to test their apps with SwiftPM now to identify and resolve issues early.

Tags: