Customization Tool logs

When binaries are being generated, logs are printed to the GUI or the terminal window. They are stored in \CustomizationTool\log. One log file is generated for each edition.

If the build fails, read these logs carefully as they may help you identify and resolve issues.

Output folders

The customized binaries are located in the \CustomizationTool\release folder, which is dynamically created during binary generation. Each Mobile Authenticator Studio edition has its own folder.

Android

The \CustomizationTool\release\android folder contains the customized AAB and APK files.

AAB (Android App Bundle) is a publishing format that includes all your app’s compiled code and resources, and defers APK generation and signing to Google Play. It must be used in order to publish your app on Google Play.

The APK file is a universal APK generated from the AAB file and signed using the certificate given during customization. It includes all of your app's code and resources such that the APK is compatible with all device configurations your app supports.

To install the APK file on an Android device

• Plug in the device with USB and download the APK file on the device’s file system. Using any file explorer application, browse to the APK file and select it.

• Alternatively, upload the APK file on a web server and access it using the device’s web browser.

iOS

The \CustomizationTool\release\ios folder contains the customized IPA file.

To install the IPA file on an iOS device

1. Start iTunes and plug in your device.

2. Drag and drop the IPA file in the app section of iTunes.

3. In the device section of iTunes, select the application and install it.

Update Mobile Authenticator Studio

When generating binaries to update previous Mobile Authenticator Studio versions, you need to consider the following:

• For all Mobile Authenticator Studio editions, you must keep the same binary name and use the same certificate.