Native configs allow you overwrite certain configurations without having to commit changes to version control on a per build/automation basis.
A few things you can leverage Native Configs for include:
- Overwrite the unique bundle ID or App ID in Capacitor configuration.
- Overwrite the App Name as it will appear on the home screen.
- Overwrite the Appflow SDK or Deploy Plugin variables and preferences
- Set the DisableDeploy
truefor development and automatically set it back to
falsewhen building binaries for release.
This feature is only available on our Growth plan and above.
With Native Configs, you can make Staging, QA, and Production versions of your app, all installable on the same device and with the ability to easily tell them apart. This makes it easy to build your app for multiple environments from the same version of the code.
- To create a native configuration, go to the
Build > Native Configstab in the sidebar and click
New native config.
- For the QA version of your app, we need a different Bundle ID, App name, and Deploy Channel so that you can install it on a single device and easily tell it apart from the development version.
- Now you can use this Native Configuration in conjunction with an Automation to create a QA build each time you push a commit to a specific branch. To create the automation, enter the branch as "QA" and select QA native config from the drop down.
- You can also use Native configuration when triggering a build manually.
Note: If you plan to use Native Configurations to modify Bundle IDs with your iOS Package builds, you will need to setup code signing credentials using those alternate Bundle IDs. See our section on Generating Credentials for more information.