How to configure iOS apps for multiple environments (Dev, QA, Prod)

Step 4: Link your configuration file and pod configuration file with each created environment. After adding all the settings it will look something like this

Showing environment configuration file linked with selected schemes

There is one more trick to do that, for Step 4: Just follow the process which is shown in the image below:

Add the path of pod .xcconfig here in the environment config file

Select the environment configuration file as per configuration.

Now all the schemes with their respective environment are linked. There is one last step to working on this configuration properly.

Step 5: Select any scheme -> edit scheme -> and set your desired configuration.

The final step to achieving Environment Scheme configuration

The project is ready to run for multiple Schemes and the configuration setup is completed:

Select scheme from drop down and run — the environment will be automatically configured as required

var environment: String {

        let env = Bundle.main.infoDictionary!["ENVIRONMENT"] as? String ?? ""

        return env 

}

var hostURL: String {

        let env = Bundle.main.infoDictionary!["HOST_URI"] as? String ?? ""

        return env

}

Firebase Crashlytics for Multiple Environment

Why do we need Multi-Environment Configuration for Firebase Crashlytics?

Using multi-environment configuration for Firebase Crashlytics allows you to manage and separate the data and settings for different stages of your app development process, such as development, staging, and production. Here are several reasons why this is beneficial:

1. Environment Separation:
   By using different configurations for each environment, you can keep your crash reports organized. This helps in distinguishing crashes occurring in the development phase from those in production.
2. Focused Debugging:
   Crashes in the development environment can be addressed without interference from production data. This allows for more focused debugging and testing.
3. Data Privacy and Security:
   Keeping production data separate ensures that sensitive user data and logs from the production environment are not accessible in development or staging environments, enhancing security and privacy.
4. Release Management:
   Different configurations help in managing releases and hotfixes more effectively. You can test new features and fixes in staging before deploying them to production.
5. Performance Optimization:
   It allows for performance monitoring and crash reporting to be tailored to each environment’s specific needs, optimizing resource usage and ensuring that performance metrics are accurate for each stage of the app lifecycle.
6. Compliance and Monitoring:
   Different environments can have different compliance requirements. Multi-environment configurations help in meeting these requirements by ensuring that only relevant data is collected and monitored.
   Overall, the multi-environment configuration for Firebase Crashlytics provides a structured and efficient way to manage, monitor, and respond to crashes throughout the app development lifecycle.

To create a separate Firebase environment

Step 1: Create/add a project

Step 2: Add Project with a bundle ID you have for each environment

Step 3: Now download GoogleService-info.plist for each environment

Make a folder in a project and name it, as I have shown a folder named Firebase, and add a folder for each environment and name it as schemes (Development, QA, Staging, Production). These folders will contain GoogleService-info.plist for each environment  downloaded from the Firebase console as shown

Make sure for all the GoogleService-info.plist in every environment folder -> the Target Membership is unchecked because these will be handled from a script

Step 4: Now go to Project and select Targets -> Go to Build Phases -> click on + icon here -> Click New Run Script Phase

Add these script codes to your New Run Script Phase Gist link please click here