Skip to content

[bug] tauri mobile build leaves a .cargo folder #6578

@Berrysoft

Description

@Berrysoft

Describe the bug

After I run tauri android dev or tauri android build, or tauri ios dev or tauri ios build, it leaves a .cargo folder with a config in the src-tauri folder. The config confuses cargo. For example, on Windows, the config set the default target to x86_64-pc-windows-msvc, and then simply running cargo build will compile binaries to target/x86_64-pc-windows-msvc/debug but not target/debug. This config is also not cross-platform because different OS uses different host target.

Reproduction

cargo tauri android init
cargo tauri android dev

Expected behavior

I don't understand why it generates such config. It shouldn't do that. We don't need to set host target manually at all.

Platform and versions

Environment
  › OS: Windows 10.0.22621 X64
  › Webview2: 111.0.1661.54
  › MSVC:
      - Visual Studio ???? 2022
  › Node.js: 18.15.0
  › npm: 9.5.0
  › pnpm: Not installed!
  › yarn: Not installed!
  › rustup: 1.25.2
  › rustc: 1.70.0-nightly
  › cargo: 1.70.0-nightly
  › Rust toolchain: nightly-x86_64-pc-windows-msvc

Packages
  › @tauri-apps/cli [NPM]: 2.0.0-alpha.3
  › @tauri-apps/api [NPM]: 2.0.0-alpha.1
  › tauri [RUST]: 2.0.0-alpha.4 (no manifest),
  › tauri-build [RUST]: 2.0.0-alpha.2 (no manifest),
  › tao [RUST]: 0.18.1 (no manifest),
  › wry [RUST]: 0.27.0 (no manifest),

App
  › build-type: bundle
  › CSP: unset
  › distDir: ../dist
  › devPath: http://localhost:5173/
  › framework: Vue.js
  › bundler: Vite

App directory structure
  ├─ dist
  ├─ node_modules
  ├─ public
  ├─ src
  └─ src-tauri

Stack trace

No response

Additional context

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    Status

    📬Proposal

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions