cocoapods

so I used Venmo/Synx on my Xcode project with CocoaPods, and it completely screwed everything up. I was able to fix the Manifest.lock and Podfile.lock errors, but now I am getting this error: The file “Pods.debug.xcconfig” couldn’t be opened because there is no such file. (/Users/user/GitHub/xxxxxx/Pods/Pods/Target Support Files/Pods/Pods.debug.xcconfig) As you can see, the path is incorrect, as there is no Pods/Pods directory (there is one extra pod). How can I fix this? I have only added PODS_ROOT to the user-defined variable, as that fixed my Podfile and Manifest.lock files. Any help would

CocoaPods的简介 当你开发iOS应用时，会经常使用到很多第三方开源类库，比如JSONKit，AFNetWorking等等。如果使 用他们，传统的方法是，在git上把他们下载下来，然后去配置。这个工作很繁琐，而且也容易出错。不 过有了Cocoapods你就会从这些繁琐的工作中解脱出来。 CocoaPods的安装及使用 第一步：安装RVM RVM: Ruby Version Manager.中文为Ruby版本管理器，包括Ruby的版本管理和Gem库管理。 $ curl -L get.rvm.io | bash -s stable //需要等一会 $ source ~/.bashrc $ source ~/.bash_profile 等待终端加载完毕，后输入 rvm -v 如图所示： 如上图所示，能显示版本号，即是安装成功了。 第二步：升级Ruby的版本 CocoaPods目前安装需要Ruby的版本大于2.2.2,不然会报错：Error installing pods: activesupport requires Ruby version >= 2.2.2。目前Mac系统默认自带是2.0，所以需要升级。 查看当前ruby版本 ruby -v 获取rvm列表，列表里会显示最新版Ruby版本 rvm list known 如下图所示： 选择安装最新版Ruby 根据rvm列表里#

After upgrading to macOS High Sierra CocoaPods is not working. While it is tempting to move away from CocoaPods, it's unfortunately not in scope right now. The error message is below. zsh: /Users/****/.gems/bin/pod: bad interpreter: /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/bin: no such file or directory I realize that the error stems from Ruby being upgraded but what is the easies fix? Trying to make CocoaPods use the new ruby version yields other errors. Edit: For now i installed Ruby 2.0 with rvm install 2.0.0 and rvm use 2.0.0 and then reinstalled CocoaPods sudo gem

I have had the bellow error for some time now. I have tried creating new projects fixing the problem within the project Resetting all cocoa pods and more And yet I have still not been able to get rid of this error. Error below: /Users/myUsername/Desktop/MapboxMap117/Pods/Target Support Files/Pods-MapboxMap117/Pods-MapboxMap117-frameworks.sh: line 114: local: `/Users/myUsername/Desktop/MapboxMap117/Pods/Mapbox-iOS-SDK/dynamic/826E141E-8875-3C3B-A106-2B772F8A0684.bcsymbolmap': not a valid identifier Command PhaseScriptExecution failed with a nonzero exit code I am also getting : (dont know if it

Using iOS-8.3, Xcode-6.3.1 and MacOS-10.10.3 - The CocoaPods (v0.37.1) installation of the RealmSwift (v0.92.3) described here and here basically works, except the WatchKit Extension does not find any Realm keywords. My Podfile looks as follows: xcodeproj 'MyApp.xcodeproj' workspace 'MyApp.xcworkspace' platform :ios, '8.3' source 'https://github.com/artsy/Specs.git' source 'https://github.com/CocoaPods/Specs.git' use_frameworks! def shared_pods pod 'RealmSwift', '>= 0.92.3' end target 'MyApp' do shared_pods end target 'MyAppTests' do shared_pods end target 'MyApp WatchKit Extension' do shared

While trying to install cocoapods I'm getting the following error, can any one help me debug it? MacBook-Pro:~ saiteja$ sudo gem install cocoapods Password: ERROR: Error installing cocoapods: activesupport requires Ruby version >= 2.2.2. MacBook-Pro:~ saiteja$ sudo gem install activesupport -v 4.2.6 First install an old version of 'activesupport' (which is both compatible with ruby 2.0 and with cocoapods) and then install cocoapods. $ sudo gem install activesupport -v 4.2.6 This was issue exactly faced by me. First you need install active script : sudo gem install activesupport -v 4.2.6 sudo

有时候我们需要为一个App生成不同环境下的版本，比如Debug版本，Appstore版本，Adhoc版本，之前见到别人都是用多个Target，但其实不用多个Target也行，这个替代方案就是多个Configurations。 如果你是用Xcode5之前的版本，可能参考这两篇文章就行： 如何在一个设备上安装一个App的两个不同版本 iOS开发之同一应用设置不同图标和名称 - 曾静的技术博客 但如果使用的是Xcode5之后的版本，特别是使用了Images.xcasset来设置应用图标，那么配置多环境可能就不那么容易了，还好找到了这篇教程： iOS multi-environment configuration | Blog | AppFoundry 搞定了上面的设置，但是并没有完。如果你的项目使用了Podfile，pod install或者pod update时可能会有下面的提示： 今天在使用pod install的时候，出现了 [!] CocoaPods did not set the base configuration of your project because your project already has a custom config set. In order for CocoaPods integration to work at all, please