Add Plist Path for build configuration Renamed Plist Files Linking Build Configuration with the Configuration File: From Targets, just select a plist file, and rename it with the same name for the Debug and Release configuration. Now we have to set the appropriate plist path for each build configuration. After that, add the keys from the configuration file to the plist files like this: Add keys in Plist File You can set some environment-specific keys and values in the plist files. Copy and paste the same plist file for the different environments inside the project, and rename each of the plist file with the environment’s name. Server URL added in Configuration File Add Plist Files: Now the most important part starts: add your server URL and other customized key value in the corresponding configuration file. Configuration Settings FileĪfter adding all the config files, your Project Navigator left pane should look like this: Configuration Files added Right click on Project, select new file, then add Configuration Settings File and give it the same name as the environment. After adding all the schemas, the manage schema screen should look like this: All the schemas are added Add Configuration Settings File: Oops, don’t forget to check the shared box there. Then add the rest of the four schemas for the other environments.
Rename it as Development - or you can delete the existing and add a new one with the name Development. There you can see that one schema is already available.
After adding all the configurations for different environmentsįor the schema creation, go to manage schema in top left corner of XCode. Now click +, and select Duplicate Debug (Development) and Duplicate Release (Development), then change the duplicate environment name with the others available names. Similarly, double click on Release and rename it as Release (Development). Add a new configuration for an Environment (Debug and Release)įirst of all, double click on Debug and rename it as Debug (Development). In the Configurations, we have to add our own configuration for the five environments (Development, Production, QA, Beta, and UAT) there. Then select Info from the two options ( Info and Build Settings). Now to add our build configurations, select the project in the Project Navigator pane on the left.
Then if we want, we can make changes specific to a particular build configuration. Add Schema and Configurations:īefore adding a schema, we need to know that every XCode schema comes with two different build configurations: Debug and Release. Open XCode and create a new single view application with a proper name.
Xcode build settings how to#
In this tutorial, I will show you how to manage different environments using schemas and configuration. So the idea is, if we create different schemas and configurations, then it allows us to change the application server URLs, App icon, Plist file, and configuration. And by applying this idea, we can easily handle any scenario. We could do this by changing some hardcoded flag value in the constant file or using macros, but it makes everything more complicated.īut if we think for a little while, we can come up with an idea. So before creating a new build pointing to an environment, we need to keep in mind that we also have to change the server URL. For these different environments, there are different server URLs, app icons, and configurations. Now, when you build on the command line using xcodebuild, your built product will be in a known place.As iOS developers, we are already aware of managing different environments like Development, QA, Beta, and Production. This example is for a framework project, so it copies the whole framework directory to the project directory (where your. You can type in a script which should be something like this: cp -R $/amework
Xcode build settings plus#
Now click on the Build Phases tab, then on the little plus sign, then on 'New Run Script Phase'. Select the target in Xcode (these instructions are for Xcode 12): click on the file icon in the top left to open the Project Navigator, then on the project name next to an Xcode icon, then on the target in the right-hand pane. My fix: add scripts to the project to copy the built files to wherever you like. You can change the build directory using the project settings, but those settings don't seem to be saved in the shared settings, so it's hard to get them into source control, which makes it difficult to create automated builds that get everything from source control first.
0 kommentar(er)
