Skip to content

UNBLOCK Desktop 0.1.1

Latest

Choose a tag to compare

@Viraj0518 Viraj0518 released this 15 Aug 23:10
381a148

Supersedes desktop-v0.1.0, which is left in place for reference. If you are installing on Windows, take this build — 0.1.0's installer could not finish first-run setup on a clean machine.

Built from unblock_desktop main @ 0279515.

Fixed

  • Windows: fresh installs no longer die at the SET UP step. The NSIS installer unpacks the app into %LOCALAPPDATA%\UNBLOCK — which is the very directory first-run setup copies the bundled CLI into. The copy was therefore a self-copy, CopyFileEx refused it with OS error 32, and the first-run wizard failed on every clean Windows install. The new guard skips the copy only when both paths canonicalize and are proven equal; when it cannot tell, it still copies, so the failure mode is biased toward doing the work. Fix authored by @Viraj0518 (unblock_desktop PR 48, commit 20eb3a7) and landed here via PR 67. Independently verified on real Windows hardware by the Windows lane: fresh install completed, registry shows 0.1.1, the previously-fatal SET UP step cleared, no OS error 32.
  • macOS: no more keychain password prompt on every update. The CLI credential now lives in a data-protection keychain.
  • Sign-in no longer flashes "signed out" at launch. /api/session is now three-state and reports pending while the keychain read is still blocked, instead of reporting a signed-out session.
  • 15+ silent /api dead legs removed. The web worker's route table is now ported into the desktop's own router.

Downloads

  • macOS (Apple Silicon)UNBLOCK-0.1.1-macos-arm64.dmg. Developer ID signed, notarized, and stapled; Gatekeeper-verified with quarantine set.
  • Windows (x64)UNBLOCK_0.1.1_x64-setup.exe. NSIS installer with the embedded WebView2 bootstrapper. Not code-signed yet, so SmartScreen will show a blue "Windows protected your PC" warning on first run — choose More info → Run anyway. This is a known, deliberate gap while Windows signing is arranged, not a sign that the download is broken. Verify the file against SHA256SUMS.txt below if you want to confirm it is the build we published.

Verify downloads against SHA256SUMS.txt.