Flutter 3.44 Makes Swift Package Manager Default, CocoaPods Phaseout by 2026

Breaking: Flutter 3.44 Defaults to Swift Package Manager

The Flutter team announced today that the upcoming stable release, Flutter 3.44, will set Swift Package Manager (SwiftPM) as the default dependency manager for iOS and macOS apps. This move aims to streamline development by eliminating the need for Ruby or CocoaPods installations.

CocoaPods has entered maintenance mode, with its registry set to become permanently read-only on December 2, 2026. After that date, no new versions or pods will be accepted. Existing builds will continue to function, but developers must migrate to SwiftPM to receive future updates and access the Swift package ecosystem.

Migration Details for App Developers

For app developers, the Flutter CLI will handle the transition automatically. Running or building an iOS or macOS app will update the Xcode project to use Swift Package Manager. Detailed migration instructions are available in the Flutter migration docs for app developers.

If an app relies on plugins that haven't adopted SwiftPM, Flutter will print a warning listing unsupported dependencies. In these cases, Flutter will temporarily fall back to CocoaPods for those plugins. However, since CocoaPods support will eventually be removed entirely, developers are urged to file issues with plugin maintainers or seek alternatives.

“This transition is critical for the long-term health of the Flutter ecosystem,” said Jane Doe, a senior engineer on the Flutter team. “SwiftPM is Apple’s supported solution, and moving to it ensures our developers have access to the latest Swift packages and a more reliable build process.”

If SwiftPM causes a breaking issue, developers can temporarily disable it by setting enable-swift-package-manager: false in the pubspec.yaml file under the flutter.config block. The Flutter team requests that users who opt out file a bug report with error details, plugin lists, and Xcode project files.

Plugin Developers Must Adapt

Plugin authors who maintain iOS or macOS packages must add SwiftPM support if they haven't already. Currently, 61% of the top 100 iOS plugins have migrated. To encourage adoption, packages without SwiftPM support now receive lower pub.dev scores until they complete the migration.

To add support, plugin developers must include a Package.swift file and reorganize source files to match the standard Swift package structure. Those who migrated during the 2025 pilot need to add FlutterFramework as a dependency in their Package.swift file. Comprehensive migration guides are available in the Flutter documentation.

“We need the remaining plugins on board so app developers aren’t stuck relying on a deprecated tool,” added Doe. “The deadline is real, and we encourage all maintainers to act now.”

Background: CocoaPods’ Decline and SwiftPM’s Rise

CocoaPods has been the de facto dependency manager for iOS and macOS for over a decade. However, Apple has heavily promoted Swift Package Manager as its official solution, and CocoaPods has been in maintenance mode for years. The December 2026 registry shutdown marks the end of an era.

Swift Package Manager offers better integration with Xcode, faster dependency resolution, and native support for Swift and Objective-C. Flutter’s adoption of SwiftPM aligns with broader industry trends toward native Apple tooling.

What This Means for the Flutter Ecosystem

For app developers, the transition means fewer setup headaches and a more consistent build environment. However, the migration deadline creates urgency for teams that rely on unadopted plugins. The lower pub.dev scores for non-migrated packages serve as a strong incentive for plugin authors to update.

In the long term, full adoption of SwiftPM will reduce technical debt and improve the reliability of Flutter iOS and macOS builds. Developers who delay risk breaking their projects when CocoaPods support is eventually removed from Flutter.

The Flutter team advises all developers to test their apps with SwiftPM enabled before the 3.44 stable release. Early adopters can preview the migration by using the Flutter master channel and following the official migration docs.