Flutter 3.44 Embraces Swift Package Manager: What Developers Need to Know

The Shift Begins: Swift Package Manager Takes Over

With the upcoming stable release of Flutter 3.44, the development framework is making a significant change to its iOS and macOS dependency management. Swift Package Manager (SwiftPM) will become the default tool for handling dependencies, effectively replacing CocoaPods. This move streamlines the setup process—no more Ruby installations or CocoaPods configurations just to get your app running. The change reflects a broader industry shift toward Apple's native solution and ensures Flutter stays aligned with modern development practices.

The End of an Era: CocoaPods Goes into Maintenance Mode

CocoaPods has been the backbone of iOS dependency management for years, but its time is winding down. The project is now in official maintenance mode, and its registry will permanently become read-only on December 2, 2026. After that date, no new versions or pods will be added to the trunk. Existing builds will continue to work, but without updates or new packages, relying on CocoaPods becomes a dead end. Flutter's transition to Swift Package Manager ensures that apps can still receive dependency updates and tap into the broader Swift package ecosystem.

What App Developers Should Expect

For most app developers, the migration is handled automatically by the Flutter CLI. When you run or build your iOS or macOS app, the CLI will update your Xcode project to use Swift Package Manager. The process is designed to be seamless, but it's worth checking the official Flutter migration documentation for app-specific details.

Handling Unsupported Plugins

If your app relies on plugins that haven't yet adopted Swift Package Manager, Flutter will print a warning during the build process, listing exactly which dependencies are unsupported. In these cases, Flutter will temporarily fall back to CocoaPods for those specific plugins. However, because CocoaPods support will eventually be removed entirely, you should urge plugin maintainers to update. If a necessary plugin breaks your build, file an issue with the maintainer or look for an alternative package that already supports SwiftPM.

Temporarily Opting Out

If SwiftPM causes a critical issue in your project, you can temporarily disable it. Open your pubspec.yaml file, go to the flutter section, and under the config block set enable-swift-package-manager to false:

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

This opt-out is a stopgap measure. If you use it, please report a bug using the Flutter GitHub issue template, including error details, a list of your plugins and versions, and copies of your Xcode project files. This helps the Flutter team resolve issues before CocoaPods is completely removed.

What Plugin Developers Need to Do

Plugin authors are the key to a smooth transition. If you maintain an iOS or macOS plugin, you must add Swift Package Manager support if you haven't already. As of now, 61% of the top 100 iOS plugins have migrated. The remaining plugins need to catch up so app developers aren't stuck relying on a deprecated tool. To encourage adoption, packages without SwiftPM support will receive lower pub.dev scores until they migrate.

Adding Swift Package Manager Support

To add support, create a Package.swift file and reorganize your source files to match the standard Swift package structure. If you already migrated during the 2025 pilot, you need one additional step: add FlutterFramework as a dependency in your Package.swift file. For complete instructions, refer to the Flutter migration docs for plugin developers.

Looking Ahead: A CocoaPods-Free Ecosystem

This migration is part of a broader trend. Apple has been steering developers toward Swift Package Manager for years, and Flutter's adoption ensures compatibility with the latest iOS features and tools. While the transition may require some effort, the long-term benefits are clear: simpler setup, better integration with Xcode, and access to a modern package ecosystem. Start testing your apps with SwiftPM today to identify any issues early.

For further details, see the official announcements on the Flutter blog or the migration documentation linked in the sections above.