Manual / When something looks wrong
When something looks wrong
- For
- a controller who is not getting the screen they expected
- Status
- current
- Covers
- the banner column, greyed and padlocked tabs, an empty map, and the version chip
- Last checked against the app
0963ac5(2026-08-19)
Most of what looks like a fault in this app is the app telling you something. A control is missing because the thing behind it is missing. A bus is grey because nobody published a prediction for it. A tab is faded because no roster has been loaded. This section is how to tell those apart from an actual fault, and what to do with each.
Start here
Three questions, in this order. They resolve most of it in under a minute.
- Is there a banner under the top bar? It is the app's own account of what is wrong, and it is more specific than anything on this page. See The banners, one by one.
- Is the control you want missing, or present and refusing? Missing means this deployment has no source for it. Present and refusing — faded, or wearing a padlock — means it exists and something is in the way, and hovering it says what. See A tab is greyed out.
- Has the app changed under you? The chip in the top bar carries the version you are running. See What is new in this release.
The pages here
| Page | What it answers |
|---|---|
| The banners, one by one | The four notices, what each is telling you, and which one you should not dismiss |
| A tab is greyed out | Faded, padlocked and absent are three different states with three different answers |
| The map looks wrong | No stops, no buses, grey buses, all-blue buses, a vanished overlay |
| What is new in this release | The version chip, the update notice and the What's new dialog |
| Who to tell | There is no report button. What to send instead, and what never to send |
One rule that covers most of it
This app hides what it cannot do rather than offering a control that fails. Every optional part — the live buses, each overlay, the roster, the diversion register, the traffic radio — appears only where the deployment has been given what it needs. So the honest first reading of a missing button is "this copy of the app was not given that", not "it is broken".
The cost of that design is the thing this section exists for: a missing feature and a feature that is not working look identical from the outside. The pages here are how you tell them apart.