Im running a Mac that generally has about 12 GB spare. I tried installing the Xcode 7.1 beta on a separate drive however it insists on installing all of the simulators on the primary hard drive, and it runs out of space.
So perhaps it's time to wipe Xcode and reinstall clean. This mac has a primary drive that started as Snow Leopard on a white macbook back in 2009. It's been backed up and updated regularly, and I wonder if this has left me with a lot of old cruft.
Look at it this way - dev'ing isn't about just the immediate IDE. Docs, sample projects, assets such as audio/video/images/data bases/...all add up. Not to mention the ancillary applications/tools/editors for those assets. Then there is the obligatory backup. Then there is the growth over time.
At the moment, Xcode and its simulators are using just over 90GB. Is this normal? If it isn't then a clean out of all those folders (i.e a brutal deletion) and a reinstall seem to me to be in order and should return me some space.
You can reduce the size of this directory by going to the Devices window in Xcode and deleting any Simulator devices that you don't use (each directory there corresponds to a Simulator device displayed in the devices window). Make sure you use Xcode (or xcrun simctl) to do the deletion; don't just delete them from the filesystem. If you change your mind later, you can always create new Simulator devices
The directories in "iOS DeviceSupport" are required for symbolicating crash logs from devices running the corresponding version. Use your judgement as to whether you can delete those directories. Worst case, you can back them up to DVD somewhere and delete them to save space. They are also used when debugging on devices, but Xcode will automatically regenerate them when you attach a device that doesn't already have a corresponding iOS DeviceSupport directory.
I've completely cleaned out things, unfortunately before I saw your reply so I was perhaps more brutal in my methods. Time Machine has everything on file in case, but I can report that having now updated to Xcode GM 7.0 and also having 7.1 installed, I now have 55GB free, with all simulators re-installed and all docsets installed.
While I agree in general that living near the edge of a full hd is not a good idea, I'm disappointed in the common community response which is just to get a bigger disc whatever the circumstances. Efficient use of storage seems to be a weak area for the osx ecosystem but also the community. Aside from the cost and backup complications there is an environmental impact of being wasteful. Some improvements are being made with app trimming on iOS, so perhaps we'll see the same on OSX soon.
Unfortunately this occurred for me when I had a big deadline the next day, causing me an extremely late night. I deleted Xcode then set about the libraries/simulators like I was no longer a developer. When I installed the new Xcode it put back the ones it needed.
I can only speak for myself when I remind you that as a developer, it's should be an economic decision, wrapped in pragmatism. HD costs are lower than ever and when biased against my dev time, there is no contest in terms of ROI, especially given that I can't order more time off Amazon, regardless of price.
Disk space is just another asset - don't let it control you. Respect yourself as a developer first, by taking appropriate advantage of modern tech while you prioritize housekeeping accordingly. Never squander your dev time needlessly.
My laptop HD can't be upgraded and had a ton of useless xcode files consuming unnecessary disk space. Thanks to the blog that others have posted here, I was able to free up enough space to download and upgrade xcode. It appears that version I upgraded was a 4.5GB download, so I'm guessing that it requires about 4 times the spaces since I had to free up 20GB before it would install.
The system had 31 GB storage after all the steps described here had been taken, apps deleted, Xcode moved to iCloud. Documents, pictures, large files all moved to iCloud. Moving Xcode to iCloud did not free up disk space as one would imagine.
Searching for Xcode on App store and clicking on the icon said something like "there's not enough space on your disk to install Xcode". A more helpful message would specify how much storage is needed.
The folder /Users/Shared had folders named "Relocated items" and "Previously Relocated items" that occupied 39 GB of storage. The read me in that folder explained that these files could not be moved into their original locations because of the upgrade. These are accumulated over successive upgrades and become huge.
Folks, I'm planning to purchase Mac Book Pro M3 Pro but have a question about a SCENARIO BASED SITUTATION.
What if I bought MacBook Pro and a couple of months later Apple changes the OS along with Xcode version and Xcode OS compatibility requirement? (they tend to come up with a new OS every 10 months)
Will it be possible to reload a new OS without loosing my data(draft App) if Apple decides to replace Sonoma?
Will it be possible to update an already downloaded version of Xcode to publish an app to the App Store?
Apple products and software are closely correlated so If I want to publish an app to the App Store I need the latest version of Xcode and to get the latest version of Xcode I need the latest OS.
I don't want to pay a steep price and end up with a product that is not compatible with Apple requirement to publish an app. Please Advise
If you want to publish an app (built with AI2 for iOS) in the App Store, you don't need Xcode, the latest MacOS or a Mac at all. However, if you want to create your app natively, i.e. with Xcode and Swift, as I have done so far, then you should actually keep Xcode and MacOS up to date. Of course, AppInventor also has to do this regularly with the build server ( ).
Anke, thank You so much for your response. Is IOS version of AI2 up and running? The link that you kindly shared has the word "test" in it. Apple says that the only way to make IOS apps is Xcode. Also, based on your experience with Apple products and software what should be the plan if I bought a MacBook Pro and Apple replaces the current OS and changes Xcode compatibility requirements? Am I gonna be stuck with a useless device? Will I be able to upgrade to a new OS and update an already downloaded version of Xcode? I've never had any Apple products. PC and Windows always seemed a lot more flexible. There're way too many unnecessary limitations with Apple products.
I can offer some observations that can be helpful. I have both the first generation (2016) and last generation (2019) of the MacBook Pro with the touchbar. These are both Intel based processors. The former cannot be upgraded and isn't running the latest Xcode but the latter one is (in fact, it is the one I use to publish the MIT App Inventor companion app to the store). So realistically you're likely to see 5 years of support but 8 is pushing it.
Hi Anke, here's the link to the Apple app store submission requirements
Latest News - Apple Developer The first line of the announcement states that:
Starting April 25, 2023, iOS, iPadOS, and watchOS apps submitted to the App Store must be built with Xcode 14.1 or later. ---- now it's Xcode 15.3 and Sonoma but the whole approach remains the same. I checked Thunkable before and it is not as good and user friendly as AI2 which is an awesome software. You guys did a tremendous job which made the IT world a better place for beginners.
Anke, may I kindly ask you to share the link with more information about
iosbuildservertest. May be I don't really need to pay $2160 after all, I'd be happy not to.
P.s. I stopped in at our local Apple Corporate Store(Philadelphia) to ask the sales staff the same questions that I'm asking you and believe it or not but No One Knows Nothing. They couldn't tell me the difference between M3 and M3 Pro chip. They've never even heard about Xcode. The only things they know well are pricing and credit card application.
Thank you so much Evan! The plan was to build an IOS app within a month from the day of the purchase. I know what has to be done programmatically . So my understanding is that the most recent model should be compatible with all of the Apple's new stuff for up to 5 years, right? Evan, your response is a huge help! Thanks a million for taking time and sharing a few thoughts with me
Hello!
I am trying to get passed some signing troubles with an Ionic application. I have followed the steps outlined here: -signing/ and replaced the xcode archive step with the ionic archive step.
In addition I am using the generate cordova build config step, and am setting the values to those used in the upload from the codesigndoc tool. I also ensured that I can create a valid .ipa file from xcode using archive / export.
I think the problem is that, when you open your generated .xcodeproj file its codesign settings are set to Xcode managed signing, Xcode generates a managed profile for your project, which you can use to export an ipa in your local Xcode.
I would recommand to setup your local project with manual codesign setting (turn off the Xcode managed codesigning) and run codesigndoc again. In this turn codesigndoc will collect your manual codesign files and upload them. Update the generate-cordova-build-configuration, with the new manual provisioning profile and run a new build.
A next upgrade came as a 400 Mhz AMD desktop, given again by friends, on which I ran a local EasyPHP webserver that I used to learn web development with PHP, MySQL and HTML/CSS. I coded a mod for Wolfenstein 3D on that machine, too.
The absence of fancy IDEs meant relying heavily on command-line tools and understanding the intricacies of the operating system. Debugging was a challenge, often involving hours of manual code reviews and print statements. But these constraints taught me the fundamentals of computing and the importance of perseverance.
The joy of seeing my code run successfully on that old PC was unparalleled.
3a8082e126