3 ms·
Edit: found a fix, if quitting iTunes isn't enough for the installer, you need to launch the Activity Monitor and manually kill the "iTunes Helper" process. Wha
by epistasis 15y ago
Edit: found a fix, if quitting iTunes isn't enough for the installer, you need to launch the Activity Monitor and manually kill the "iTunes Helper" process. What a pain.
This seems extremely half-baked. The App Store doesn't install Xcode, it just downloads an installer for Xcode, and ever-so-helpfully places it in LaunchPad.
After launching the installer and letting it run for many minutes, it silently popped up a window requesting that I quit iTunes for the installation to proceed. Besides being an insane request, when I do quit iTunes nothing happens. And if I double click on the iTunes name it launches iTunes. And on top of that, this request window isn't associated with the installer app, so I wouldn't even know it has anything to do with Xcode unless I'm not doing anything else on my computer.
And to top it all off, the installer has disabled all its buttons, so there's no clean way to quit it, and no way to get it to check for iTunes again.
This is about the lowest quality that I've ever seen Apple achieve; I hope that the rest of the dev chain gets more love.
- mattmichielsen 15y agoThe "please quit iTunes" thing happened to me with Xcode 4.0 on 10.6 as well. Pretty ridiculous.
- fredoliveira 15y agoThe Xcode installation asks you to close iTunes because of iTuneshelper and how iTunes will sync devices (including development devices) when they're plugged in. It makes sense that Xcode asks you to quit itunes (and kills ituneshelper too) to update files. It isn't ridiculous.
- deleted 15y ago[deleted]
- epistasis 15y agoThe broken application detection and the refusal to identify which processes need to be killed is ridiculous. Having a dev system that's so fragile that iTunes needs to killed when installing Xcode is insane. It's the request of a lazy programmer that's not willing to put in the work of understanding the real requirements or working around the problems, and would be unacceptable in a consumer-facing application. I don't want to say it's OK in the developer tools, but probably not as bad.
- pornel 15y agoIt is ridiculous, because: • asks user to perform task manually which is trivial to automate: `tell application iTunes to quit`. Apple even has sudden termination API that iTunes could use to make it safely killable most of the time. • needs to quit iTunes in the first place. Why can't it take advantage of versioning of libraries and frameworks? Why can't it update files in place? (running application should see old version [inode] until it closes the file). • and the usual ridicule: a music player is a critical piece of device sync and development infrastructure.
- sdkmvx 15y agoIn a terminal, do killall iTunesHelper. Apple did mess up, but that will get you through. If you don't know, iTunesHelper is the thing that starts iTunes when you plug in an iThing.
- thenduks 15y agoInteresting, I got the notice and quit iTunes same as you - I stared at the notice for a bit thinking "hmm, I did quit iTunes..." But then I got distracted doing something else and a couple minutes later I heard the ding that something finished installing (Xcode). So, for anyone else reading this, try just going to make a sandwich :)
- ezy 15y agoI just had the install hang at the end, hitting the close button on the window after waiting entirely too long causes its "installhelper" process to jump to 100% CPU (probably spinning on a closed pipe). I have to agree -- the packaging on this is complete shit.