You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
About 1 week ago, my tauri app stopped working and panicked at startup with a runtime exception, whereas it has been working fine for the last couple of months.
I tried figuring out the issue, and ended up creating a new vanilla app (npm, vite, typescript) with the tauri create app npm module.
The vanilla app also fails with the same runtime exception:
$ RUST_BACKTRACE=1 npm run tauri dev
footauri@0.0.0 tauri
tauri dev
Running BeforeDevCommand (`npm run dev`)
footauri@0.0.0 dev
vite
VITE v5.2.11 ready in 207 ms
➜ Local: http://localhost:1420/
➜ Network: use --host to expose
Info Watching C:\tauri\footauri\src-tauri for changes...
Updating crates.io index
Blocking waiting for file lock on build directory
Compiling footauri v0.0.0 (C:\tauri\footauri\src-tauri)
Finished dev [unoptimized + debuginfo] target(s) in 4.85s thread 'main' panicked at src\main.rs:14:10:
error while running tauri application: Runtime(CreateWebview(WebView2Error(WindowsError(Error { code: 0x800700AA, message: The requested resource is in use. }))))
It seems to be caused by a new WebView2 version, installed by auto update.
I tried to rollback the version by using the bundle/windows config in tauri.json.config, but the version used for dev is still the same.
Online, it says it might be due to corrupt windows files, but I run a filesystem check, and the issue still arises after that.
I updated node.js, webview2, tauri.. but the issue is once again still there.
Nothing obvious on my side, so any help would be greatly appreciated :-)
Thanks.
Reproduction
create and launch a vanilla tauri app typescript/vite/npm with the env info below, and it should panic at launch, with an instantaneous runtime exception.
Expected behavior
The default vanilla tauri app should launch and work correctly.
it might be an issue with my laptop - I am unable to update webview2, with the same error code. Probably a corrupt system file? I will try to re-install windows. Thanks for your help!
I found the issue: it is corrupted files in the webview2 user data directory.
If this happens again, one just needs to rename or delete directory C:\Users<user>\AppData\Local\com.tauri.dev
Describe the bug
Hi,
About 1 week ago, my tauri app stopped working and panicked at startup with a runtime exception, whereas it has been working fine for the last couple of months.
I tried figuring out the issue, and ended up creating a new vanilla app (npm, vite, typescript) with the tauri create app npm module.
The vanilla app also fails with the same runtime exception:
$ RUST_BACKTRACE=1 npm run tauri dev
VITE v5.2.11 ready in 207 ms
➜ Local: http://localhost:1420/
➜ Network: use --host to expose
Info Watching C:\tauri\footauri\src-tauri for changes...
Updating crates.io index
Blocking waiting for file lock on build directory
Compiling footauri v0.0.0 (C:\tauri\footauri\src-tauri)
Finished dev [unoptimized + debuginfo] target(s) in 4.85s
thread 'main' panicked at src\main.rs:14:10:
error while running tauri application: Runtime(CreateWebview(WebView2Error(WindowsError(Error { code: 0x800700AA, message: The requested resource is in use. }))))
It seems to be caused by a new WebView2 version, installed by auto update.
I tried to rollback the version by using the bundle/windows config in tauri.json.config, but the version used for dev is still the same.
Online, it says it might be due to corrupt windows files, but I run a filesystem check, and the issue still arises after that.
I updated node.js, webview2, tauri.. but the issue is once again still there.
Nothing obvious on my side, so any help would be greatly appreciated :-)
Thanks.
Reproduction
create and launch a vanilla tauri app typescript/vite/npm with the env info below, and it should panic at launch, with an instantaneous runtime exception.
Expected behavior
The default vanilla tauri app should launch and work correctly.
Full
tauri info
outputStack trace
Additional context
No response
The text was updated successfully, but these errors were encountered: