0.5.22 Windows: webview points at build-runner path -> ERR_FILE_NOT_FOUND on launch

[loviswaternakamoto]

Version: Buzz desktop 0.5.22 (Buzz_0.5.22_x64-setup_alpha-unsigned.exe, also via in-app update from 0.5.20)
OS: Windows 11 x64, WebView2 runtime current

Symptom: on launch the window shows the WebView2 "File not found / ERR_FILE_NOT_FOUND" page instead of the app.

Observed: with WEBVIEW2_ADDITIONAL_BROWSER_ARGUMENTS=--remote-debugging-port=9223, GET /json reports the page URL as
file:///C:/Users/RUNNER~1/AppData/Local/Temp/buzz-tauri-package-assets-izi1rV/dist — a path on the CI build runner, not on the user's machine.

Repro: clean install of 0.5.22 (kill app, run installer /S, relaunch) reproduces every time.

Workaround: roll back to 0.5.20 — the same check then reports http://tauri.localhost/ and the app loads normally, workspace and agents intact.

Suggested cause: the packaged frontend asset path is not being rewritten at bundle time for the Windows target, so the webview navigates to the runner's temp dist directory.

[MalakezDarnos]

Yup, ran in to the same problem, just updated and got the error file not found on launch.

[gcapnias]

Possible duplicate of #7362

[Cookiebubba]

Confirmed on another Windows 11 x64 machine (0.5.20-era install updated in-app to 0.5.22 on 2026-09-05).

• WebView2 debug port shows the page URL as file:///C:/Users/RUNNER~1/AppData/Local/Temp/buzz-tauri-package-assets-izi1rV/dist, matching the report above. Steering the webview to http://tauri.localhost/ returns asset not found: index.html, so the bundle really has zero embedded assets rather than a bad start URL. buzz-desktop.exe is 84.8 MB in 0.5.22 vs 95.4 MB in 0.5.19.
• Quick check for anyone triaging: the broken Windows installer is 43.8 MB; working ones (0.5.19, 0.5.20) are ~54 MB.
• Rolling back with the updater's cached Buzz-0.5.19-installer.exe /S restores the app with workspace, agents and identity intact. No identity re-import was needed here: the secrets.buzz-desktop Credential Manager entry already used the JSON blob layout from an earlier version, and secret_store.rs is identical between the desktop-v0.5.19 and desktop-v0.5.22 tags. So the keyring caveat in [desktop][windows] 0.5.22 renders only "ERR_FILE_NOT_FOUND" on launch; 0.5.20 works — plus keyring format not backward-readable #7362 seems to depend on which version last wrote the entry, not on 0.5.22 itself.
• After rollback the sidebar immediately offers 0.5.22 again via "Ready to update"; users need to dismiss it until a release with fix(desktop): keep packaged frontendDist relative so Windows embeds assets #7177 ships.

Root cause and fix as in #7177 (absolute Windows frontendDist path parses as a URL with scheme c:).

[ajuroshan]

Hit this on Windows 11 x64 with a clean 0.5.22 install.

Worth recording that the bundle genuinely has no assets in it, rather than just a wrong start URL. Launching with WEBVIEW2_ADDITIONAL_BROWSER_ARGUMENTS=--remote-debugging-port=9222, the page target reports:

file:///C:/Users/RUNNER~1/AppData/Local/Temp/buzz-tauri-package-assets-izi1rV/dist

Steering the webview to http://tauri.localhost/ over CDP doesn't recover it. Tauri's own asset handler answers:

asset not found: index.html

So tauri-codegen embedded zero assets, which matches the C: scheme parse described in #7177.

Binary sizes agree — buzz-desktop.exe is 84,847,616 bytes in 0.5.22 against 95,371,264 in 0.5.20. The missing ~10 MB is the frontend.

The Rust side is entirely healthy while this happens: it logs its persisted identity, binds the media proxy on 127.0.0.1, and downloads the STT/TTS models normally. Only the webview is empty, so the process exits 0 and nothing in the logs looks wrong. That's probably why it got through CI.

Workaround for anyone stuck: reinstall a previous release over the top, Buzz_0.5.20_x64-setup_alpha-unsigned.exe /S. Workspace, agents and identity all survive — I compared the pubkey the app logs at boot before and after and it's unchanged. The updater offers 0.5.22 again immediately afterwards, so it has to be dismissed until a fixed build is out.

#7177 addresses the cause and currently reports mergeable/clean with CI green.

[amv101]

Installing the new v.0.5.23 seems to have resolved the issue for me.

https://github.com/block/buzz/releases?page=1#release-desktop-v0.5.23