Understanding Build Execution Time
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.
There are many reasons why build duration can be higher when using App Center Build:
- When running your build locally, many things are cached, including NuGet packages, pods, dependencies, and so on. In App Center, we always do a clean build, and also redownload dependencies not already included in your repository.
- Build configuration differences between your local build compared to App Center. For example, a signed device build typically takes longer than a simulator build.
- The CPU power of your development machine may be higher than the CPU of our VMs.
- More builds queued then the build concurrency for your organization.
- If your build includes other production tasks, like running tests or publishing binaries, those can also increase the build time.
Why do I get an extended build time when Run launch test on a device is enabled?
We run the test as part of the build operation, which gives the added build time. While App Center Test validates your app, extra tasks occur like signing, checking permissions, and so on. After that it's time to wait for a device. Once started, it runs the app on a real device, which takes time. And lastly, we move test logs, screenshots into the cloud.
Expect an additional 10 minutes of build time.