pod install fails on a project saved by a newer Xcode
Your error
[Xcodeproj] Unable to find compatibility version string for object version `70`.2 more lines it can showFix it fast
Most common cause, 1 of 3CocoaPods is older than the Xcode that saved the project
Update CocoaPods with the same tool you installed it with.
gem install cocoapods
# macOS system Ruby needs sudo: sudo gem install cocoapods
pod --version
pod installShort answer
Each Xcode release can save .xcodeproj files with a new objectVersion number, and the Xcodeproj gem inside CocoaPods refuses numbers it does not know. Xcode 16 writes 70 or 77; Xcode 26.3 writes 100. Update CocoaPods (1.16.0 added Xcode 16 support, 1.17.0 added Xcode 26.3), and if the project uses a Gemfile, update it there and run pod through bundle exec.
Which cause do you have?
Compare the object version stored in the project file with the CocoaPods version that actually runs.
grep -m1 objectVersion ios/Runner.xcodeproj/project.pbxproj 2>/dev/null || grep -m1 objectVersion *.xcodeproj/project.pbxproj
pod --version
bundle exec pod --version 2>/dev/nullThen find the line you see in this list and open its fix:
- 1CocoaPods is older than the Xcode that saved the project
objectVersion is 70 or 77 and pod --version prints 1.15.x or lower, or objectVersion is 100 with 1.16.x - 2A Gemfile pins the old CocoaPods
pod --version is new, but bundle exec pod --version is old, and the project has a Gemfile.lock (React Native and many fastlane setups do) - 3An old pod binary comes first on PATH
You updated the gem, yet pod --version still prints the old number
What does the error look like?
[Xcodeproj] Unable to find compatibility version string for object version `70`.[Xcodeproj] Unable to find compatibility version string for object version `77`.[Xcodeproj] Unable to find compatibility version string for object version `100`.
Cause 1 of 3
CocoaPods is older than the Xcode that saved the project
You seeobjectVersion is 70 or 77 and pod --version prints 1.15.x or lower, or objectVersion is 100 with 1.16.x
Check
Xcodeproj keeps a table that maps each object version to an Xcode release and raises this ArgumentError for any number missing from it. Its changelog adds Xcode 16 support in 1.26.0 (required by CocoaPods 1.16.0) and the Xcode 26.3 object version in 1.28.0 (CocoaPods 1.17.0).
gem list xcodeproj cocoapodsFix
Update CocoaPods with the same tool you installed it with. Homebrew users run brew upgrade cocoapods instead.
gem install cocoapods
# macOS system Ruby needs sudo: sudo gem install cocoapods
pod --version
pod installVerify
pod install completes and writes Pods/Pods.xcodeproj without the ArgumentError.
pod installConfirmed by raw.githubusercontent.com
Cause 2 of 3
A Gemfile pins the old CocoaPods
You seepod --version is new, but bundle exec pod --version is old, and the project has a Gemfile.lock (React Native and many fastlane setups do)
Check
With Bundler, the version in Gemfile.lock wins whenever pod runs through bundle exec, which scripts and CI usually do. Updating the global gem does not touch the lock file.
grep -nE "cocoapods|xcodeproj" Gemfile Gemfile.lockFix
Update the two gems inside the bundle, commit the new Gemfile.lock, and keep calling pod through bundle exec. Loosen the version range in Gemfile first if it caps cocoapods below 1.16.
# Gemfile
gem 'cocoapods', '>= 1.17'
bundle update cocoapods xcodeproj
bundle exec pod installVerify
bundle exec pod --version prints the new version and the install passes.
bundle exec pod --version && bundle exec pod installConfirmed by guides.cocoapods.org
Cause 3 of 3
An old pod binary comes first on PATH
You seeYou updated the gem, yet pod --version still prints the old number
Check
A Homebrew copy, a system Ruby copy and a version-manager copy can all exist. The one first on PATH is the one that runs.
which -a pod
gem env | grep -E "INSTALLATION|EXECUTABLE"Fix
Remove the copies you do not use, or call the intended one by its full path, then open a new terminal.
brew uninstall cocoapods # if you moved to the gem
# or
gem uninstall cocoapods # if you prefer Homebrew
hash -r && pod --versionVerify
which -a pod lists a single pod, and its version is the new one.
which -a pod && pod --versionConfirmed by guides.cocoapods.org
How do I stop it coming back?
- Update CocoaPods in the same week you install a new major Xcode.
- Keep one install method for CocoaPods per machine and per CI image.
- Commit Gemfile.lock so every developer and CI job runs the same pod version.
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.