Summary
During v0.12.4 release testing, the Swift macOS app reached its main Dashboard window after x0xd became healthy, but the window was not visible on the active desktop.
Evidence
- Release app:
/Users/davidirvine/Applications/Communitas-Swift-0.12.4.app
- Process:
Communitas, pid observed as 61648
x0xd health endpoint was healthy: {"ok":true,"status":"healthy","version":"0.21.2"}
- System Events reported one Communitas window named
Dashboard, but with an offscreen/invalid-looking position such as pos=771-956 and size 1200820 (interpreted as a list formatting issue, likely {77, -956} / {1200, 820}).
- Attempts to activate by bundle id, set process frontmost, raise the window, and set
AXPosition/AXSize did not bring the window into the visible desktop.
- Computer Use also stopped returning the Swift accessibility tree and returned an internal
remoteConnection marker for the Swift release path.
Expected
After onboarding completes or daemon recovery succeeds, the Swift main window should be visible on the active desktop with sane bounds.
Actual
The app process runs and has a Dashboard window, but the window is effectively inaccessible/offscreen, blocking UI testing and user interaction.
Notes
This happened after working around issue #20 by creating temporary ~/.x0x/bin symlinks to the installer-produced ~/.local/bin binaries and starting x0xd successfully.
Summary
During v0.12.4 release testing, the Swift macOS app reached its main
Dashboardwindow after x0xd became healthy, but the window was not visible on the active desktop.Evidence
/Users/davidirvine/Applications/Communitas-Swift-0.12.4.appCommunitas, pid observed as61648x0xdhealth endpoint was healthy:{"ok":true,"status":"healthy","version":"0.21.2"}Dashboard, but with an offscreen/invalid-looking position such aspos=771-956and size1200820(interpreted as a list formatting issue, likely{77, -956}/{1200, 820}).AXPosition/AXSizedid not bring the window into the visible desktop.remoteConnectionmarker for the Swift release path.Expected
After onboarding completes or daemon recovery succeeds, the Swift main window should be visible on the active desktop with sane bounds.
Actual
The app process runs and has a
Dashboardwindow, but the window is effectively inaccessible/offscreen, blocking UI testing and user interaction.Notes
This happened after working around issue #20 by creating temporary
~/.x0x/binsymlinks to the installer-produced~/.local/binbinaries and starting x0xd successfully.