4.5Auto-publish, versions, and history
Send every successful build to a store without a second click, and keep track of what went where.
Section 5 of 5 in this chapter
Auto-publish
The build form's When the build succeeds row lets you tick the stores a successful build should be sent to. The upload starts the moment packaging finishes, for every build in a matrix, with nothing else to press.
A store you have not finished configuring shows as Set up rather than as something you can tick by mistake and discover an hour later.
This is what turns shipping a playtest build from an evening's work into a thing you do because it is Tuesday.
Version numbers
The version box is pre-filled with the next version after your last successful build, and it warns you if the number you typed has already been built for that platform and configuration.
Shipping two different builds under one version is easy to do and genuinely hard to undo: bug reports arrive tagged with a version that describes two different sets of bytes, and there is no way to tell them apart afterwards.
Publish history and logs
Every upload is recorded — which build, which store, when, and how it ended. The full log is readable in the app, and successful uploads carry a deep link to the store page you sent them to.
If an upload stalls, the app notices and says so rather than sitting on a progress bar that has not moved in twenty minutes.