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

Breaking: Flutter 3.44 Makes Swift Package Manager the Default

The next stable Flutter release, version 3.44, will replace CocoaPods with Swift Package Manager (SwiftPM) as the default dependency manager for iOS and macOS apps. The shift marks the end of an era for CocoaPods, which enters maintenance mode with its registry going read-only on December 2, 2026.

“This transition streamlines the developer experience by removing the need for Ruby or CocoaPods installations,” the Flutter team announced. “Existing builds will continue to work, but no new versions or pods will be added to the trunk after the cutoff date.”

To ensure ongoing dependency updates and access to the Swift package ecosystem, Flutter is moving to Apple’s natively supported solution. The Flutter CLI now handles migration automatically when you run or build an iOS or macOS app, updating the Xcode project behind the scenes.

Background: Why the Shift?

CocoaPods has been a staple for iOS dependency management for over a decade, but it relies on Ruby and external infrastructure. Apple’s Swift Package Manager, introduced in 2019, is integrated directly into Xcode and the Swift ecosystem, offering better performance and tighter integration.

The Flutter team has been piloting SwiftPM support since 2025. Now, with CocoaPods officially deprecated, Flutter 3.44 makes SwiftPM the default to reduce friction and future-proof app development.

What This Means for App Developers

For most app developers, the migration is invisible. The Flutter CLI automatically updates Xcode project settings when you run or build. If your app uses plugins that haven’t adopted SwiftPM, Flutter will print a warning listing the unsupported dependencies and temporarily fall back to CocoaPods.

“CocoaPods support will eventually be removed entirely,” the team warned. “If a plugin hasn’t updated and breaks your build, file an issue with the dependency’s maintainer or find an alternative package.”

If SwiftPM causes a breaking issue, you can temporarily disable it in pubspec.yaml by setting enable-swift-package-manager: false under the flutter block. The team urges developers who opt out to file a bug report with error details, plugin list, and Xcode project files to help resolve issues before CocoaPods is completely removed.

What This Means for Plugin Developers

Plugin authors who maintain iOS or macOS plugins must add SwiftPM support. Currently, 61% of the top 100 iOS plugins have migrated. The remaining plugins need onboard to avoid leaving app developers reliant on a deprecated tool.

“To encourage adoption, packages without Swift Package Manager support receive lower pub.dev scores until they migrate,” the Flutter team noted. To add support, create a Package.swift file and restructure source files per the Swift package standard. If you already migrated during the 2025 pilot, you must now add FlutterFramework as a dependency in Package.swift.

Timeline and Urgency

The CocoaPods registry will become permanently read-only on December 2, 2026. After that date, no new versions or pods can be added. While existing builds remain functional, developers relying on CocoaPods will lose access to updates. The Flutter team recommends completing migration before that deadline.

Detailed migration docs are available for both app developers and plugin developers. For any issues, use the Flutter GitHub issue template to ensure timely support.