pod init or pod install fails with 'Unknown ISA PBXFileSystemSynchronizedRootGroup'
Unknown ISA PBXFileSystemSynchronizedRootGroupShort answer
Xcode 16 stores your folders as synchronized root groups. CocoaPods reads the project through the xcodeproj gem, and versions before 1.26.0 do not know that group type. Update CocoaPods, and if you use Bundler, update the pinned gem in your Gemfile.lock, so that xcodeproj 1.26.0 or newer loads.
Fix it fast
1Find out which cause you have
See which CocoaPods and xcodeproj versions the pod command really uses.
pod --version gem list xcodeproj2Match what you see, then jump to its fix
- 1
Unknown ISA PBXFileSystemSynchronizedRootGroup right after pod init or pod install on a project saved by Xcode 16.CocoaPods or xcodeproj is older than the Xcode 16 releaseFix - 2
gem list shows a new version, but bundle exec pod --version shows an old one.Bundler keeps an old CocoaPods locked in Gemfile.lockFix - 3
The error comes back after you moved to a newer Xcode, with CocoaPods you had updated before.A newer Xcode wrote a project format that your xcodeproj does not knowFix
- 1
What does the error look like?
Unknown ISA PBXFileSystemSynchronizedRootGroup
Cause 1 of 3
CocoaPods or xcodeproj is older than the Xcode 16 release
1Check
The xcodeproj changelog says support for file system synchronized groups introduced in Xcode 16 arrived in 1.26.0. CocoaPods 1.16.0 raised its minimum xcodeproj to that version. Anything older fails on these projects.
pod --version
gem list xcodeproj2Fix
Install a current CocoaPods. It pulls in a new enough xcodeproj.
gem install cocoapods
pod --version3Verify
pod version is 1.16.0 or newer, and the command no longer raises the error.
pod installConfirmed by github.com
Cause 2 of 3
Bundler keeps an old CocoaPods locked in Gemfile.lock
1Check
Inside a project with a Gemfile, bundle exec uses the versions written in Gemfile.lock, not the newest installed.
bundle exec pod --version2Fix
Update the locked gem, then run the install through Bundler.
bundle update cocoapods
bundle exec pod install3Verify
bundle exec pod --version prints 1.16.0 or newer.
bundle exec pod --versionConfirmed by github.com
Cause 3 of 3
A newer Xcode wrote a project format that your xcodeproj does not know
1Check
The xcodeproj changelog for 1.28.0 lists an objectVersion added for Xcode 26.3, and CocoaPods 1.17.0 raised its minimum xcodeproj to 1.28.0.
gem list xcodeproj2Fix
Move to CocoaPods 1.17.0 or newer.
gem install cocoapods
pod --version3Verify
gem list xcodeproj shows 1.28.0 or newer, and pod install works.
gem list xcodeproj
pod installConfirmed by github.com
How do I stop it coming back?
- Pin cocoapods in the Gemfile and run bundle update cocoapods when you adopt a new Xcode major version.
- Check the CocoaPods changelog before moving a team or CI image to a new Xcode.
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?
Related fixes
Mobile apps
Running pod on a React Native project fails with can't find gem cocoapods
can't find gem cocoapods (>= 0.a) with executable pod
The pod command exists, but the Ruby that is running it has no CocoaPods gem.
3 causes, each with a fixMobile apps
Cannot change the App Privacy answers in App Store Connect
Publish Your App Privacy Responses?
Only the Account Holder, Admin and App Manager roles can answer the App Privacy questions.
2 causes, each with a fixMobile apps
App record creation fails because you lack permission
You cannot add a new app in App Store Connect as a Developer or limited user
Only the Account Holder, an Admin or an App Manager can create an app record, and Apple blocks it until the Account Holder has signed the latest agreement.
3 causes, each with a fixMobile apps
You cannot find the button to pull your app back from review
No 'remove this version from review' message appears on the version page
There is no button called Reject Binary.
3 causes, each with a fixMobile apps
Your Apple Account cannot sign in to App Store Connect
Sign-in to App Store Connect is refused for an account that should have access
App Store Connect does not open to every Apple Account.
3 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 fix