[bug] [macOs] Blank screen with default Tauri/Preact boilerplate

[FaureAlexis]

Describe the bug

Hey there, I am getting started with Tauri, and I got an issue:

• I create the app using create-tauri-app or manually
• I run the cargo tauri dev
• I got a white screen:

(the vite server is running fine)

Thanks for your help !

Reproduction

Use the default vite Preact/tauri boilerplate on macos

Expected behavior

No response

Full tauri info output

Tauri info:
[✔] Environment
    - OS: Mac OS 14.2.1 X64
    ✔ Xcode Command Line Tools: installed
    ✔ rustc: 1.75.0 (82e1608df 2023-12-21)
    ✔ cargo: 1.75.0 (1d8b05cdd 2023-11-20)
    ✔ rustup: 1.26.0 (5af9b9484 2023-04-05)
    ✔ Rust toolchain: stable-aarch64-apple-darwin (environment override by RUSTUP_TOOLCHAIN)
    - node: 18.0.0
    - pnpm: 8.8.0
    - npm: 8.6.0

[-] Packages
    - tauri [RUST]: 1.5.4
    - tauri-build [RUST]: 1.5.1
    - wry [RUST]: 0.24.7
    - tao [RUST]: 0.16.5
    - tauri-cli [RUST]: 1.5.9
    - @tauri-apps/api [NPM]: 1.5.3
    - @tauri-apps/cli [NPM]: 1.5.9

[-] App
    - build-type: bundle
    - CSP: unset
    - distDir: ../dist
    - devPath: http://localhost:1420/
    - framework: React
    - bundler: Vite

webkit version: 19617.1.17.11.12

Stack trace

No response

Additional context

No response

[FaureAlexis]

I tested with every front-end (Vanilla JS, React, Preact, Rust) an the same issue with everything.

[FabianLars]

If you right click on the window does it show a context menu? If it does, can you open the devtools from there?

Just trying to check if the WebView completely crashed.

[FaureAlexis]

appreciate your help, @FabianLars ! No, I don't have any context menu and I can't open devtools :(

[FabianLars]

This is a bit concerning. And no messages in the terminal where you run tauri dev either?

[FaureAlexis]

When I run in debug mode in VS i got the following output :

2024-01-15 16:56:26.291278+0100 what-ports[80492:1427886] [Process] WebContent process (0x11801cc40) took 2.903851 seconds to launch
2024-01-15 16:56:26.433394+0100 what-ports[80492:1428317] flock failed to lock list file (/var/folders/4l/qb0kgrsd2sz8wf4k2_89_71w0000gn/C//com.apple.metal/32023/libraries.list): errno = 35
2024-01-15 16:56:26.435662+0100 what-ports[80492:1428171] flock failed to lock list file (/var/folders/4l/qb0kgrsd2sz8wf4k2_89_71w0000gn/C//com.apple.metal/16777235_322/functions.list): errno = 35
2024-01-15 16:56:26.675117+0100 what-ports[80492:1427886] RemoteLayerTreeDrawingAreaProxyMac::scheduleDisplayLink(): page has no displayID

RemoteLayerTreeDrawingAreaProxyMac::scheduleDisplayLink(): page has no displayID
2024-01-15 16:56:26.761048+0100 what-ports[80492:1427886] RemoteLayerTreeDrawingAreaProxyMac::scheduleDisplayLink(): page has no displayID

RemoteLayerTreeDrawingAreaProxyMac::scheduleDisplayLink(): page has no displayID
2024-01-15 16:56:26.993215+0100 what-ports[80492:1427886] [Process] 0x13d814018 - [pageProxyID=7, webPageID=8, PID=80499] WebPageProxy::didFailProvisionalLoadForFrame: frameID=2, isMainFrame=1, domain=NSURLErrorDomain, code=-1004, isMainFrame=1, willInternallyHandleFailure=0
2024-01-15 16:56:27.663356+0100 what-ports[80492:1427886] [miscellany] FAULT: <NSRemoteView: 0x11cefe040 com.apple.TextInputUI.xpc.CursorUIViewService TUICursorUIViewService> determined it was necessary to configure <TUINSWindow: 0x13e3ee1d0> to support remote view vibrancy

[FaureAlexis]

Bump

[ReactorScram]

I had a similar issue but it's because I was just using cargo run. When I switched to cargo tauri dev and then it prompted me to set up Node and run pnpm install, it started working.

[FaureAlexis]

I had a similar issue but it's because I was just using cargo run. When I switched to cargo tauri dev and then it prompted me to set up Node and run pnpm install, it started working.

for my part I ended up buying a new macbook