#thread '<unnamed>' panicked

6 messages · Page 1 of 1 (latest)

glad bay
#

Finished dev [unoptimized + debuginfo] target(s) in 0.81s
thread '<unnamed>' panicked at 'called Result::unwrap() on an Err value: Os { code: 216, kind: Uncategorized, message: "The version of %1 is incompatible with the version of Windows you are running. Check the computer's system information, and then contact the software publisher." }', src\interface\rust\desktop.rs:57:63
note: run with RUST_BACKTRACE=1 environment variable to display a backtrace

what is the problem and how can i fix this?

jaunty kite
#

please post the output of the tauri info command. Typically this error means that your visual studio build tools installation is too old (== not 2019 or 2022)

glad bay
# jaunty kite please post the output of the `tauri info` command. Typically this error means t...
  1. I just installed the build tools like 1h ago (2022)
  2. The Tauri command doesnt work for me i have to do pnpm tauri

but this is the result of pnpm tauri info:

[✔] Environment
    - OS: Windows 10.0.22621 X64
    ✔ WebView2: 113.0.1774.57
    ✔ MSVC:
        - Visual Studio Build Tools 2022
        - Visual Studio Build Tools 2017
    ✔ rustc: 1.69.0 (84c898d65 2023-04-16)
    ✔ Cargo: 1.69.0 (6e9a83356 2023-04-12)
    ✔ rustup: 1.26.0 (5af9b9484 2023-04-05)
    ✔ Rust toolchain: stable-x86_64-pc-windows-msvc (default)
    - node: 19.9.0
    - pnpm: 8.6.0
    - yarn: 1.22.19
    - npm: 9.6.7

[-] Packages
    - tauri [RUST]: 1.3.0
    - tauri-build [RUST]: 1.3.0
    - wry [RUST]: 0.24.3
    - tao [RUST]: 0.16.2
    - @tauri-apps/api [NPM]: not installed!
    - @tauri-apps/cli [NPM]: 1.3.1

[-] App
    - build-type: bundle
    - CSP: unset
    - distDir: ../.output/public
    - devPath: http://localhost:3000/
    - framework: Vue.js (Nuxt)
    - bundler: Webpack
jaunty kite
#

I just installed the build tools like 1h ago (2022)
According to tauri info you also have 2017 installed so i bet that 2017 is set as the default.
You can permanently, or temporarily (per terminal) change it afaik, but i don't know how without uninstalling 2017 but google should be able to help hopefully

#

or maybe it does set the new installation at default but you have to restart the computer to make it work idk

glad bay