By John Gruber
Retool — build native iOS apps with just JS and SQL.
Determined to get someone on the phone, I used my employer’s developer account to be able to reach the phone support page, where I entered my number. Developer support then called me, and I gave my previous case number to a nice person on the other end of the phone, who explained that my case had been escalated to a supervisor, who then escalated it to their supervisor, and that I would hear back from them “soon”. This was in mid September. In early October, I called again and was told I would receive an e-mail explaining the situation, I haven’t.
More recently, I tried calling again and got to talk with a supervisor, who said I would be getting an e-mail with instructions to get my access restored. During the call, they told me my developer account is currently “inactive”. I followed up over e-mail a couple of days later and got a generic response that “the internal team is still investigating the issue” and thanking me for my patience.
Like I mentioned before, the problem began in August. So far I’ve tried every possible private communication channel before deciding to make this story public. It’s worth mentioning that I didn’t get any e-mail or call from Apple warning about any sort of action being taken against my developer account. Apple always says that “running to the press doesn’t help”. Unfortunately, they haven’t responded in any way, even when I tried reaching out through internal contacts that I have. So the only option I have left now is to “run to the press”.
It’s bad enough that his developer account has been disabled for nearly three months. It’s downright Kafka-esque that he hasn’t been told why and can’t get an answer from Apple.
Pure speculation on my part, but unsaid in Rambo’s write-up of this story is that he’s not just any random developer. Rambo is extraordinarily talented at what I would describe as digital spelunking — he explores the internals of beta OS releases and pokes at beta APIs and he finds things that weren’t supposed to have been exposed. And when he does, he publishes his findings. It would be quite a coincidence if that’s not the conflict at the center of his account having been disabled — that someone at Apple got pissed off and impetuously ordered Rambo’s account disabled, and now they don’t want to explain it.
Or, you know, maybe it’s just a simple mix-up with Rambo’s billing information. Could have happened to anyone sort of thing. Right?
★ Wednesday, 20 November 2019