Flutter's Transition to Swift Package Manager: What Developers Need to Know

Flutter developers working on iOS and macOS projects are about to witness a significant shift in dependency management. Starting with the upcoming stable release, Flutter 3.44, Swift Package Manager (SwiftPM) will become the default tool for handling iOS and macOS dependencies, effectively phasing out CocoaPods. This change promises a simpler, more seamless workflow without the need for Ruby installations or CocoaPods configuration. Let's explore what this transition entails for both app developers and plugin authors.

The Shift to Swift Package Manager

CocoaPods has been a staple in the iOS development ecosystem for years, but it's now officially in maintenance mode. Its registry will be permanently read-only as of December 2, 2026. While existing builds will continue to function, no new pods or updates will be added after that date. To ensure access to ongoing dependency updates and the broader Swift package ecosystem, Flutter is adopting Apple's native solution: Swift Package Manager. This move aligns with industry trends and reduces friction for cross-platform development.

How the Migration Works for App Developers

For most app developers, the transition is straightforward. The Flutter CLI handles the heavy lifting automatically. When you run or build your iOS or macOS app, the CLI updates your Xcode project to use SwiftPM instead of CocoaPods. No manual intervention is required. For detailed instructions, refer to the Flutter migration docs for app developers.

However, if your app depends on plugins that haven't yet adopted SwiftPM, Flutter will display a warning listing those unsupported dependencies. In such cases, Flutter temporarily falls back to CocoaPods for those specific plugins. But since CocoaPods support will eventually be removed entirely, it's crucial to ensure all your dependencies support Swift Package Manager. If a plugin breaks your build due to lack of SwiftPM support, you should file an issue with its maintainer or seek an alternative package.

What If SwiftPM Causes Issues?

Migrations can sometimes encounter unexpected problems. If SwiftPM introduces a breaking issue in your project, you can temporarily disable it. Open your pubspec.yaml file, navigate to the flutter section, and set enable-switch-package-manager to false under the config block:

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

When opting out, please help improve Flutter by filing a bug report using the Flutter GitHub issue template. Include error details, a list of your plugins and versions, and copies of your Xcode project files. This will aid resolution before CocoaPods is fully deprecated.

Plugin Developers: Steps to Migrate

Plugin authors play a critical role in this transition. If you maintain an iOS or macOS plugin, you must add Swift Package Manager support if you haven't already. Currently, about 61% of the top 100 iOS plugins have migrated. The remaining 39% need to catch up to avoid leaving app developers reliant on a deprecated tool. To encourage adoption, packages without SwiftPM support now receive lower scores on pub.dev until they migrate.

To add support, you need to:

1. Create a Package.swift file in your plugin's iOS or macOS directory.
2. Rearrange your source files to match the standard Swift package structure.
3. If you already migrated during the 2025 pilot, add FlutterFramework as a dependency in your Package.swift file.

For full guidance, consult the Flutter migration docs for plugin developers.

Conclusion

The move to Swift Package Manager marks a new chapter for Flutter's iOS and macOS support. With a set deadline and clear migration paths, both app developers and plugin authors can prepare ahead. By adopting SwiftPM, the Flutter community ensures smoother workflows, better integration with Apple's ecosystem, and long-term access to updates. Embrace the change now to avoid last-minute issues when CocoaPods support is eventually removed.