![]() Note: If you don’t have an Apple Developer account you can use here, don’t worry. Change the value for Team to that of your own Apple Developer account. In the Project navigator, select Stellar Space.Ĭurrently, the Team used to archive Stellar Space is set to None.In Xcode, follow these steps to reach the Signing and Capabilities settings for Stellar Space: But first, you need to prepare Stellar Space for code-signing. In this section, you’ll archive Stellar Space and then remove that archive from your Mac, saving valuable storage space. You could have years-old archives waiting to be cleaned up. Whenever you archive an app for distribution on TestFlight or the App Store, that archive is stored locally on your Mac. But archived release versions are stored elsewhere. This clears up the debug version of Stellar Space that you built. Remember: To delete all your derived data, you need to delete the entire DerivedData folder. With that, you’ve cleared the derived data for Stellar Space. Note: Depending on the language settings on your Mac, the menu option may say Move to Bin or some other localized option. Right-click the Stellar_Space folder and select Move to Trash to delete it. ![]() Mine is named Stellar_Space-gmjdilbusvnhawfcpcbkkdqfsiuv, but yours will be different. In your Finder window, look for Stellar Space’s derived data. Next, you’ll delete only the Stellar Space folder, in case you want to keep the data for any other apps that have particularly long build times. Deleting Derived DataĬlearing your derived data is as simple as deleting the entire folder from Finder. In fact, clearing derived data is a common trick among iOS developers to sort out pesky compilation issues.Īlthough deleting derived data is safe, your build will take a little longer next time while Xcode builds your project from scratch. ![]() When to Delete Derived DataĮverything in DerivedData is safe to delete. In the Stellar Space folder, you’ll find supporting files that Xcode generated the last time you built Stellar Space. Similarly, the individual project folders also quicken build time. Xcode shares these cached modules between projects and builds to quicken build time. ModuleCache.index stores modules that Xcode compiled earlier. Your derived data contains a ModuleCache.noindex folder as well as folders for any projects you’ve built in Xcode, such as Stellar Space. Here, type the location of your derived data folder:Ĭlick Go to change the Finder window’s path to DerivedData. In the Finder menu bar, select Go ▸ Go to Folder…. To find your derived data folder, open a new Finder window. You’ll find your derived data folder in your macOS user library. When you build a project, Xcode stores build files for that project in your derived data. Clearing that storage is one of the things you’ll learn in this tutorial.Įarlier, when you built Stellar Space, Xcode saved some caches and build files. Images saved to your iOS simulators use storage on your Mac. Using NASA’s Astronomy Picture of the Day API, Stellar Space shows images taken by NASA for users to choose and save to their device. Make sure to choose a simulator as the build target, then build and run. So get ready to reclaim some long-lost Mac storage! Getting Startedįirst, download the project materials by clicking the Download Materials button at the top or bottom of this tutorial. Once you understand what each directory does, you’ll write a script to help keep your Mac in tip-top shape. In this tutorial, you’ll learn more about the purpose of each directory and why you might want to clear it. This tutorial will give you the know-how of when and why to delete some of Xcode’s supporting files. Don’t delete anything unless you’re sure Xcode will work fine without it. Note: You need to be careful when deleting Xcode’s data on your Mac. Even Xcode needs a bit of spring cleaning sometimes. If you see strange behavior when building an app, clearing folders such as derived data and caches can help to restore normality. It can also be a source of strange bugs and compilation issues. To make matters worse, this saved data doesn’t only eat into your Mac’s precious storage. Over time, Xcode’s storage size bloats when considering some of its tools and directories: For all its good qualities, Xcode is a notorious storage hog. ![]() But those 11 gigabytes are just the tip of the iceberg. A fresh installation of Xcode takes 11 gigabytes on your Mac. Xcode makes it easy to build projects, debug them and code-sign the resulting app.īut all the functionality provided by an IDE takes up space in your Mac’s storage. Using an IDE for iOS development comes with myriad benefits. It’s a full-blown Integrated Development Environment (IDE). Xcode is more than a plain old text editor. ![]()
0 Comments
Leave a Reply. |