everybody, did you happen to encounter such an error while running the pod install command?
Link to the error itself
Since I tried to reinstall ruby by this method already:
rvm install ruby-2.6.3
rvm use ruby-2.6.3
rvm --default use 2.6.3
And still, unsuccessfully.
and cocoapods are also unsuccessful anyway, there is simply no place to look for an answer.
This error flies away only when working with an Obj-c project (and quite ancient ones), because I am now looking at the cryptoPro library and the standard project is not launched there.
There are no such problems with new projects at the moment.
Fixed an error. I will tell you what it was about me. I noticed this line in the bug:
untimeError - [Xcodeproj] Consistency issue: build setting ARCHS has multiple values: {"Debug"=>"$(ARCHS_UNIVERSAL_IPHONE_OS)", "Release"=>"$(ARCHS_STANDARD_32_BIT)"}.
After that I got into the Targets -> Build Settings -> Architectures project itself.
Specify there $(ARCHS_STANDARD) for both cases and then everything worked!
Related
I have several versions of Ruby installed via RVM. I have been using Ruby 2.5.0 for a while, but also working on projects at 2.3.3. Every time I open the terminal or a new tab, it switches to version 2.3.3. I have set the default to 2.5.0, but it doesn't respect this.
I finally pushed my last commit that needed 2.3.3 so I thought I could just nuke it and maybe that would fix my problem. One the one hand, it now correctly defaults to 2.5.0, but always with the error:
Required ruby-2.3.3 is not installed.
What does it take to make RVM switch to the default and stay there? Why would it be hung up on this specific version?
I had the same problem and it drove me nearly crazy. All symlinks and config files under /usr/local/rvm/config where pointing to 2.5.3, as I set it up to, but I got the same message as you. Turned out there was a .ruby-version file in the project directory that overrode all settings. Updating this file to the correct version did it for me. Hope it helps you too.
Today I've updated to Xcode 6.2/iOS SDK 8.2 and I've updated my project's Parse framework to 1.6.4 simultaneously. Now, I'm getting this error:
Definition of 'PFInstallation' must be imported from module 'Parse.PFInstallation' before it is required.
and
Definition of 'PFFile' must be imported from module 'Parse.PFFile' before it is required.
Both manifest as errors, not warnings, though interestingly my app builds.
I think modules are a Swift thing, though I'm on Objective-C and my project has nothing to do with Swift. What should I do?
UPDATE: Cleaning the build folder and restarting Xcode and rebuilding got me rid of the installation one, though file error is still here.
Congratulations!
You've found (yet another) bug in Xcode.
File it on bugreporter.apple.com
Cause it's still there one major release later in xcode 7.2.1
and I have to rm -rf ~/Library/Developer/Xcode/DerivedData all the time
to have the project build and run
(I do have swift content in the outer framework of mine though)
UPD 2016.02.18 this either seems fixed in 7.3 beta 3 OR I have strategically killed an #import somewhere which took care of this. Do not hesitate to share YOUR experience in the comments and/or answers ;-)
Try to import the file with framework reference like this:
#import <Parse/PFInstallation.h>
It seems that in cmd-line builds, Pods don't get built automatically. Even when invoking xcodebuild to reference the workspace that declares how projects link to each other.
Is there a way to fix this, besides manually opening the project in Xcode and building?
I don't have any problem with such configuration: CocoaPods 0.28.0 and Xcode5 (+ Command-Line Tools) here and building using the Command-Line quite often (especially for Continuous Integration) without having any problem.
Neither with the Apple's xcodebuild command, nor with xctool (see also this NSHipster's article) when building my personnal project using Travis-CI either, everything works fine;
At work we have plenty of Xcode workspaces created using CocoaPods / pod install and we use Jenkins-CI to run xcodebuild to build them and no problem either.
Maybe you need to check a bit more about your configuration? Which CocoaPods & Xcode version, Which Command-Line Tools (xcode-select --print-path?), How is you Xcode configured (maybe you changed some of Xcode's default settings that broke it somehow)?
Tell us more about your specific configuration and the error/warning messages you got, because there should not be any problem.
Also make sure you have an up-to-date version of CocoaPods (some stuff were fixed some versions ago regarding Xcode5 and the new arm64 architecture, that broke implicit dependency detection in some cases)
I have been using the YouTube v2 APIs for a little while and now have finally gotten around to setting up v3. So I have downloaded their frameworks/libraries from here:
svn checkout http://google-api-objectivec-client.googlecode.com/svn/trunk/ google-api-objectivec-client-read-only
And looked closely at the instructions they give for adding it to your project here:
http://code.google.com/p/google-api-objectivec-client/wiki/BuildingTheLibrary
For the life of me I cannot get my app to compile with some sort of problem. Its either and ARC problem, can't find header files or all sorts of other errors.
Hoping someone can come along who has it working and simply put some 1 2 3 steps as it would make a lot peoples lives easier as I am sure the Google APIs of all varieties are pretty relevant to a lot of people and will continue to be, thanks.
I had the same problem recently. The quickest way I could find to get the new client library up and running quickly was to install with this CocoaPod project, called iOS-GTLYouTube.
CocoaPods is a really simple way to install libraries. If that's new to you, you can check out the instructions at cocoapods.org.
Install Cocoapods if you don't have it, using your system ruby:
$ sudo gem install cocoapods
Create a Podfile located within your project with the following:
platform :ios, '7.0'
pod 'iOS-GTLYouTube'
In your project directory, using the system ruby:
$ pod install
I installed jRuby to try it in a new project, but I didn't think it would affect my entire Ruby installation.
Now when I try to start an old project, I get an error
/usr/bin/env jruby: no such file or directory
I've tried searching for how to remove jruby, but don't come up with anything. is there a nice way to get my rails apps working again with regular ruby?
I REALLY hope so.
Looks like it created symlinks; point them back at at the Ruby you want to use.
Use something like rvm to avoid this. (Or rbenv if you prefer.)
Rerun "bundle install" -- if you ran bundle install under jruby, the shebang for your scripts in the /bin folder was likely changed to reference jruby. By re-running bundle install under MRI, bundler will fix the shebangs for you.