Ticket

**ZanPOS, Deansgate, Till 1.** First thing worth knowing: Till 1 and the Hub are the **same machine** at Deansgate — both records are 192.168.100.189. The Hub ticket raised 4h ago carries the identical symptom, so this is one screen and one fault, not two. **What I can and cannot say from the picture.** Our notes describe three screens the app itself can show: the attract/ordering screen, the pairing screen (**six digits**, no keyboard), and a PIN screen with its own keypad. **An email-and-password sign-in is none of them** — that is the branch panel (`/api/staff/auth/login`, web-admin), not the ZanPOS app. So the most likely thing is that the app is not what is drawn: a browser or another window is in front, or the app is not running at all and something else is on the desktop. I am not going to name a cause beyond that — our notes do not cover an email/password screen inside the app. **In the order somebody at the machine would do it:** 1. **Look at the screen and press Alt+Tab.** If the ordering app is behind a browser window, that is the whole fault — close it. 2. **Ask the machine, not the task:** `Get-Process zanpos_app | Select-Object Id, SessionId, StartTime` Exactly one process, `SessionId` 1 or higher. Zero processes = it is not running. Two = two launchers (`37-a-screen-is-started-one-way`). 3. **If it is running and `Responding` but has no window**, this is the pattern in `35-a-process-with-no-window`: read the first byte of `%APPDATA%\com.zanpos\zanpos_app\shared_preferences.json` — `7B` (`{`) is healthy, `00` is a torn write. Also look for a `shared_preferences.json.unreadable-<stamp>` file beside it; a stamp matching a recent update means the settings were moved aside and it came up unpaired. 4. **Starting it again: console session only.** `schtasks /Run /TN ZanPOSLaunch`, or the hub's `app-start` job. Anything launched over SSH lands in session 0, has no desktop, and dies — and the screenshot comes back black. 5. **Photograph it.** "Running" is not "working"; the picture is the proof. **To have it done from here:** Do → **Put the ordering app back on a screen** (`screen.restart-app`), shop **Deansgate**, screen **Till 1**, press Run. It stops the app if stuck, starts it in the right session and takes a picture. Then Do → **Look at one screen** (`screen.picture`) to confirm. One caution before pressing Run: this box is also the shop's hub. `update.ps1`/restart only stops `zanpos_app`, so the hub keeps printing — but know which machine you are touching. If the picture after that still shows email and password, do **not** guess further — say so on the ticket with what was ruled out, and read the machine's own log: `C:\ZanPOS\app.log` and `flutter.devlog.lines` inside `shared_preferences.json`.