[bug] Cargo.lock file is version 4 when using with Dioxus
luis-prates opened this issue · 1 comments
luis-prates commented
Describe the bug
When creating a project using Dioxus as the frontend, the resulting Cargo.lock file shows version = 4
at the top, which causes the build to fail. When manually changing the version to 3 the build is successful.
Reproduction
- Run
cargo create-tauri-app
- Choose project name, identifier, Rust as the frontend language, and Dioxus as the UI template
- Run
cargo tauri dev
Expected behavior
The app is expected to be built successfully.
Full tauri info
output
[✔] Environment
- OS: Windows 10.0.22631 x86_64 (X64)
✔ WebView2: 129.0.2792.89
✔ MSVC:
- Visual Studio Build Tools 2019
- Visual Studio Build Tools 2022
✔ rustc: 1.83.0-nightly (1bc403daa 2024-10-11)
✔ cargo: 1.83.0-nightly (15fbd2f60 2024-10-08)
✔ rustup: 1.27.1 (54dd3d00f 2024-04-24)
✔ Rust toolchain: nightly-x86_64-pc-windows-msvc (environment override by RUSTUP_TOOLCHAIN)
- node: 18.16.0
- pnpm: 9.4.0
- npm: 9.6.5
[-] Packages
- tauri 🦀: 2.0.3
- tauri-build 🦀: 2.0.1
- wry 🦀: 0.46.0
- tao 🦀: 0.30.3
- tauri-cli 🦀: 2.0.3
[-] Plugins
- tauri-plugin-shell 🦀: 2.0.1
[-] App
- build-type: bundle
- CSP: unset
- frontendDist: ../dist
- devUrl: http://localhost:1420/
Stack trace
Running BeforeDevCommand (`dx serve --port 1420`)
Warn Waiting for your frontend dev server to start on http://localhost:1420/...
👑 Build done.
thread 'main' panicked at C:\Users\mine\.cargo\registry\src\index.crates.io-6f17d22bba15001f\manganis-cli-support-0.2.4\src\manifest.rs:51:51:
called `Result::unwrap()` on an `Err` value: Parse("parse error: invalid Cargo.lock format version: `4`\n")
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
Error The "beforeDevCommand" terminated with a non-zero status code.
Additional context
No response
amrbashir commented
This is an issue with Dioxus CLI, please report the issue in their GitHub issues.