#XCODE PROJECT BUILD SETTINGS HOW TO#
#XCODE PROJECT BUILD SETTINGS SOFTWARE#
#XCODE PROJECT BUILD SETTINGS CODE#

It’s always recommended to leave those to Standard – $(ARCHS_STANDARD), which is armv7 and arm64. Here you can set the supported device architectures on which your app can run on. It’s the first section in build settings, so we will start with Architectures first. Here’s a list of all the settings for reference. Is some path configured in a wrong way? Are the architectures properly set? What about the linker flags? In this post, we will look at several build settings (not all since there are too many), and what errors they might cause.

Usually, when your app shows build errors or it fails to validate on iTunesConnect, build settings is the place that you should search for errors. If you didnt’ aware that before, this means you can create a build for debug and another one for release with a different setting.Build settings in Xcode define how your app is going to be built. Once done, you should see that Xcode already provides you two different configuration levels: Debug and Release. Select the top-level element in the project navigator and make sure the “YOUR_PROJECT_NAME” item in the Project section is selected. Or if you prefer, start with an existing one that is available on your computer. Creating the Build Configurationįirst, let’s create a new project using Xcode. Putting build configuration settings into files is a huge win for configuration management. This is what I am going to walk you through in this tutorial. Then you can build a different version of an app by simply changing the scheme. xcconfig files and refer those in your project info. The alternative approach is to put your build configuration settings into.

#XCODE PROJECT BUILD SETTINGS HOW TO#

If you haven’t read that, please do his tutorial – How to Use Xcode Targets to Manage Development and Production Builds that covers all the key concepts. Defining different preprocessor macros will control the conditional compilation of various chunks of code.Įugene Trapeznikov has already covered this approach in this excellent tutorial.

It could also be achieved by using Bundle Identifiers. Each time a target is selected, a different ist will be used, hence we will be able to differentiate variables like token, URLs for different builds. One is to create different targets, each one of which employs different ist. There are different approaches that can achieve it.

#XCODE PROJECT BUILD SETTINGS CODE#

How can you efficiently manage all these build variants with the same code base in Xcode? This is what I want to discuss in this tutorial and show you how to create multiple configurations with the help of Xcode. On top of that, you may not be showing the same level of information when an error occurs in the application for all the builds. When you move to the next stage, the other build will have another URL for connecting to the staging/production server. The build is probably configured with a test URL. All of these builds are not exactly the same, each of which usually has some specialties and a slightly different configuration.įor example, if the app needs to connect to a backend, it is very likely the app is connected to the test environment during QA tests. At last, there will be the production-ready application, once the client is satisfied with the build that you have sent. When the app passes all tests and got the QA team’s approval, you will create another version which is sent to your customers for beta test before pushing it to App Store. When you are ready to move to the next stage, there is another build that will be utilized by your QA group to test the features and bug fixes. At the early stage, there will be the one that conforms to your local configuration.

#XCODE PROJECT BUILD SETTINGS SOFTWARE#

During the development lifecycle of a software project, you probably create different builds at various stages.

Xcode project build settings