--- title: "View and download built apps" slug: "masp-ug-view-and-download-built-apps-1-1" updated: 2026-09-28T08:29:33Z published: 2026-09-28T08:29:33Z canonical: "docs.onespan.com/masp-ug-view-and-download-built-apps-1-1" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.onespan.com/llms.txt > Use this file to discover all available pages before exploring further. # View and download built apps Completed builds are added to the list of available builds in the Build List page where, you can check the build status and view essential information. The page refreshes automatically every minute, but you can also refresh it manually by clicking Refresh in the page header. ## Available build information and list structure The list includes the builds of the last 7 days and provides the following build data: - Build name - Description - Operating system - Mobile Authenticator Studio version - Status Possible build statuses are: - Queued - In Progress - Success - Timeout - Failed - Expired - Timeout - Creation date and time (in UTC) Each row of this list corresponds to a build. You can sort the columns by the Build Name, Status, or Created at columns. The list is paginated to enable convenient navigation. For each completed build, a context menu with the available options for that build is provided. To open the menu and access the options, click the three dots at the end of the row. ## Build log The Mobile Authenticator Studio Portal provides logs for every completed build, i.e. builds with the status Success or Failed. For the other statuses, the build is in some form ongoing, e.g. pending or queued, and the log is only available once the build in question has completed. You can view the log via the build’s context menu. This build log contains the build name, the Mobile Authenticator Studio version used for the build, and the build status. In the log message itself, you can find the detailed logs. One log file corresponds to one build job and provides information such as the timestamp, a basic categorization in `INFO` or `ERROR`, and each line corresponds to one event. For a failed build the log provides reasons why it failed, and for successful builds the log lists the completed tasks. When a build fails because of a user error, the build is marked Failed and the Build List page displays an error message with details. This occurs for instance when you upload a customization file with syntax errors in the file. For instructions how to create a customization file and examples, see [JSON customization schemas](/mobile/docs/mas-5-ig-json-customization-schemas-5-8-0). For some builds, logs are not available because the portal cannot generate them when an unexpected error occurs during the build process, such as a timeout. In such cases, you can run another build using the same input files. ## Build artifacts: download and retention After a build has completed successfully, you can download the app-release.zip file from the build’s context menu in the build list. This archive contains the build artifacts: AAB and APK files for Android, and IPA files for iOS. You can access your builds at any time, as all builds are retained indefinitely in the portal’s database.