Here your app stops being a design and becomes an actual installable file – and, if you choose, gets submitted to the App Store and Google Play. Building and submitting aren’t two separate jobs here: they’re two choices inside one five-step wizard. Most day-to-day editing never brings you to this page at all. You’ll come here for your first build, and after that only when you genuinely need a new one.
What Build & Deploy covers
Connect GitHub before you build comes first: a one-time, workspace-wide connection that keeps the Trigger Build button locked until it’s done. After that, Build your app – and submit it to the store walks the whole wizard end to end – checking requirements, choosing platforms and a version number, deciding between Build Only and Build & Deploy, writing release notes, and starting the build. It also covers what to do once the build finishes: where the logs live and how to download what was produced.
The last article is for when a build comes back Failed, which is more common on a first attempt than you’d think and usually straightforward to diagnose.
Before you start
GitHub needs to be connected, and the requirements in Publishing Setup all need to pass – the wizard checks them live on its first step and won’t let you continue until they do.