20 comments

[ 3.6 ms ] story [ 49.8 ms ] thread
Glad that the XLIFF file import bug is fixed
Holy multi-GB download Batman!

How do developers on slow and metered connection deal with this?

I have never ever in my life downloaded XCode with full Bandwidth. It always takes ages to download, despite fast internet download speed. :(
Not on that kind of connection, but I can rarely successfully download something that large from the App Store on the first attempt. I've found it far better to get from the tools area of the developer member center.
What I'm always shocked at is that the App Store doesn't seem to have any capability to resume a download.
The app store on OSX is among the buggiest pieces of software I've ever used.

- on opening it's very slow to render the first screen

- on clicking, the "updates" tab is extremely slow to display anything.

- clicking to initiate an update often doesn't do anything, and multiple subsequent clicks are required

- once an update is initiated and downloading, the state is often inaccurate on the updates screen

- often after clicking "update all", only some of the updates actually begin. This happens on the IOS app store too.

This is with a fast (120 megabits per second) connection and a top of the line 15" macbook pro.

How do developers on a slow and metered connection download OS updates? Surely that's 100x worse.
A good point - some updates from apple are again multi-GB.
I'm travelling semi-permanently (away from "home" ~9 months now). I had to update OS X and Xcode recently. 11GB fortunately only took 2 days (and $60 of data charges) since I'm somewhere with ok cell LTE. I did have to delay the update for a month or two until I was somewhere I could do it.
As someone who hasn't used XCode in a while, why is this release news-worthy?
(comment deleted)
That's a really long time to patch that critical git 2.7.4 vulnerability. Have they even patched the openssh UseRoaming bug yet?

Using only Apple tools to interface with foreign git repositories on the internet is a high risk sport these days (weeks (months))...

Upstream fixed the issue a couple days before Xcode 7.3 was released (and didn't even have their story straight about what version actually contained the fix). The fix was available in the 7.3.1 beta less than a month later, so I'm not sure where you get "months" from there.

As for the OpenSSH issues you mention (CVE-0216-0777 and CVE-0216-0778), those were fixed in OS X 10.11.4 months ago.

The git bugs were announced around March 15th (with some funny business going on with 2.7.1 and 2.7.3, before 2.7.4 came about). Debian released patches for git in DSA-3521-1 on March 19th, Xcode didn't fix this before 7.3.1 yesterday. That's about a month and a half. Beta versions of Xcode can't be used to submit to the app store, so they aren't useful because any serious developer will still need to have the latest stable xcode installed and probably set as default to not risk appstore submission problems.

Debian: 4 days to patch. Xcode: 50 days.

The openssh bugs were announced around January 14th. Debian released patches for OpenSSH in DSA-3446-1 on the same day. I guess Apple finally fixed it in OSX 10.11.4 which was released on March 21st. That's more than two months. Thanks for the heads-up, though, after two months with no patch I kind of assumed there would never be a patch.

Debian: 0 days to patch. OSX: 67 days

Will the Mac App Store download only the diff?
It did for me, was about 235mb.
Why is this interesting? It looks like any other Xcode update.