Flutter iOS build fails with "Framework 'Pods_Runner' not found" on Xcode 26.2 beta
08:47 18 Feb 2026

I'm getting a linker error when building my Flutter iOS app on the simulator:

Error (Xcode): Framework 'Pods_Runner' not found
Error (Xcode): Linker command failed with exit code 1 (use -v to see invocation)

Environment:

  • Xcode 26.2 (Build 17C52)

  • macOS Darwin 25.2.0 (Apple Silicon M1)

  • Flutter (stable channel)

  • CocoaPods

What I've tried (none worked):

  1. flutter clean + flutter pub get + pod install

  2. pod deintegrate + pod cache clean --all + pod install

  3. Clearing DerivedData (rm -rf ~/Library/Developer/Xcode/DerivedData)

  4. Changing use_frameworks! to use_frameworks! :linkage => :static in Podfile

  5. Adding FRAMEWORK_SEARCH_PATHS with ${PODS_CONFIGURATION_BUILD_DIR} in post_install

  6. Completely deleting the ios/ folder and regenerating it with flutter create --platforms ios . — same error on a fresh iOS project

Key finding: The Pods_Runner.framework is never produced in the build output. The Pods-Runner target exists in Pods.xcodeproj with productType = "com.apple.product-type.framework", and the main Runner.xcodeproj references Pods_Runner.framework in its link phase, but Xcode 26 never actually builds it.

Podfile:

platform :ios, '14.0'
ENV['COCOAPODS_DISABLE_STATS'] = 'true'

project 'Runner', {
  'Debug' => :debug,
  'Profile' => :release,
  'Release' => :release,
}

# ... flutter_root helper ...

target 'Runner' do
  use_frameworks!
  flutter_install_all_ios_pods File.dirname(File.realpath(__FILE__))
  target 'RunnerTests' do
    inherit! :search_paths
  end
end

post_install do |installer|
  installer.pods_project.targets.each do |target|
    flutter_additional_ios_build_settings(target)
  end
end

Dependencies include: flutter_secure_storage, google_mlkit_face_detection, mobile_scanner, image_picker, shared_preferences, sqflite, path_provider

This seems to be an Xcode 26 beta issue since a completely regenerated iOS project fails the same way. Has anyone found a workaround?

ios swift flutter xcode xcode26