-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RuntimeError - [Xcodeproj] Unknown object version. #10984
Comments
|
you are on a very old version of cocoapods. please update to latest version and also |
|
Ya - I tried that... and this is what I get... Davids-MacBook-Pro:Burgardts punky$ gem update xcodeproj And this is after I completely removed pods and reinstalled |
|
you will need to update cocoapods gem too. |
|
its possible the latest version of xcodeproj gem doesnt work with 1.5.0 so you are maxing out what version of xcodproj you can use with 1.5.0 of cocoapods. |
|
Ok. So this is what I did... gem list --local ! grep cocoapods Now I do The output is : However... So I guess a better question is ... how do I install 1.11.2 ? |
|
Ok - so an even better question... *** LOCAL GEMS *** *** LOCAL GEMS *** but pod --version responds with I hace no idea how this is happening and am a little loss now for words... Clearly there are conflicting versions or something going on. |
|
I think you installed it but somehow your environment is not using it. If you want to somehow force it then use https://bundler.io/ with a |
|
Well - I noticed in the environment - there was a POD file sitting in Once I removed that file.. pod --version stopped working... which is good... means it's no where to be found ... that seems to be where the conflicting version was. So ya - your hint that the environment was not using the correct version was accurate. rbenv: pod: command not found I did try out bundler - but it was giving me errors. |
|
Yeah I am not entirely sure. Sorry. It seems that things were working out once you got the latest version installed. |
|
Actually... it's still not working... I an still getting However. the Cocoapods GUI is doing something... looks like it is running the pods setup command (which I was not able to do within terminal since pods could not be found)... so I am just letting this all run its course. I'll be back.... |
|
Using Homebrew I removed RUBY and and the ruby environment and rebooted the computer. Well the GUI fixed up the command line installation... but it was still showing 1.5.0 with pod --version. HOWEVER, the gui reported that a newer version was available and to do a gem install cocoapods. I did that - it failed on permissions so I did sudo. Of course I said yes. At the end... I did pod --version and was told Eureka... We are getting close. and no Error and the pod file was created. So. I left this message here so people could see the pain and maybe pickup some hints if they are having the same issues as I had. |
This worked for me. I had old cocoapods version |
Nothing to update, but reinstall cocoapods solved my problem. |
Building native extensions. This could take a while... this is what i get after gem update cocoapods |
|
@PunkStarStudios this answer helped me https://stackoverflow.com/questions/39481636/updating-to-latest-version-of-cocoapods You have to install cocoapods again and very importantly link the updated version with |
Report
What did you do?
pod init
What did you expect to happen?
Initialize podfile etc.
What happened instead?
An error occurred
Error
CocoaPods : 1.5.0
Ruby : ruby 2.4.1p111 (2017-03-22 revision 58053) [x86_64-darwin16]
RubyGems : 2.7.6
Host : macOS 11.6 (20G165)
Xcode : 13.0 (13A233)
Git : git version 2.24.1
Ruby lib dir : /Users/punky/.rbenv/versions/2.4.1/lib
Repositories : master - https://github.com/CocoaPods/Specs.git @ 5f0e69d664cb8452ef4c0b6ae0ea95ce6d46fc61
Executable Path: /Users/punky/.rbenv/versions/2.4.1/bin/pod
cocoapods-deintegrate : 1.0.2
cocoapods-plugins : 1.0.0
cocoapods-search : 1.0.0
cocoapods-stats : 1.0.0
cocoapods-trunk : 1.3.0
cocoapods-try : 1.1.0
The text was updated successfully, but these errors were encountered: