Once all the necessary assets have been prepared, you can build your Mobile Authenticator Studio app with the portal.
Build process
Some of the build or customization features are optional. If you choose to use an optional feature, all associated integration steps become mandatory. Steps that are entirely optional are marked as such.
To create a build
Configure the system parameters:
Navigate to the Mobile Authenticator Studio Portal and log in.
In the Build List screen, click Create Build.
Enter a name for your build.
(Optional) Add a description.
Select the Mobile Authenticator Studio version from the drop-down list.
Select at least one operating system.
Customize the general parameters:
Add the customization file for the app’s look and behavior.
Add the translation file for in-app text strings.
Customize the legal information and help content:
End user license agreement (EULA)
To display an EULA, select the languages you want to include, and add one text file per language.
Offline help
To display offline help, select the languages you want to include, and add one text file per language.
Customize the Android-specific assets:
If you want to integrate Google services into your Android app, add a Google Services file.
Add an image file with the launcher icon.
(Optional) Add Image file with splash screen icon.
The implementation and customization of a splash screen icon is optional but recommended.
Add image files with adaptive background and foreground launch icon.
Add an image file with notification icon.
Customize the iOS-specific assets:
Add an image file with the app icon.
Add an image file with the splash screen icon
Finalize the build:
Verify all entries and uploaded files.
Click Create.
During the build process, your tenant ID and build ID are automatically added as prefixes to your files for identification and logging purposes.
After submission, you are redirected to the Build List screen where the build is added to the list of available builds. Initially, its status is set to Queued. As soon as build processing begins, the status changes to In progress. The final status is either Success or Failed, depending on the outcome of the build.
You need to re-sign any app built with the portal with your own signing identity!
Input validation
The portal validates your input and checks the following:
A valid build name is provided:
The field must not be empty.
The entered name must not exceed 255 characters.
All mandatory fields are completed and correctly filled in.
All required files are uploaded.
All files required for selected optional features are uploaded.
All uploaded files use the correct format.
The portal indicates the required format for each file.
The—optional—description does not exceed 255 characters.
At least one operating system is selected.
No uploaded file exceeds the allowed maximum size of 5 MB.
The total size of all uploaded files does not exceed the 50 MB.
If any validation check fails, the portal displays an error message next to the affected field or file and provides a summary of all input errors at the top of the Create Build page.