pod install cannot pick a version of a pod that satisfies every requirement
[!] CocoaPods could not find compatible versions for pod "FirebaseAuth":Short answer
CocoaPods tried every version of the named pod and none fit all requirements. The sentence at the end of the error says why: a higher minimum deployment target, no spec found, or two pods wanting different versions. Read that sentence, then raise the Podfile platform, refresh the spec sources, or loosen and update the conflicting pins.
Fix it fast
1Find out which cause you have
Run the install by hand from the ios folder so the whole message is visible, and read the sentence under the In Podfile tree. Flutter hides it behind a generic Error running pod install.
flutter pub get cd ios && pod install2Match what you see, then jump to its fix
- 1
Specs satisfying the … dependency were found, but they required a higher minimum deployment target.A pod needs a higher iOS deployment target than your Podfile platformFix - 2
None of your spec sources contain a spec satisfying the dependency, followed by the list You have either … out-of-date source repos … mistyped the name or versionNo spec matches: the version does not exist, the name is mistyped or the sources are staleFix - 3
The In Podfile tree shows the same pod twice, once from your own line and once as a dependency of another pod, with ranges that do not overlapTwo requirements for the same pod cannot both be satisfiedFix - 4
You have changed the constraints of dependency `X` inside your development pod `some_plugin`. You should run `pod update X` to apply changes you've made.A development pod (such as a Flutter plugin) changed its dependencies and Podfile.lock still holds the old onesFix
- 1
What does the error look like?
[!] CocoaPods could not find compatible versions for pod "FirebaseAuth":Specs satisfying the `FirebaseAuth (~> 11.0)` dependency were found, but they required a higher minimum deployment target.None of your spec sources contain a spec satisfying the dependency: `FirebaseAuth (~> 99.0)`.You should run `pod update NAME` to apply changes you've made.
Cause 1 of 4
A pod needs a higher iOS deployment target than your Podfile platform
1Check
Every podspec declares the lowest iOS it supports, and CocoaPods only considers versions that fit the platform line in your Podfile. When all versions that match your constraint need a newer iOS, none are left. Look at your platform line and at what the pod asks for. I reproduced this by asking for FirebaseAuth 11 with platform :ios, '11.0'.
grep -n "platform :ios" ios/Podfile
pod spec cat FirebaseAuth --version=11.15.0 | grep -A2 '"platforms"' # replace with your pod and version2Fix
Set the platform line to at least the iOS version the pod declares. In a Flutter Podfile the line is commented out by default; uncomment it and set the number. If your app must keep supporting an older iOS, pin the pod to an older version that still supports it instead.
# ios/Podfile
platform :ios, '15.0'
# or keep the old iOS and pin an older pod release
pod 'FirebaseAuth', '~> 10.29'3Verify
pod install resolves and finishes, and the app still builds for your lowest supported iOS.
cd ios && pod install
cd .. && flutter build ios --no-codesignConfirmed by github.com
Cause 2 of 4
No spec matches: the version does not exist, the name is mistyped or the sources are stale
1Check
CocoaPods says three possible reasons itself: out-of-date source repos, a mistyped name or version, or a source repo that is not in the Podfile. List the versions the sources have for that pod and compare them with your requirement.
pod spec which FirebaseAuth --show-all # replace with your pod; lists every version found
grep -n "pod 'FirebaseAuth'\|^source" ios/Podfile2Fix
Correct the name or the version requirement. If the version exists upstream but is missing locally, refresh the sources as part of the install, which runs pod repo update first. If the pod lives in a private or non-default repository, add its source line to the Podfile.
cd ios && pod install --repo-update3Verify
The install finds a spec and writes Podfile.lock.
cd ios && pod install
grep -n "FirebaseAuth" Podfile.lock | head -3Confirmed by guides.cocoapods.org
Cause 3 of 4
Two requirements for the same pod cannot both be satisfied
1Check
When your Podfile pins a pod (for example ~> 10.0) and another pod you use depends on a newer major version of it (~> 11.0), no version satisfies both. The tree in the message lists who asked for what. On 1.17.0 my reproduction ended with the deployment-target sentence even though the real conflict was the two ranges, so read the tree and not only the last line.
cd ios && pod install 2>&1 | head -20
grep -n "pod " Podfile2Fix
Remove or loosen your own pin so the dependent pod can choose, or move the pod that needs the old range to a version that supports the new one. In a Flutter app that usually means upgrading the plugin that pulls the conflicting pod.
flutter pub outdated
flutter pub upgrade some_plugin
cd ios && pod install3Verify
pod install finishes and Podfile.lock lists one version of the pod.
cd ios && pod install
grep -n "FirebaseCore" Podfile.lock | head -3Confirmed by guides.cocoapods.org
Cause 4 of 4
A development pod (such as a Flutter plugin) changed its dependencies and Podfile.lock still holds the old ones
1Check
Pods that come from a local path, which includes Flutter plugins linked through ios/.symlinks, can change their own dependency lines when you upgrade the plugin. Podfile.lock still records the earlier result, and plain pod install keeps locked versions. CocoaPods names the pod to update in the message.
cd ios && pod install 2>&1 | grep -B2 -A3 "pod update"
git diff --stat Podfile.lock2Fix
Update only the pod the message names, so the rest of the lockfile stays as it was. Run it from the ios folder after pub get.
flutter pub get
cd ios && pod update X # replace X with the pod name in the message3Verify
Podfile.lock shows the new version and a normal pod install runs cleanly.
cd ios && pod install
git diff Podfile.lock | head -20Confirmed by guides.cocoapods.org
How do I stop it coming back?
- Keep Podfile.lock in version control, and update pods on purpose with pod update NAME, not by deleting the file.
- Do not pin pods that a plugin already pulls in; let the plugin's range decide.
- After a Flutter or plugin upgrade, run flutter pub get and pod install in the ios folder and read the full message there.
- Raise the Podfile platform line and the app's deployment target together when a dependency drops an old iOS.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Every cause above names the document that confirms it. I have not reproduced this fix on a machine of my own yet, so read it as documented guidance, not a test report. Found a mistake? Tell me.
Which stack is behind this page?
Projects of mine built on the same technologies:
- TaxiDexMy own multi-tenant taxi dispatch SaaS: API, dispatcher portal, driver and passenger apps, and the servers underneath.
- Dispatch ProA real-time logistics platform: Flutter apps, Spring Boot services and a Kafka event pipeline on AWS.
- Qist BazaarA buy-now-pay-later marketplace built from a blank repo, now past 100K downloads on Google Play.
Related fixes
Mobile apps
Xcode says a script phase failed, but not which one or why
error: The sandbox is not in sync with the Podfile.lock. Run 'pod install' or update your CocoaPods installation.
This line only reports that one Run Script build phase exited with an error.
4 causes, each with a fixMobile apps
Swift cannot import a module that is installed in the project
No such module 'Flutter'
The compiler for this target cannot see the module, even though the code exists on disk.
4 causes, each with a fixMobile apps
Apple rejected the app under Guideline 4.3, Design: Spam
Guideline 4.3(b) - Design - Spam
Guideline 4.3 is Apple's duplicate rule.
5 causes, each with a fixMobile apps
flutter run says: Could not run Runner.app, try Xcode Product > Run
Try launching Xcode and selecting "Product > Run" to fix the problem:
Flutter prints this when installing or launching the built app on the iPhone fails, and it hides the real reason.
4 causes, each with a fixMobile apps
flutter doctor says CocoaPods is installed but not working
You appear to have CocoaPods installed but it is not working.
Flutter runs pod --version and treats a failed or unreadable result as a broken install.
3 causes, each with a fixMobile apps
flutter run on iOS or macOS stops with Error running pod install
Warning: CocoaPods not installed. Skipping pod install.
Flutter only reports that pod install failed; the reason is in the lines just above it.
5 causes, each with a fix