Редагувати

Build results

  • Стаття

Important

Visual Studio App Center is scheduled for retirement on March 31, 2025. While you can continue to use Visual Studio App Center until it is fully retired, there are several recommended alternatives that you may consider migrating to.

Learn more about support timelines and alternatives.

The build results give you rich information about the status of your build. You can download your successful build or only the symbols to use for crash reporting. If it fails, you can investigate the logs to solve build issues.

After a build has been triggered, it can be in the following states:

  • queued - the build is in a queue waiting for resources to be freed up.
  • building - the build is running the predefined tasks.
  • succeeded - the build is completed and it's succeeded
  • failed - the build completed, but failed. You can troubleshoot what went wrong by inspecting the build logs.
  • canceled - the build has been canceled by a user action or it's timed out

1.1. The AppPackages

Building your app for Release will result in a folder called "AppPackages" that contains a .appxupload file for the store and the Test folder that contains the .appxbundle files for sideloading, one for each platform.

App Center always generates an app bundle. However, Debug builds aren't meant to be used for sideloading. You won't get the .appxupload file and the provided .appxbundle files in the Test folder don't contain required dependencies.

1.2. The symbols files

The .appxsym files contain the debug symbols for the app. There's one symbols file for each platform your app supports.

1.3. Build logs

For a completed build (succeeded or failed), download the logs to understand more about how the build went. App Center provides an archive with the following files:

|-- 1_build.txt (this is the general build log)
|-- build (this folder contains a separate log file for each build step)
    |-- <build-step-1> (e.g. 2_Get Sources.txt)
    |-- <build-step-2> (e.g. 3_Pod install.txt)
    |--
    |-- <build-step-n> (e.g. n_Post Job Cleanup.txt)

The build step specific logs (located in the build directory of the archive) are helpful for troubleshooting and understanding in what step and why the build failed.