You come at a certain point in the development of every app that what you see in the simulator does not match what you think should happen. Mostly these are human errors -- or at least they are in most of my cases ;-) -- but sometimes Xcode has just 'lost track', or so it seems. I've learnt that the Clean
(Shift+Cmd+K) and Clean Build Folder…
(Option+Shift+Command+K) menu options can show the difference between your error or Xcode's.
My question though is:
What does the
Clean
command do or not do, which leaves a reason forClean Build Folder…
to exist? When should I pick one over the other, why not just always clean the whole folder?
Clean the Build Folder This will delete all of the products and intermediate files in the build folder. To clean the build folder you can use the shortcut Command+Option+Shift+K or Menu Bar → Product → Hold Option Key → Clean build Folder .
If you select Clean from the Product menu, XCode will delete the files inside every folder in the Build folder, if you select Clean Build Folder it will delete the entire Build folder.
"clean: Removes all the product files, as well as any object files (.o files) or other intermediate files created during the build process."
If you select Clean
from the Product menu, XCode will delete the files inside every folder in the Build folder, if you select Clean Build Folder
it will delete the entire Build folder.
After Clean
command:
After
Clean Build Folder
command:
I think you should select Clean Build Folder
when you want to build a binary that you want to release to the AppStore, when you messed up with your project or when your app doesn't work for an "unknown" reason, otherwise use Clean
.
I hope I've answered your question :D
Clean…
cleans the folders for the current selected target.Clean Build Folder…
cleans the folders for all the targets.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With