Build Station help
Everything from installation to store upload
Here you find the complete documentation. Start with the first steps or jump straight to the topic you need. The app itself is in German, so button names are given as they appear in the app.
Getting started
Getting started
Install the iw Build Station, set it up on first launch and build your first Flutter project, from requirements to your first artifact.
Read moreThe interface
How the Build Station window is laid out: sidebar, project list, the Build, History and Codemagic tabs, the status bar and keyboard shortcuts.
Read moreAdding projects
The project assistant, a buildstation.json to check in, adding missing credentials, and building two customer variants from one folder via Git branch.
Read moreBuilding
Presets
Presets are named build configurations: platform, mode, flavor, Dart defines, env and pre-steps, with a live command preview and a dry run.
Read moreCustom scripts and web builds
Shell scripts as a build step: the BS_* variables, reporting artifacts with BUILDSTATION_ARTIFACT, build_web.sh and auto-committing web builds.
Read moreBuilding and the queue
Start builds in the Build tab, check version and build number, change values for a single run, queue builds and build all customer variants at once.
Read moreWhen a build fails
Known error patterns with cause and fix, one-click repairs, automatic change suggestions as a diff and the optional AI repair with Claude.
Read moreVersions and updates
Update dependencies with pub upgrade, analyze before building, apply Flutter hotfixes, raise the Android API level and align JDK, Gradle and AGP.
Read moreShipping
Artifacts and upload
Where finished builds land and how they're named, the per-build checklist, all upload routes at a glance, release notes, Git tags after upload and auto-upload.
Read moreGoogle Play
Upload AAB and APK directly via the Google Play Developer API: create a service account, grant it access in the Play Console, pick a track, test it.
Read moreApp Store and TestFlight
Upload IPA files to TestFlight with xcrun altool and an App Store Connect key (.p8), with validation, release notes and Transporter as an alternative.
Read moreMicrosoft Store
Submit a finished MSIX to the Microsoft Store via the Partner Center API: create an Entra app, enter the Store ID and keep an eye on key expiry.
Read moreDistributing macOS apps
Distribute Flutter macOS apps via the Mac App Store or directly: Developer ID, notarization, DMG via GitHub release or webhook, and Sparkle updates.
Read morefastlane
Keep using your existing fastlane setups: fastlane supply for Google Play or your own lane for Android and iOS, with an installation assistant.
Read moreMore
Codemagic
Codemagic in the Build Station: store your token, link an app, auto-build on push, start builds, download artifacts and check your codemagic.yaml.
Read moreMCP server for AI assistants
Through the MCP server, AI assistants like Claude Code start local and Codemagic builds, read logs, upload builds and repair failed ones.
Read moreRemote access in the browser
Run the Build Station on one Mac and use it from a browser: with a license and password, port 8787, your own HTTPS certificate and downloads.
Read moreOverview and work list
The Overview shows which version each customer has and which certificates are expiring. Offen collects builds with steps still left to do.
Read moreFreeing up space
Clear build folders, pods and Gradle caches, find old simulators, NDKs and Flutter versions, and clean up automatically after a build.
Read moreSettings and security
All Build Station settings, where configuration and logs are stored, what's kept in the keychain and what is sent to which services.
Read moreHelp
License
One project works without a license; a license unlocks unlimited projects and remote access. Here's how to request one and enter it in the app.
Read moreTroubleshooting
Solutions to common problems: fvm not found, project folder not readable, broken CocoaPods, no artifact detected or a failed upload.
Read more