[bug] How to debug with released binary? #3638
-
Describe the bugI have a vue based app and it is running perfectly in development but the css file was missing in released windows binary. However, it's totally perfect on released macos binary. Does anyone experienced like this before? Or how should I debug with released binary? Is there're any way to open up a dev console in released binary? ReproductionNo response Expected behaviorNo response Platform and versionsOperating System - Windows, version 10.0.22000 X64
Webview2 - 99.0.1150.30
Visual Studio Build Tools:
- Visual Studio ���ɹ��� 2019
- Visual Studio Community 2019
Node.js environment
Node.js - 16.13.2
@tauri-apps/cli - 1.0.0-rc.5 (outdated, latest: 1.0.0-rc.7)
@tauri-apps/api - 1.0.0-rc.1 (outdated, latest: 1.0.0-rc.2)
Global packages
npm - 8.1.2
pnpm - 6.24.3
yarn - Not installed
Rust environment
rustup - 1.24.3
rustc - 1.59.0
cargo - 1.59.0
toolchain - stable-x86_64-pc-windows-msvc
App directory structure
/.git
/.vscode
/dist
/node_modules
/public
/src
/src-tauri
/test
App
tauri - 1.0.0-rc.3
tauri-build - 1.0.0-rc.3
tao - 0.6.2
wry - 0.13.2
build-type - bundle
CSP - unset
distDir - ../dist
devPath - http://localhost:8080/
framework - Vue.js (Quasar)
bundler - Webpack
|
Beta Was this translation helpful? Give feedback.
Answered by
xuchaoqian
Mar 8, 2022
Replies: 1 comment
-
Put "devtools" flag to Cargo.toml to enable "devtools" feature in release build. Just like this: tauri = { git = "https://github.com/tauri-apps/tauri.git", branch = "dev", features = ["devtools", "dialog-all", "macos-private-api", "path-all", "process-exit", "process-relaunch", "shell-open", "window-all"] } see the docs Mod Edit: code formatting |
Beta Was this translation helpful? Give feedback.
0 replies
Answer selected by
JonasKruckenberg
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Put "devtools" flag to Cargo.toml to enable "devtools" feature in release build. Just like this:
see the docs
Mod Edit: code formatting