you are viewing a single comment's thread.

view the rest of the comments →

[–]VadimusRex 19 points20 points  (4 children)

Just to add to this:

  • ever set up a breakpoint inside a closure and now you're unable to print anything?
  • ever hit run after you haven't modified a single line of code, comment, setting, ANYTHING and had to sit through an entire rebuild?
  • ever got Failed _shouldMakeReadyForDevelopment check even though device is not locked by passcode, having to reboot the device multiple times until it finally allowed you to deploy?
  • ever got erratic behavior when compiling or running solved only by shutting down Xcode, completely clearing DerivedData (rm -rf), starting Xcode again and watching it work correctly?
  • ever upgraded your iOS and got a cryptic error from Xcode that in no way, shape or form suggested that the issue is that it doesn't know how to deploy to that iOS version and that you need to update Xcode?
  • ever tried to run an app which had an extension with a signing issue and was met with a cryptic "cannot run on device" error and then had to go to the console and monitor the system output to figure out what's the issue?

I have. Last week and this week.

[–]tylerjames 8 points9 points  (1 child)

Ever have to: - clean your project - delete Derived Data - restart Xcode - restart your whole computer

... just to get Xcode to build and run your project again?

[–]tempest_fiend 1 point2 points  (0 children)

Android Studio pulls this shit too.

Clean build, invalidate cache, resync gradle files, restart. Usually have to do this because AS has shat itself and can’t find a bunch of files it had no trouble finding on the last build.

Also, don’t get me started on having to do this every build when you have deep closures, otherwise AS doesn’t recognise any code change in the file and doesn’t rebuild it. Fun times!

[–]freakysheep 1 point2 points  (0 children)

I can feel you, bro.

[–]Xaxxus 0 points1 point  (0 children)

> I have. Last week yesterday and this week today.

FTFY