Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[bug] Launch failed but no error logs were generated. #10366

Closed
qq253498229 opened this issue Jul 23, 2024 · 2 comments
Closed

[bug] Launch failed but no error logs were generated. #10366

qq253498229 opened this issue Jul 23, 2024 · 2 comments
Labels
platform: Windows status: needs triage This issue needs to triage, applied to new issues type: bug

Comments

@qq253498229
Copy link

qq253498229 commented Jul 23, 2024

Describe the bug

I am developing an application with tauri and steamworks-rs, and I forgot to copy the steam_api64.dll and steam_api64.lib files to the debug directory when I started it, so the application did not start as I wish.

npm run dev

> happy-cultivation-tauri@0.0.0 dev
> tauri dev

     Running BeforeDevCommand (`npm run start`)

> happy-cultivation-tauri@0.0.0 start
> ng serve

Initial chunk files | Names          |  Raw size
styles.css          | styles         | 700.77 kB | 
polyfills.js        | polyfills      |  88.34 kB | 
main.js             | main           |  11.65 kB | 
chunk-RW2SMIYW.js   | -              |   1.98 kB | 

                    | Initial total  | 802.74 kB

Lazy chunk files    | Names          |  Raw size
chunk-CANKSL6J.js   | welcome-routes |   3.96 kB | 

Application bundle generation complete. [3.119 seconds]

Watch mode enabled. Watching for file changes...
NOTE: Raw file sizes do not reflect development server per-request transformations.
  ➜  Local:   http://localhost:14200/
        Info Watching D:\src\game\happy-cultivation-tauri\src-tauri for changes...
   Compiling vswhom-sys v0.1.2
   Compiling vswhom v0.1.0                                  
   Compiling embed-resource v2.4.2                          
   Compiling tauri-winres v0.1.1                            
   Compiling tauri-build v1.5.3                             
   Compiling happy-cultivation-tauri v0.0.0 (D:\src\game\happy-cultivation-tauri\src-tauri)
    Finished `dev` profile [unoptimized + debuginfo] target(s) in 5.87s

What puzzles me is that the console did not display any error logs, which caused me to waste a lot of time troubleshooting this issue.

I would like to know how to display the error logs.

Reproduction

https://github.com/qq253498229/tauri-error001

No response

Expected behavior

No response

Full tauri info output

npm run tauri info

> happy-cultivation-tauri@0.0.0 tauri
> tauri info


[✔] Environment
    - OS: Windows 10.0.22631 X64
    ✔ WebView2: 126.0.2592.113
    ✔ MSVC: Visual Studio Community 2022
    ✔ rustc: 1.79.0 (129f3b996 2024-06-10)
    ✔ cargo: 1.79.0 (ffa9cf99a 2024-06-03)
    ✔ rustup: 1.27.1 (54dd3d00f 2024-04-24)
    ✔ Rust toolchain: stable-x86_64-pc-windows-msvc (default)
    - node: 20.10.0
    - pnpm: 9.5.0
    - yarn: 1.22.21
    - npm: 10.2.3

[-] Packages
    - tauri [RUST]: 1.7.1
    - tauri-build [RUST]: 1.5.3
    - wry [RUST]: 0.24.10
    - tao [RUST]: 0.16.9
    - @tauri-apps/api [NPM]: 1.6.0
    - @tauri-apps/cli [NPM]: 1.6.0

[-] App
    - build-type: bundle
    - CSP: unset
    - distDir: ../dist/happy-cultivation-tauri/browser
    - devPath: http://localhost:14200/
    - framework: Angular
    - bundler: Webpack

Stack trace

No response

Additional context

No response

@qq253498229 qq253498229 added status: needs triage This issue needs to triage, applied to new issues type: bug labels Jul 23, 2024
@qq253498229
Copy link
Author

I have tried setting RUST_BACKTRACE=1, but there are still no error logs.

$env:RUST_BACKTRACE = 1
echo $env:RUST_BACKTRACE 
1

@FabianLars
Copy link
Member

I think this is a windows issue. If you build the app and try to run the app binary from inside powershell it also silently fails. It will only complain about a missing dll if you double click on the exe. Here's one of the GitHub issues i found PowerShell/PowerShell#16468 (auto closed by the inactivity bot but it's not resolved).

@FabianLars FabianLars closed this as not planned Won't fix, can't repro, duplicate, stale Jul 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
platform: Windows status: needs triage This issue needs to triage, applied to new issues type: bug
Projects
None yet
Development

No branches or pull requests

2 participants