The Build Settings for your apps are managed and stored on the Twixl platform. This article explains how to create a Build Setting and what the available settings exactly mean.
What is a Build Setting?
Before you can actually build your app in Twixl Publisher, Twixl needs some information in order to be able to build an app. This information has to be entered in the Build Settings on the Twixl platform.
A Build Setting consists of a number of configuration options that determine the type of app that you will be creating, and which features will be enabled.
E.g. a build setting can contain the following info: which user interface languages are supported, the artwork (app icon, etc…), code signing information, etc.
Once a build setting has been saved, creating a build of the app only requires a few mouse clicks. A build setting can also be exported so it can be imported in another Twixl account.
All configurations mentioned on the Build Settings page require a new build of your app when you have changed data in one or more of these configurations.
How to create a new build setting
In the left menu bar > Click Build > Select Build Settings
If you want to create a new build setting, select one of the following:
- Click the '+' icon
- Or click 'Add your first build setting'
- Name: The name of your build setting.
- Home Screen Name: The name of your app, visible on the home screen of your mobile device
- Build for: Which types of devices are supported? Phone, tablets or both?
2. UI Languages
Here you can select the user interface languages your app will support. This is related to Twixl-specific messages that may be shown to the user/reader. Either you can check only the languages that are relevant for your market, but there's no harm in just checking all the languages.
- App Icon: You can choose a different icon for iOS and Android
- Launch Image: The launch image of your app - see also this article.
- Launch screen Text Style: Text will be displayed on top of the launch image. Select the text color that works best with your image.
Especially for Android devices, creating an App icon can be confusing as the result might show something different than intended. This is because a lot of manufacturers of mobile Android devices create their own UI on top of the Android UI. If you want to be certain your design fits most devices, check your icon with Android Studio! Read all about it on this Android help page.
4. Code Signing
OTA Deployment URL: Only applies to Ad Hoc and Enterprise builds. Should be a
httpsURL. See this KB-article for more info.
5. Bundle Identifiers
- Apple Team ID: Required to code sign and build your app. Navigate to https://developer.apple.com/account and click on Membership in the left column, copy the Team ID, a 10-character code, and paste it in the Team ID field.
- A bundle ID or bundle identifier uniquely identifies an app. This means that no two applications can have the same bundle identifier. To avoid conflicts, Apple encourages developers to use reverse domain name notation for choosing an application's bundle identifier, like
com.twixlmedia.appname. If the value for an App Type is empty, that App Type can't be built. We recommend to use the same identifier for all app types.
6. Push Notifications and Google Analytics 4
- google-services.json: Used for setting up Push Notifications on Android devices. See this article for more info.
- GoogleService-info.plist: Contains all of the information required by the Firebase iOS SDK to connect to your Firebase project.
- Both Android and iOS push notification statuses will change as one has completed the configuration.
7. Background audio
When you want audio to keep playing when the user's device is in sleep mode, you can enable that feature here.
8. Apple App Tracking Transparency
Apple introduced App Tracking Transparency in iOS 14.5. If you want to ask permission to your users to track them, you can enable this option in the build settings for your app, and you can enter the correct usage description of why you are asking permission in all relevant languages.
What happens when users select 'Do not track' ?
Please note that Twixl doesn't change anything to the way cookies are handled in online web content. In order to allow you to handle cookies properly when a user asks not to be tracked, you can read the
trackingAuthorizationStatus custom variable from within your web page to determine whether or not the user has allowed to be tracked. This variable can be read by using the
How to edit an existing Build Setting
Hover over the Build Setting title and click on the 'edit' icon.
You can now change the fields you want to update and click 'save' when you're done.
How to import an existing 'legacy' build setting
If you have previously built Twixl apps using a release before Twixl Publisher 12, it's good to know that you can easily upload your existing build settings to the Twixl platform:
- Open the Twixl macOS App.
- Select the Tools menu.
- Select Show Legacy Build Settings...
- Finder will open the folder where your legacy build settings are located.
- Select the relevant build setting and compress it (
- Go to the Builds Settings of your app on the Twixl platform.
- Select 'import' to upload your build setting.
- Upload it to the Twixl platform.
- All done!