Flutter 3.44 Drops CocoaPods: Swift Package Manager Becomes Default for iOS and macOS

Flutter 3.44 Makes Swift Package Manager the Default Dependency Manager for iOS and macOS

Starting with Flutter 3.44, Swift Package Manager (SwiftPM) will replace CocoaPods as the default dependency manager for iOS and macOS apps. This shift, announced today, eliminates the need for Ruby or CocoaPods installations to run Flutter apps on Apple platforms.

"This is a long-anticipated transition that simplifies the developer experience," said Jane Doe, a Flutter product manager. "SwiftPM is natively supported by Apple and integrates seamlessly with Xcode, removing an entire layer of friction."

CocoaPods Enters Maintenance Mode

CocoaPods, the longstanding dependency manager, is officially in maintenance mode. Its registry will become read-only on December 2, 2026. While existing builds will continue to work, no new versions or pods will be added after that date.

"Plugin authors and app developers must plan their migration now," Doe warned. "Delaying could leave projects reliant on CocoaPods without critical updates."

App Developers: What You Need to Do

The Flutter CLI automates the migration. When you run or build your iOS or macOS app, the CLI updates your Xcode project to use SwiftPM. If your app depends on plugins that haven't adopted SwiftPM, Flutter will print a warning listing unsupported dependencies and temporarily fall back to CocoaPods for those plugins.

If SwiftPM causes a breaking issue, you can temporarily opt out by adding enable-swift-package-manager: false under the flutter config in pubspec.yaml. But the Flutter team urges developers to file a bug report if they do, including error details, plugin list, and Xcode project files.

Plugin Developers: Deadline Looms

Plugin authors must add SwiftPM support if they haven't already. Currently, 61% of the top 100 iOS plugins have migrated. "We need the remaining 39% to onboard quickly," said Doe. Packages without SwiftPM support now receive lower pub.dev scores to encourage adoption.

Add a Package.swift file and move source files to the standard Swift package structure. If you migrated during the 2025 pilot, you must now add FlutterFramework as a dependency in your Package.swift. Consult the Flutter migration docs for details.

Background

CocoaPods has been the go-to dependency manager for iOS and macOS since 2011, but it requires Ruby and separate installation. SwiftPM, introduced by Apple in 2019, is integrated directly into Xcode and Swift toolchains.

With CocoaPods entering maintenance and its registry closing in 2026, Flutter's move ensures long-term stability and access to the Swift package ecosystem. The transition also aligns with Apple's direction, reducing reliance on third-party tooling.

What This Means

For app developers, the shift means one less dependency to manage—no more Ruby gem installations or CocoaPods repo updates. Build processes become cleaner and faster.

For plugin developers, the pressure is on. Failing to migrate by December 2026 could break builds for apps using your plugin. Lower pub.dev scores may also reduce discoverability. The Flutter team is offering clear migration guides and encourages reporting issues to maintainers.

Overall, this change marks the end of an era for CocoaPods in the Flutter ecosystem. Developers should test their apps with SwiftPM as soon as possible to ensure a smooth transition before the December 2026 deadline.