Create a Native Configuration
Note: This feature is only available on our Growth plans and above.
You can use native configs to:
- Overwrite the unique bundle identifier or id attribute in
config.xml
- Overwrite the App Name as it will appear on the home screen of a device
- Overwrite the
Appflow SDK (Deploy Plugin) variables and preferences
In this part of the tutorial, we'll setup a native configuration for
Development
to:
- Use a unique bundle id so that we can install both the development version of the app and the production version of the app on the same device
- Change the App Name so we can tell the two installations apart once they're installed on the device
- We'll also modify the
Deploy Channel that the development version of the app listens to so that we can assign updates to that channel first to make sure they work (before we assign them to theproduction
Channel)
Create a Native Configuration
To create a native config, go to the Package > Native Configs
tab in the Appflow Dashboard sidebar and click
New native config
in the top right.
Next:
- Name the configuration
Development
- Overwrite the unique bundle id with
com.snapcats.demo.development
- Overwrite the app name with
Snapcats - Dev
- Overwrite the deploy channel to be
Development
Add the Native Config to an Automation
To take full advantage of automating your development environment, you'll want to add the native config to the automation we created earlier.
In your Automations
tab, click
Edit
from the Options
icon on the right of your automation, select the configuration from
the
Native Config
dropdown and click
Save
.
Now your apps should automatically use a different
bundle id
, app name, and deploy channel between your development and production
builds. This means you can install both your development and production applications on the same device and easily tell them apart! 🔥