Skip to content

[bug] How to debug with released binary? #3637

@red010182

Description

@red010182

Describe the bug

I 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?

Reproduction

No response

Expected behavior

No response

Platform and versions

Operating 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


### Stack trace

_No response_

### Additional context

_No response_

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions