r/iOSProgramming • • Jul 05 '21

Discussion Tired of Xcode.

I don’t know about you, but I’m starting to get sick of it.

First, it’s terribly slow.

  • Opening a storyboard with a single ViewController can take over a minute, and any file I try to open will be a blank screen until it’s done loading the storyboard.

  • But then, just opening a project can take quite a bit of time.

  • Yes, SwiftUI is supposed to be better. But, personally, SwiftUI previews have only ever worked for tiny brand new projects. Then they just start failing.

Second, it’s unreliable.

  • One day it’ll open a project. The next, it’ll (take a long time and) crash trying. But opening said project via right-clicking on Xcode’s Dock icon will work. Go figure.

  • Then, suddenly, at some point while programming, all syntax highlighting will be gone, and auto completion will just stop working, plain and simple.

  • Edit 2: Also, @IBDesignable. It’s a neat idea. If only it worked reliably instead of randomly failing to render.

Third, I find it’s build time errors can be ridiculous.

  • The worst of course, is when using things like RxSwift. But I find the Combine ones pretty hilarious too, sometimes.

Fourth, it’s "refactoring" capabilities are meh.

  • When it does work, and doesn’t just take ages playing it’s accordion animation only to fail cryptically, the renaming refactoring feature will often behave like a simple search and replace, renaming properties from other classes and structures.

Last, weird bugs with more or less helpful logs:

  • Why do we have to wipe the DerivedData so often? It was almost nice and fine until we started adding SPM packages into the mix and they too were stored there. Now, after wiping those, we also have to redownload our dependencies. Yay

  • Did you know there were other folders you could clean up when stuff stops working? There’s xcuserdata in the xcworkspace, also ~/Library/Caches/com.apple.dt.Xcode.

  • And sometimes you have to reboot your Mac because somehow XCode suddenly lost the rights to write into one of it’s build folders. Don’t ask me how; I have no idea

  • Crashes / hanging forever because a device is plugged in / connected "over the network" ? Seems it’s been fixed since. But that was pretty annoying.

Anyway, sorry for the rant. It just gets tiring over time, and sharing with other people who might know that pain makes it feel better.

If anyone has solutions, you are more than welcome.

And if I’ve forgotten anything this godforsaken tool does wrong, you absolutely are welcome to chime in.

Edit: fixed format

170 Upvotes

96 comments sorted by

View all comments

3

u/cwir Jul 05 '21 edited Jul 05 '21

Please connect your device… it’s already connected $&@@x16262)&2$3 !!!!!!!!!!!!!!!!!!!!!!!!! Your device is busy, your device is not ready for development, your device, your device, your device. I’m also heaving a pick in my frustration over xcode lately. I’m working with external accessory so I have no other choice than Wi-Fi debugging - this is a nightmare to use, debugging crashes and is extremely slow even that my network setup is pretty good. When i started 11 years ago i remember working and coding with obj-c was way faster than today. Clearing derived data every other day is a must when you work on heavy projects. Please just stop adding new features, fix what’s already there for christ sake i beg you apple.

On the side note apple forcing storyboards makes no sense to me. No custom initializers, usually with more than 4-5 screens is a pain to use, not even mention merging this huge xml file when working in the team. All projects I saw with storyboards implemented because of “readability” were just funny and load 30 sec. yes you can split those, but in this case why not to use good old xib files?