SocketIO not working on Tauri-built NextJS desktop app

[WaelMajdoub]

Hi Tauri community,

I'm building a desktop app with Next.js and Tauri, and I'm using Socket.IO for real-time communication between the client and the server. When I run the app with "yarn dev" command, the app works fine with Socket.IO and the socket client. However, when I build the app to a desktop application for Windows, the Socket.IO connection doesn't seem to work anymore.

It's worth noting that the issue only occurs in the desktop version of the app, and not when running the app locally.

Has anyone encountered a similar issue with Socket.IO in a Tauri-built app, and if so, how did you resolve it? I'd appreciate any help or insights on this matter.

Thanks in advance!

[FabianLars]

Are you using a http/ws connection? If so then this may be related to #3007. Could also be a CSP i think.

Anyway, try building in debug mode: tauri build --debug (if you use npm it needs an extra -- like npm run tauri build -- --debug) - output in target/debug/. This build will have the devtools enabled so you can check its console for errors.

[r3wt]

@sauhaardac websockets over ssl protocol is wss://, not ws://.

[raunakdoesdev]

Yep fixed that, thanks. Turns out you can operate without SSL on macOS but it's needed for windows.

[RHAM91]

I found a solution, it is the following:
in the tauri.conf.json file go to the "security" key you should add this:

 "security": {
      "dangerousUseHttpScheme": true,
      "csp": null
  }

this will allow mixed content when we try to fetch http endpoints.

I hope I've been useful

[PMLS3]

dangerousUseHttpScheme is not an option anymore, is there another fix?

[FabianLars]

In v1 this is still an option and in v2 this is now the default so the option was removed (we'll probably add it back at some point)