#Xcode project build settings how to#
#Xcode project build settings code#

You can specify build settings at the project or target level. For example, the information in a build setting can specify which options Xcode passes to the compiler. I'll name it Environment.A build setting is a variable that contains information about how a particular aspect of a product’s build process should be performed. BundleĬreate a new Swift file and name it any way you'd like. Now all you have to do is access the base url in your code. All your custom user properties will get stored here. Select any property in Custom iOS Target Properties and click on the + button to add a new property.Īdd BASE_URL with the reference to your configuration property $(BASE_URL):Īfter adding the property, an ist file gets added to your project automatically. Select your project's target in Xcode and go to Info tab. Custom iOS Target Propertiesīy adding a reference to the configuration properties, you can access their values with Foundation's Bundle API. Now all that's left to do is to add a reference to the property in target's build settings. We only have a single configuration file, but this is where you can set up different configuration files for different environments: Expand Configurations and add your Configuration.xcconfig file to both Debug and Release. Select your project in Xcode and go to Info tab. We're nudged to use Xcode's Build Settings instead. This file is a feature and only created when needed. Following Xcode 13 release, there's no ist file by default anymore when you create a new project in Xcode. It'll get compiled during build time based on the build settings provided and copied into the app bundle.īut wait, there's no ist file in Xcode. As it should be.Īfter creating the BASE_URL property, you need to add it to your ist file. When you compile the app, none of it is available. com istīuild settings defined by Xcode project and configuration files are only available at build time. Next, add a property for your base url to the file: // Example: BASE_URL = awesome. Make sure not to select any targets for it. In your Xcode project, create a new Configuration Settings File anywhere you'd like and name it Configuration. You can read more on configuration settings file format in Apple's Xcode Help documentation. Each file consists of a sequence of key-value properties in a KEY_NAME = value format, where value can be String, Int, Bool, or other defined formats. xcconfig files allow us to define and manage build settings for our apps in plain text. 'The only way to keep a secret is to never have one.' Configuration Settings File

#Xcode project build settings code#

The best way to keep your secrets secure, is to obfuscate them using code generation. He suggests never to use Xcode Configuration files to manage your API Keys (or secrets).

I suggest reading this article by Matt from NSHipster on Secret Management on iOS.

We're going to use it to store a base URL for our API. One of the popular use-cases for using a configuration file is to manage constants across different environments.

Because all properties are in plain text, they are easier to read and you don't have to navigate Xcode's maze of build settings. You can open Xcode configuration files outside of Xcode and with any text editor. But even if you don't, you could still benefit from creating an Xcode build configuration file for different build settings. If you are working alone, you might not have these environments set up for a smaller app. The names can be different, but these are usually a development environment for devs to do their work, a testing environment for QAs and a production environment. If you are working as part of a team in a bigger company, it's likely you have multiple environments set up.

#Xcode project build settings how to#

How to manage build settings using Xcode configuration files