Overview 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.
Two sections in the sidebar answer questions across all projects. The Übersicht (Overview) shows what your customers have and what’s about to expire. Offen (Open) shows what’s still left to do after a build.
The Overview
The Overview answers the question: What’s in which store, and how far has the code moved on since? In the sidebar it says “Stand beim Kunden” (customer version) underneath, or, if something is expiring, how many credentials are affected.
Customer version
There’s a card for each project. It shows one row per configured store:
| Column | Content |
|---|---|
| Store | Google Play, App Store Connect, Microsoft Store or macOS |
| Version | last uploaded version with build number |
| Date | when it was uploaded, with “vor … Tagen” (… days ago) |
| Git | the build’s commit, the Git tag and how many commits have been added since |
“Code unverändert” (code unchanged) means nothing has happened on the branch since the upload. “12 Commits seitdem” (12 commits since) means the customer has an older version. The suffix “laut Store” (according to the store) shows that the information comes straight from the store API and not just from the Station’s own history.
Below the store rows is the letzte Build (last build) with preset, version, status and time. If no upload is set up for a project, it says Kein Upload eingerichtet (no upload set up).
Neu abfragen (query again) asks all stores again and re-checks the expiry dates.
Building all variants
Alle in die Warteschlange … (add all to queue) builds one preset per project with a single click, with upload if you like. That way all customers get the same version. How it works is described in Building and the queue.
Expiring credentials
Certificates, profiles and keys expire, and usually you only notice when a build or upload fails. The Station reads the expiry dates in advance. It checks:
| Credentials | Where the Station gets the date from |
|---|---|
| iOS distribution certificate | from the keychain, matching the team in the project.pbxproj |
| provisioning profile | from the installed profiles for the bundle ID |
| Android upload key | from the keystore named in android/key.properties |
| Partner Center key | from the date you enter in the store setup |
| Developer ID certificate | from the keychain, for projects with direct macOS distribution |
Everything is read only. For the Android keystore, the Station uses the password from key.properties and passes it to keytool only via an environment variable.
The traffic light
Each project card shows a coloured dot at the top right for that project’s credentials, with the most urgent case as text. Hover over it to see all entries with their dates.
| Colour | Meaning |
|---|---|
| green | everything valid |
| yellow | expires in less than 45 days |
| red | expires in less than 14 days or has expired |
| grey | date unknown |
Everything that’s yellow or red is also listed at the top of the Overview under Zugangsdaten, die bald ablaufen (credentials expiring soon), with how to renew it. For example: “In Xcode unter Settings › Accounts › Manage Certificates ein neues Apple-Distribution-Zertifikat anlegen.” (create a new Apple Distribution certificate in Xcode under Settings › Accounts › Manage Certificates).
If credentials expire in less than 14 days, macOS reports this with a notification once per app launch. After all, you don’t look at the Overview every day.
Offen: the work list
The Offen section collects all successful builds whose checklist hasn’t been fully ticked off, across all projects. Unlike the history, it’s not a record to look things up in, but a list to work through. The counter in the sidebar shows how many builds are open.
Each card shows:
- in the header: project, preset, version, branch and commit
- below that, Als Nächstes: (next) with the next open step
- the upload actions with the drag handle, without switching to another tab
- the checklist for ticking things off directly
- the build’s note, if there is one
Two buttons save clicks:
- „…” erledigt (“…” done) ticks off the next open step, with its name in the button.
- Alles abhaken (tick off everything) completes a build you uploaded outside the Station.
At the top you switch between Neueste zuerst (newest first) and Nach Projekt (by project). Once everything is done, it says Nichts offen (nothing open), with Zum Verlauf (to history) as the way to the completed builds.
If you upload via the Station, it ticks off “Version/Build-Nummer geprüft” (version/build number checked) and the upload step itself. What’s left is what only you can know, such as whether the customer has been informed. More on the checklist in Artifacts and upload.