Why this happens
A Flutter iOS project contains several independently configured build targets. Changing the minimum iOS version for Runner does not necessarily change the deployment target of every dependency in the generated Pods project.
That is why you can still see this warning after updating the app target:
warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 8.0, but the range of supported deployment target versions is 9.0 to 14.0.99. (in target 'FirebaseAuth' from project 'Pods')
Those version numbers describe the toolchain in the original report, not a current recommendation. The underlying problem is an outdated deployment target on a pod target. Also, this is a warning: if the build ends with Encountered error while building for device., inspect the full log for a separate error before assuming deployment targets are the only cause.
How to fix it
1. Choose one supported minimum and align Runner with the Podfile
Choose an iOS minimum that meets all three requirements:
- Your installed Xcode supports building for it.
- Your Flutter SDK supports it.
- Your plugins and native dependencies support it.
The examples below use iOS 13.0 only as an illustration. Replace it everywhere with the minimum appropriate for your project. A dependency requiring a newer version takes precedence over this example.
From the Flutter project root, open the iOS workspace:
open ios/Runner.xcworkspace
In Xcode:
- Select the Runner project in the project navigator.
- Select the Runner app target.
- Open Build Settings and search for iOS Deployment Target.
- Set the intended minimum for every build configuration, including any custom configurations.
Then open ios/Podfile and set its platform declaration to the same version:
platform :ios, '13.0'
If the declaration starts with #, remove that comment marker. Update the existing declaration rather than adding conflicting declarations.
This establishes your app’s minimum and CocoaPods’ platform requirement. Some pod targets can still retain explicit older deployment settings, which the next step addresses.
2. Correct outdated pod targets in the existing post-install hook
Edit ios/Podfile, not the generated Pods.xcodeproj. Manual changes to generated pod targets can disappear the next time CocoaPods installs dependencies.
Find the existing post_install block. For a standard Flutter Podfile that already uses this structure, merge the following logic into it:
post_install do |installer|
minimum_ios_version = '13.0'
installer.pods_project.targets.each do |target|
flutter_additional_ios_build_settings(target)
target.build_configurations.each do |config|
current = config.build_settings['IPHONEOS_DEPLOYMENT_TARGET']
if current.nil? ||
Gem::Version.new(current.to_s) < Gem::Version.new(minimum_ios_version)
config.build_settings['IPHONEOS_DEPLOYMENT_TARGET'] = minimum_ios_version
end
end
end
end
Use the same minimum you selected in step 1. This assumes explicit deployment-target values are version strings, as they normally are in generated pod targets. If your project uses a custom build-setting expression there, inspect that configuration rather than trying to parse it as a version.
Keep flutter_additional_ios_build_settings(target): Flutter’s generated Podfile includes that call to apply its additional iOS build settings. Also preserve any unrelated customization already in your hook. Do not add a second competing post_install block.
A commonly reported fix assigns the chosen version unconditionally:
config.build_settings['IPHONEOS_DEPLOYMENT_TARGET'] = '13.0'
The conditional version above is safer because it raises outdated values without lowering a pod target that already declares a newer minimum. If a dependency needs a newer iOS version than Runner supports, resolve that mismatch by raising the app minimum or selecting a compatible dependency version—not by forcing the dependency’s target downward.
3. Alternatively, remove the pod-level override
The accepted solution for the original report removed each pod target’s explicit deployment setting:
post_install do |installer|
installer.pods_project.targets.each do |target|
flutter_additional_ios_build_settings(target)
target.build_configurations.each do |config|
config.build_settings.delete('IPHONEOS_DEPLOYMENT_TARGET')
end
end
end
This removes the target-level override and lets Xcode resolve the value from lower-precedence settings, such as project settings or defaults.
Use this instead of, not alongside, the explicit-minimum logic. It is useful when an unnecessary old override is the problem and the inherited value is appropriate.
Deleting a pod setting does not make that target inherit Runner’s setting: Runner is a separate target. Verify the resolved deployment target in Xcode afterward. If it remains unsupported, use the explicit-minimum approach and check the generated project’s configuration.
4. Check Flutter framework metadata when applicable
The highly voted workaround also updated MinimumOSVersion in ios/Flutter/AppFrameworkInfo.plist.
If that file exists in your project, inspect it for an outdated value. For a project whose Flutter framework minimum should be the illustrative iOS 13.0 minimum, the entry is:
<key>MinimumOSVersion</key>
<string>13.0</string>
Do not treat this as the primary fix for warnings naming targets in the Pods project. Framework metadata and pod build settings are different things. Updating this file alone will not remove an explicit 8.0 deployment target from a pod.
Do not create the file solely because an older workaround mentions it; Flutter project layouts and generated files can differ.
5. Reinstall pods and rebuild without deleting lockfiles
From the Flutter project root, run:
flutter pub get
cd ios
pod install
cd ..
flutter build ios
If you use Bundler to manage CocoaPods, run bundle exec pod install instead of pod install.
If stale build products remain a concern, clean and repeat:
flutter clean
flutter pub get
cd ios
pod install
cd ..
flutter build ios
Keep ios/Podfile.lock and pubspec.lock unless you deliberately intend to resolve different dependency versions. Deleting them is not necessary to apply a Podfile build-setting change and can introduce unrelated upgrades.
After rebuilding, check whether the named pod targets still produce the warning. If the warning is gone but the build fails, find the actual error in the build output. Signing failures, compiler errors, and dependency compatibility problems need their own fixes.
How to prevent it
- Keep Runner’s minimum and the Podfile platform declaration aligned.
- Store pod-target corrections in the Podfile rather than editing the generated Pods project.
- Preserve Flutter’s build-settings call and existing post-install customizations.
- Review plugin minimum requirements before upgrading dependencies.
- Commit lockfiles so local and CI builds resolve consistent dependency versions.
- Recheck deployment targets after changing Xcode or Flutter; old workaround version numbers are not permanent requirements.
FAQ
Why does the warning remain after I change Runner’s deployment target?
Each pod has its own build target and can specify its own IPHONEOS_DEPLOYMENT_TARGET. Changing Runner does not automatically replace those settings; inspect the target named in the warning and apply a persistent Podfile correction.
Should I set every pod to iOS 9.0?
No. That value addressed the older toolchain shown in the original report. Choose a minimum supported by your current toolchain and dependencies, and never lower a dependency’s declared requirement just to suppress a warning.
Do I need to delete Pods, the workspace, and both lockfiles?
Not as a first step. Run pod install after editing the Podfile, then clean build products if necessary. Preserve lockfiles to avoid unrelated dependency changes while diagnosing the deployment-target warning.
Parts of this guide are adapted from content licensed under CC BY-SA 4.0; this article is shared under the same license.
