OMG. I didn't know I could actually hit the delete key there. Worked perfect!
Gees..
Thank you so so much!!!!
Selecting any option will automatically load the page
Post
Replies
Boosts
Views
Activity
this just shouldn't happen. Apple has no solution?
Here is a quote from chatgpt re: this situation with owning the M! and OS 15.5 and xcode 16.3 and trying to program with cocoapods.
Yes — you’ve absolutely run into the classic CocoaPods + Apple + Ruby versioning spiral of doom. And you’re not alone. This is an extremely common pain point when:
You use macOS + M1/M2/M3 chips (Apple Silicon),
Apple ships a newer Xcode that isn’t supported by your CocoaPods version,
Ruby was installed via rbenv or brew, and
CocoaPods doesn't behave like a good citizen between those environments.
Topic:
Developer Tools & Services
SubTopic:
Xcode
Tags:
Here's a recap of the issue
Summary of Current Setup So Far (for your documentation):
Step Command Output / Result
A gem install cocoapods -v 1.14.3 ✅ Installed successfully
B which pod user/bob/.rbenv/shims/pod
C pod --version 1.14.3
D gem install xcodeproj --pre ✅ Installed xcodeproj-1.27.0
CONCLUSION:
This confirms:
Xcode 16.3 writes .xcodeproj files with object version 90
The latest xcodeproj gem (1.27.0) only supports up to object version 77
Therefore, CocoaPods will crash every time with modern Xcode, no matter which version of cocoapods you use
✅ Clear Answer
❌ You cannot use CocoaPods right now unless:
Xcodeproj is updated to support object version 90
→ You’d have to wait for CocoaPods to release a compatible version
Or you downgrade Xcode to something that supports .xcodeproj object version 77
→ But this means downgrading to Xcode 15.x or lower, which won’t run on macOS 15.5 Sequoia
→ So you’re stuck.
Topic:
Developer Tools & Services
SubTopic:
Xcode
Tags: