Skip to main content

“In order to continue the installation, please close the following application: iTunes” : Xcode Menace


Just when I thought everything was alright…I got “In order to continue the installation, please close the following application: iTunes” and it was showing after it completed almost 97% of the installation.

Yes….I was trying to install Xcode 4.1 into the Snow Leopard…
Developing app for MAC is something I always wanted to do,and now when I was just going to utilize my Apple Developer membership this stupid error cropped it's head.



I checked the dock bar, and iTunes wasn’t running at all. I also have an app called QuitsAppsMBI which is a handy tool for quitting applications, nothing on there to say iTunes was running. Lastly, I checked Force Quit to see if there was anything, and there was nothing in there at all.


Not wanting to potentially ruin the installation, I wasn’t sure I wanted to just kill the Installer, so I seeked the help of Google to see if there were any suggestions on what to do. I came across the following post on James Greenhalgh’s blog: http://james.greenhalgh.eu/2011/in-order-to-continue-the-installation-please-close-the-following-application-itunes

This post detals exactly the problem I was having, and a really simple fix! Open up Terminal (found in Applications\Utilities) and type in the following command:

ps x | grep iTunes

This will list all the processes running on your computer with iTunes in the path. This returned the following for me:

189  ??  S     0:00.04 
/Applications/iTunes.app/Contents/MacOS/iTunesHelper.app/Contents/MacOS/iTunesHelper -psn_0_57358
2613 s001  S+     0:00.00 grep iTunes

So this shows that the iTunes Helper is still running in the background. To kill this off, you then enter the following command:

kill 189

The first number from the first command is a process ID, so you’re telling it to kill the process with ID 189. Change the 189 to whatever the ID shows as from the first command, and it’ll end the iTunes Helper. After a few seconds, the Xcode installer will clock onto this and continue the installation!

Comments

Post a Comment

Popular posts from this blog

Racecraft (Project Koru) · Prologue — The Origin Story

Racecraft · Prologue , The Origin Story It Started With a Wine List and a Question About Racing How a happy-hour conversation in the Bay Area turned into a trustable AI race coach , and then into a second version that runs entirely on a phone, on the NPU. This is the prologue to a five-part series. Two years ago(1st November, 2024) I was in the Bay Area for a GDE Summit. If you've never been: it's a couple of days of talks among Google Developer Experts, the kind of people who get unreasonably excited about a new on-device runtime, and then , mercifully , a happy hour where everyone stops performing and just eats. We ended up at a restaurant(Puesto Santa Clara), a long table of GDEs, and I was doing the most important engineering of the evening: trying to decide which wine to order. Across the table was Ajeet Mirwani . I don't even remember how the wine talk turned into racing talk , these things drift , but the moment the word "racing" ...

A Split‑Brain Neuro‑Symbolic Training Method for High‑Velocity Autonomous Coaching from Telemetry

 Author: Rabimba Karanjai Scope: Problem statement + data methodology + model training (no deployment discussion) Abstract Real‑time coaching in motorsport is a safety‑critical learning problem : a system must map noisy, high‑frequency telemetry to short, actionable guidance that remains physically consistent and avoids hazardous recommendations . This paper proposes a “Split‑Brain” training formulation that separates (i) a semantic coaching target (what action/critique should be expressed) from (ii) a reflexive interface (how actions are represented as compact, verifiable tokens). The approach trains a Small Language Model (SLM) in the Gemma family [1] using QLoRA fine‑tuning [2] , and introduces a telemetry tokenizer plus teacher‑student synthesis pipeline to generate instruction‑action pairs at scale. Core contribution: a reproducible method to convert “ golden lap ” differential tel...

The Throughput Trap: Benchmarking vLLM on OpenXLA and the Reality of Production LLM Serving

vLLM Systems · DevLab 2026, Deep Dive I was recently invited by the Google TPU team to speak at the OpenXLA Summer DevLab 2026 . This post breaks down our deep-dive evaluation of the matured vLLM + OpenXLA stack, the fundamental engineering mismatches between CUDA and XLA serving paths, and why traditional capacity metrics are lying to you. If you are operating large language models at enterprise scale right now, your platform architecture team is likely staring at a massive infrastructure crossroads: Should we migrate our core serving workloads from GPUs to TPUs? Historically, NVIDIA's CUDA ecosystem was the only serious option for user-facing, low-latency LLM generation. But here in 2026, the economics and infrastructure options have transformed. Google TPUs are highly available, cheaper per chip, and the open-source serving stack built around vLLM and OpenXLA has officially achieved absolute production readiness. Yet, when our infrast...