{"id":6509,"date":"2021-01-05T14:25:09","date_gmt":"2021-01-05T08:55:09","guid":{"rendered":"https:\/\/www.innovationm.com\/blog\/?p=6509"},"modified":"2021-01-05T14:25:09","modified_gmt":"2021-01-05T08:55:09","slug":"build-and-deployment-configuration-flavors-in-ios","status":"publish","type":"post","link":"https:\/\/www.innovationm.com\/blog\/build-and-deployment-configuration-flavors-in-ios\/","title":{"rendered":"\u00a0Build and Deployment Configuration Flavors in iOS"},"content":{"rendered":"

Suppose your App has 2 Different Environments- \u2018Development\u2019 & \u2018Production\u2019 ( sometimes it may be 3 or 4 according to our Project needs ) and these Different environments have Different codebase or may be Different URLs. And you need to randomly move between all these various server URLs for the testing purpose or maybe another purpose depends on your project needs.<\/p>\n

Example:<\/strong> Suppose, you need to submit your app in App Store in \u2018Production\u2019 Environment, and currently, you select \u2018Development\u2019 environment Url And you forgot to change the Development URL into Production environment Url, And by mistake, you submit & Live your App in App Store. Therefore, it creates a Big Problem.<\/p>\n

So, in order to store important Data like API Keys\/Base URL and also needs to be secure, We use .xcconfig files and attach .plist file with them to fetch data.<\/p>\n

.xcconfig Files are supplemental Files that help in configuring a specific build type. These files are edited outside the Xcode, too.<\/p>\n

We are using 2 environments for now – Production and Development<\/p>\n

Step 1-<\/strong> Open your Project.<\/p>\n

Step 2-<\/strong> Select the Project file( Top file ) in the navigator area, then select the Info tab and make sure your project is selected. Look at the configuration Section. Here, we already have Debug and Release configurations. So, for 2 environments, we have to build debug&release.<\/p>\n

-First rename the present Debug and Release to Debug(Production) and Release(Production) and then pick the icon at the bottom of configuration Section and select Duplicate Debug(Production). And rename into Debug(Development).<\/p>\n

-Repeat this process for Release(Production) and rename into Release(Development).<\/p>\n

As shown in image-<\/p>\n

\"\"<\/p>\n

Step 3-<\/strong> Create a new folder \u201cConfigs\u201d and create new .xcconfig files For development and production.<\/p>\n

\"\"<\/p>\n

Then select Next and name the File Production and make sure that no target is selected because we do not add these files in the application bundle as they are not being compiled.<\/p>\n

\"\"<\/p>\n

Now, Repeat the process for Development, after that it looks as below image:<\/p>\n

\"\"<\/p>\n

Now, write the API keys and the Url\u2019s that are used in your Project For Production( Data is Different Based on Project needs ) Environment. Then after that repeat the process for Development.<\/p>\n

\"\"<\/p>\n

Note:<\/strong> Make sure that you enter space after and before in the equal sign( = ) And enter $() between Forwarding slashes because we need to split it with an empty variable substitution into .xcconfig files.<\/p>\n

\u00a0\u00a0\u00a0Example = MY_URL = https:\/$()\/\u2026\u2026\u2026<\/strong><\/p>\n

Step 4-<\/strong> Now, we need to set the appropriate file for each configuration. So, move to the configuration section in the info tab and select the correct configuration files. As shown in below image-<\/p>\n

\"\"<\/p>\n

Note:<\/strong> If you already use cocoa pods Then Delete the .xcworkspace file, podfile.lock and pods Directory ( make sure that you don\u2019t delete the podfile ) Then reinstall the pods( The reason for this is Because cocoa pods have it\u2019s own xcconfig files.)<\/p>\n

In Terminal you see that cocoa pods did not set the configuration since we already set the custom configurations. It provides a link to be included in each.<\/p>\n

Something like that ( see in below image ):<\/p>\n

\"\"<\/p>\n