Why this happens
When you run pod install in a Flutter iOS project, CocoaPods resolves dependencies for all plugins. Firebase pods such as Firebase/Core, FirebaseAnalytics, GoogleUtilities, and gRPC-Core each declare a minimum iOS version in their podspecs. If your Podfile still has the default platform :ios, '9.0' (or an older version), CocoaPods finds podspecs that satisfy the version constraints but refuse to install because they demand a newer deployment target. The resolver then aborts with the message:
Specs satisfying the `Firebase/Core` dependency were found, but they required a higher minimum deployment target.
This mismatch is common after upgrading Flutter, adding new Firebase plugins, or switching to a newer Xcode SDK that drops support for older iOS versions.
How to fix it
1. Find the highest required iOS version in local podspecs (most reliable)
- Open Terminal and navigate to your Flutter project root.
- Inspect the generated local podspecs:
bash
grep -r "ios.*\"" ios/Pods/Local\ Podspecs/*.json | head -20
Look for lines like"ios": "10.0"or"ios": "11.0". Note the highest number. - Open
ios/Podfilein your editor. - Locate the commented line
# platform :ios, '9.0'. - Uncomment it and replace the version with the highest one you found (e.g.,
10.0):
ruby
platform :ios, '10.0' - Save the file and run:
bash
cd ios && pod install
2. Quick alternative: bump to a modern baseline
If you don’t want to grep the podspecs, set a safe modern minimum that covers current Firebase releases:
platform :ios, '12.0'
iOS 12 is the oldest version still supported by Firebase SDKs as of 2024. This avoids the grep step and future-proofs the project for a while.
3. Clean and reinstall if the lockfile is stale
Sometimes Podfile.lock caches an old resolution. After updating the platform version:
cd ios
rm -f Podfile.lock
rm -rf Pods
pod install
This forces a fresh resolution against the new deployment target.
4. Verify Flutter plugin podspecs are up to date
Run flutter pub upgrade to pull the latest plugin versions, then repeat pod install. Newer plugin releases often relax or update their iOS version requirements.
How to prevent it
- Keep the
platform :iosline uncommented inios/Podfileand set it explicitly (don’t rely on the default). - After any
flutter pub addorflutter pub upgradethat touches Firebase or Google plugins, re-check the deployment target. - Add a CI step that runs
cd ios && pod install --repo-updateon every merge to catch version drift early. - Pin the CocoaPods version in your CI (
gem install cocoapods -v 1.15.2) so the resolver behaves consistently.
FAQ
Why does pod update alone not fix it?
pod update only upgrades pod versions within the constraints of the current deployment target. If the target itself is too low, the resolver never considers newer pod versions that require a higher iOS version, so the conflict persists.
Can I keep the deployment target low and use older Firebase pods?
Technically yes, but you would have to lock every Firebase dependency to an old version that still supports iOS 9. This blocks security updates, new features, and eventually breaks App Store submission when Apple raises the minimum SDK requirement.
What if the error mentions gRPC-Core or GoogleUtilities instead of Firebase/Core?
The root cause is identical: a transitive dependency demands a newer iOS version. Raising the platform :ios value in the Podfile resolves all of them at once because it lifts the floor for the entire dependency graph.
Parts of this guide are adapted from content licensed under CC BY-SA 4.0; this article is shared under the same license.
