Most Flutter developers have already migrated to Swift Package Manager without noticing. It has been enabled by default since Flutter 3.44 , and the tooling adds the integration to your Xcode project the first time you build after upgrading. The reason to pay attention now is a date: the CocoaPods registry becomes read-only on December 2, 2026 . After that, opting out stops being a supported escape hatch. Flutter 3.47 reports that 92 of the top 100 iOS plugins have migrated to Swift Package Manager . The long tail is what will bite you, not the head of the distribution. What actually changes in your project When SwiftPM is enabled and you build, Flutter modifies your Xcode project in three ways: Adds FlutterGeneratedPluginSwiftPackage as a package dependency of the Runner target. Adds a Run Prepare Flutter Framework Script pre-action to your build scheme. Resolves and downloads the Swift packages your Flutter plugins depend on. That generated package lives at ios/Flutter/ep...