3 ms·

+1 for mentioning the "Clean Build Folder" issue. I was stuck on that for about an hour yesterday, then I found this post: http://stackoverflow.com/questions/3

+1 for mentioning the "Clean Build Folder" issue. I was stuck on that for about an hour yesterday, then I found this post: http://stackoverflow.com/questions/32586144/upgraded-to-swift-2-and-cocoapods-38-2-now-getting-build-error-command-bin-s http://stackoverflow.com/questions/32586144/upgraded-to-swif... I didn't know about using the Alt key to reveal "Clean Build Folder", and I've been doing iOS dev for years. I'll add this to the list of unhelpful compile errors that are fixed by cleaning the build.

w4 11y ago
"Clean Build Folder" is basically the "turn it off, then turn it back on" of Xcode. Almost anytime you get a weird compiler error on a project that compiled fine moments ago, it's solved by "Clean Build Folder." Definitely a good trick to know.
- dv_says 11y ago
  Or for those who prefer automating, add this to ~/.bash_profile: alias nuke="rm -rf ~/Library/Developer/Xcode/DerivedData/"
  - seivan 11y ago
    I always advice people to put their DerivedData and build folder somewhere accessible. You can change it settings, don't use the default setting.
    - wingerlang 11y ago
      Good tip. As someone with quite a small main HDD I'll do this ASAP.
  - vitd 11y ago
    That's pretty drastic. That nukes the derived data folder of all your Xcode projects. If you work on more than 1, using this to solve a problem in 1 will lead to needing to rebuild all of your projects. That seems a bit extreme for an issue in a single project.
div 11y ago
cmd+shift+k followed by cmd+alt+shift+k is a multiple-times-a-day incantation for me :)