0

I updated to Xcode 6 a while ago, I had absolutely no errors on Xcode 5.1.1 Getting some weird and totally illogical errors when compiling in Xcode 6. I went through all of them but I seriously have no idea why these errors are appearing only on Xcode 6.

https://www.dropbox.com/s/z255siefabr8xtv/Screenshot%202014-10-04%2009.56.35.png https://www.dropbox.com/s/19hcoi4068semuo/Screenshot%202014-10-04%2009.56.50.png

All these errors are on the dependency Pods and their methods which I've used in my native code. None of these errors are occurring in my code except the external library methods which are being called inside my code

Anuj Rajput
  • 836
  • 9
  • 30
  • Did you try a `pod install` again? I am guessing that the header files are not being imported properly. See this thread - http://stackoverflow.com/questions/12002905/ios-build-fails-with-cocoapods-cannot-find-header-files/16703468#16703468 – raurora Oct 04 '14 at 06:38
  • Yes tried the `pod install` many times already. Nothing works – Anuj Rajput Oct 04 '14 at 07:47
  • Not sure, where exactly is wrong. Did you check the above link? Could be the header path. On SO, there are multiple threads addressing the same issue, but none of them have an upvoted answer. – raurora Oct 04 '14 at 18:53
  • None of the solutions worked for me. The one you suggested, I have only single target for my app so that doesn't work either – Anuj Rajput Oct 05 '14 at 09:33
  • If you can create a simplified version of your project, do you still get those errors on Xcode 6? I'll be happy to look at them if you can share the simplified version. – raurora Oct 05 '14 at 18:14
  • By simplified, you mean removing all the Pods? – Anuj Rajput Oct 07 '14 at 07:11
  • Not writing any of your code. Just installing Pods. – raurora Oct 07 '14 at 16:12
  • This is my [Podfile](https://dl.dropboxusercontent.com/u/42834001/Teamie/Podfile) iOS Deployment Target is 6.0 – Anuj Rajput Oct 08 '14 at 03:20
  • I created a new project and added this [Podfile](https://dl.dropboxusercontent.com/u/42834001/Teamie/Podfile) and built using Xcode 6. Still the same errors – Anuj Rajput Oct 08 '14 at 05:42

1 Answers1

0

Yes, those errors are all related to compatibility. On Terminal, inside your project directory - I did a rm -rf ~/.cocoapods followed by, sudo gem install cocoapods on the terminal.

And now, before we do pod install. You modify your PodFile. Instead of a version, you can specify the :head flag. This will use the pod’s latest version spec version, but force the download of the ‘bleeding edge’ version [Source]. A spec might not be compatible with the source material anymore.

ECSlidingViewController was one example. This is how your PodFile should look like -

source 'https://github.com/artsy/Specs.git'
source 'https://github.com/CocoaPods/Specs.git'

platform :ios, '6.0'
inhibit_all_warnings!

# Frameworks
pod 'RestKit', :head

# UI
pod 'FlatUIKit', :head
pod 'SVProgressHUD', :head
pod 'SDWebImage', :head
pod 'MKNumberBadgeView', :head
pod 'TDBadgedCell', :head
pod 'EMAccordionTableViewController', :head

# Controls
pod 'TSMessages', :head
pod 'ECSlidingViewController', '0.10.0'
pod 'SVPullToRefresh', :head
pod 'WEPopover', :head
pod 'SVWebViewController', :head
pod 'EGOPhotoViewer', :head
pod 'DACircularProgress', :head

# Tools
pod 'FontAwesomeIconFactory', :head
pod 'KeychainItemWrapper', :head
pod 'DAKeyboardControl', :head
pod 'ARAnalytics/GoogleAnalytics', :head
pod 'Instabug', :head

# Categories
pod 'NSData+Base64', :head
raurora
  • 3,623
  • 1
  • 22
  • 29
  • You might get one error with WEPopover. The fix is very simple, I raised an issue here - https://github.com/werner77/WEPopover/issues/57 – raurora Oct 08 '14 at 08:44
  • I tried this method. I don't get any errors with it. But I'm using a specific versions of specs purposely. I am not willing to update to the newer specs right now as some of them would require architecture change and would have to change a lot of code in my app. The errors still exist :( – Anuj Rajput Oct 09 '14 at 05:38
  • I doubt its a good idea to continue maintaining older versions. You can start a bounty on the question if it remains unanswered. I tried my best :) – raurora Oct 09 '14 at 06:13