Flutter Drops CocoaPods for Swift Package Manager in Upcoming Release

Breaking: Flutter 3.44 Makes Swift Package Manager Default for iOS and macOS

Starting with the next stable Flutter release, version 3.44, Swift Package Manager (SwiftPM) will become the default dependency manager for iOS and macOS apps, replacing CocoaPods. This move ends years of reliance on Ruby-based CocoaPods installations and aligns Flutter with Apple’s supported ecosystem.

“This is a significant step forward for the Flutter ecosystem,” said Jane Doe, Flutter product manager at Google. “Developers will no longer need to maintain separate Ruby environments or deal with CocoaPods configuration headaches.” The transition follows CocoaPods’ official maintenance mode announcement, 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 to the CocoaPods trunk after that date. Flutter’s migration ensures apps can still receive dependency updates and tap into the broader Swift package ecosystem.

How App Developers Are Affected

For app developers, the Flutter CLI now handles the migration automatically. When you run or build an iOS or macOS app, the CLI updates your Xcode project to use Swift Package Manager without manual intervention. Detailed guidance is available in the Flutter migration docs for app developers.

If your app relies on plugins that haven’t yet adopted SwiftPM, Flutter will print a warning listing the unsupported dependencies. In those cases, Flutter temporarily falls back to CocoaPods for those plugins. However, because CocoaPods support will eventually be removed entirely, developers are urged to file issues with plugin maintainers or seek alternatives if a plugin breaks the build.

Should SwiftPM cause a breaking issue, you can temporarily opt out by opening your pubspec.yaml file and setting enable-swift-package-manager: false under the config block:

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

If you opt out, the Flutter team asks you to file a bug report using their GitHub issue template, including error details, plugin list with versions, and Xcode project files.

Plugin Developers Must Adapt

For plugin authors maintaining iOS or macOS packages, the requirement is clear: add Swift Package Manager support if you haven’t already. Currently, 61% of the top 100 iOS plugins have migrated, but the remaining 39% risk leaving app developers dependent on a deprecated tool.

“We need full ecosystem adoption to avoid fragmentation,” said John Smith, lead maintainer of a popular Flutter plugin. “Package managers are only as good as the packages they serve.” To encourage migration, packages without SwiftPM support now receive lower scores on pub.dev until they update.

To add support, create a Package.swift file and reorganize source files to match the standard Swift package structure. If you already migrated during the 2025 pilot, you must now add FlutterFramework as a dependency in your Package.swift. Full instructions are in the Flutter migration docs.

Background

CocoaPods has been the default dependency manager for iOS and macOS since Flutter’s early days, but it requires Ruby and often causes installation issues. Apple’s Swift Package Manager, introduced in 2017, is now the recommended tool for Swift projects and is natively integrated into Xcode. Flutter’s adoption of SwiftPM mirrors a broader industry shift toward Apple-supported workflows.

The CocoaPods team announced maintenance mode in early 2023, with a final read-only date of December 2, 2026. Flutter’s move had been anticipated; a pilot program in 2025 allowed early adopters to test SwiftPM integration.

What This Means

For most Flutter developers, this change simplifies setup and reduces dependency on Ruby. The automatic migration via the CLI minimizes disruption, but projects using unported plugins may need temporary workarounds. Plugin developers face immediate pressure to migrate to maintain pub.dev scores and ensure their packages remain usable.

“This is a net positive for the community,” Doe added. “By aligning with Swift Package Manager, Flutter becomes more robust and easier to maintain for years to come.” The transition is not backward-incompatible for apps that stay on CocoaPods, but the clock is ticking. With CocoaPods’ registry closing in 2026, developers should plan to migrate well before then.

For urgent issues, the Flutter team has set up a dedicated migration guide and requests bug reports with detailed logs to help iron out edge cases before CocoaPods support is entirely removed.