Skip to content

Desktop: Windows launch and physical USB acceptance #994

Closed as not planned
Closed as not planned

Description

@timohueser

Remaining desktop acceptance

The desktop CI builds the release app on Linux, macOS and Windows. #1727/#1729 also prove the actual Linux executable launches its embedded frontend, exercises catalog IPC and shuts down. macOS has manual device evidence from #957.

Remaining:

  • Launch the real release app on Windows. Confirm its frontend and catalog, not just compilation.
  • On Windows and Linux, connect the physical device and upload one route. Check WinUSB binding on Windows and the actual udev setup on Linux.
  • Record only the per-OS setup steps that these checks establish in the desktop README.

#993 owns the pending USB PID allocation and identifier change. Installers, signing and updater design stay deferred in #1518. #1978 S6 coordinates Windows acceptance.

No cross-OS or hardware acceptance is claimed by this issue audit.

Historical scope and evidence — use the current work above

Split out of #908, which keeps installers, auto-update and the signing decision (deferred — no
launch planned soon).

The near-term bar for the desktop app is just this: it builds and launches on macOS, Windows and
Linux.
Not packaged, not signed, not auto-updating — launched, showing its window, talking to a
device.

What CI now proves

The desktop matrix builds and tests the release app on Linux, macOS and Windows. The Linux end-to-end job added in #1727 / #1729 downloads that release executable, launches its embedded custom-protocol frontend under Xvfb and an isolated D-Bus session, exercises the region picker and Rust catalog IPC with a loopback fixture, and checks clean shutdown. PR CI run 34789369813 passed, and its screenshot, request log and result were inspected.

This is software launch evidence. It does not establish physical USB behavior. The runtime failure found in #957 remains the reason that compilation and device acceptance must be separate gates.

Status

Scope

  • Launch the app on a Linux desktop and on Windows: window opens, the frontend loads over the
    tauri:// protocol (i.e. custom-protocol did its job — a blank window is the classic failure),
    the region picker and the catalog render.
  • Plug in a device on each: it enumerates, the header chip connects, one route uploads.
  • Write down whatever each OS needs first (the udev rule on Linux; whatever Windows asks for), in
    apps/obc-desktop/README.md.
  • If anything is broken, fix it here — this is the issue that makes "builds on three OSes" mean
    something.

Acceptance

  • The app launches and shows its real frontend on all three OSes.
  • A device is detected and one route lands on it from each.
  • The README's per-OS first-run steps match what actually happened.

Software-only closeout — 2026-09-14

The bounded Linux software launch child #1727 / #1729 is complete and merged after independent review and green CI. The actual release app selected Switzerland at 994 B through six native catalog requests and then exited. Windows launch, physical enumeration and route upload on the supported operating systems remain open. No local board or phone was accessed.

Activity

  1. changed the title [-]The desktop app builds AND launches on all three OSes (CI only proves it builds)[/-] [+]Desktop: Windows launch and physical USB acceptance[/+] on Oct 4, 2026
  2. timohueser commented on Nov 20, 2026

    @timohueser
    OwnerAuthor

    Closed in the backlog cleanup as obsolete: the desktop app was deleted in #3403 (builder/desktop/ is gone). The one check that is left (Chrome WebUSB on Windows through WinUSB/MS OS 2.0, and on Linux with the builder/usb/linux udev rule) is a line in the acceptance checklist #1978.


    Generated by Claude Code

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions