If you’re curious, try searching ~/Library/Developer for “IMG_0005.JPG” – I found 90 copies of the same photo. Keep in mind that each of those simulators is feature complete, right down to those sample photos you see in the Photos app.
#IOS SIMULATOR FOR MAC TOO BIG INSTALL#
First, install the awesome tool GrandPerspective, then point it at your ~/Library/Developer directory. Xcode’s initial install size is beyond our control, but its extended post-install growth is something you can reduce. If I hadn’t been cleaning Xcode’s device support directory, each of those combined would have been taking up a whopping 20GB of space, even though each beta version was effectively rendered obsolete as soon as its successor came out. In my case, I recently finished writing a book teaching all the new iOS APIs in iOS 11, which meant I had installed iOS 11 betas 1 through 10 on my devices. The problem is, Xcode doesn’t ever seem to want to remove device support once it’s installed, so if you’re an active iOS developer who doesn’t actively prune this yourself there’s a good chance you’ll find around 40GB or more of device support data – most of which is for iOS versions that you don’t even think about any more.
This is no small amount of data – you can expect Xcode to chew up 2-3GB for each iOS version you connect. What Xcode is doing is configuring its device support system so that it understands all the frameworks that ship inside the iOS version you connected, which in turn means it can symbolicate crash logs. This happens once per iOS version, although it’s extremely fine-grained – even going from iOS 11 beta 9 to iOS 11 beta 10 will cause this process to repeat. You see, Xcode is a bit sneaky: the 10.41GB that Xcode 9 takes up is actually only its starting size.Įach time you connect a device to your computer, you might have noticed Xcode likes to spend some time “Processing symbol files” or “Preparing debugger support” for that device. Sponsor Hacking with Swift and reach the world's largest Swift community! But wait – there’s more!Īll this extra growth means that Xcode 9 is more than twice the size of Xcode 5, but even that’s not the whole story. SPONSORED With Sentry’s error and performance monitoring for iOS, you see mobile vitals that actually matter, can solve any latency issues quickly, and learn how each release is performing over time. Many developers – myself included! – have a long wish list of features we want to see in Xcode 10, so there’s a never-ending trade-off between cutting size and adding features. It’s also important to note that Xcode has added features over those years, such as Swift in Xcode 6 or App Thinning in Xcode 7, so some amount of natural growth is inevitable.
#IOS SIMULATOR FOR MAC TOO BIG DOWNLOAD#
Now, some amount of natural fluctuation is to be expected – as Firlik said back in 2012, Apple can adjust its selection of simulators in order to reduce the initial download at the expense of possible later downloads. Let’s take a look at some figures: Version
When we shipped Xcode 4.2 we were able to shrink that package size down to about 1.5 gigabytes by making some of the legacy content – like the older iOS simulators – downloadable on demand.Īt the time that was a big and welcome improvement, but sadly it wasn’t to last: after going on its crash diet in 2012, Xcode has since been busy at the dessert aisle and has grown far beyond the “no more to be said about that” size of Xcode 4.1. Last year when we shipped Xcode 4.1 our download size was a little bit over 4 gigabytes, and I don't think there's anything more to be said about that. Here’s what Matthew Firlik (Director of Development Technologies at Apple) had to say at the time: We all know that Xcode has struggled with being a little on the portly side for some years, and even Apple acknowledged this back at WWDC 2012.
0 kommentar(er)
