ASAR integrity info corrupt in crossplatform build

[Lemonexe]

Preflight Checklist

• I have read the Contributing Guidelines for this project.
• I agree to follow the Code of Conduct that this project adheres to.
• I have searched the issue tracker for a bug report that matches the one I want to file, without success.

Electron Version

33.2.0

What operating system(s) are you using?

Ubuntu

Operating System Version

Ubuntu 24.04.1 LTS

What arch are you using?

x64

Last Known Working Electron version

No response

Expected Behavior

• When building an electron app on Linux for Windows, with EnableEmbeddedAsarIntegrityValidation fuse on, the built .exe binary should contain valid file integrity information.
• The .exe should start normally.

Actual Behavior

• The .exe binary built on Linux for Windows contains "file":"resources/app.asar" in the file integrity info
  • instead of the expected "file":"resources\\app.asar".
• When you execute the binary both natively on Windows, as well as through wine on Linux, crashes with following error:

  [268:1112/144705.795:FATAL:archive_win.cc(152)] Failed to find file integrity info for resources\app.asar
  

• After switching off the EnableEmbeddedAsarIntegrityValidation fuse on the built binary, the application runs.

Testcase Gist URL

https://gist.github.com/Lemonexe/094a6b77f2ece7b7d326db57ebc75da6

Additional Information

ℹ More details in the gist README.md.

• The gist is using electron-forge, but I also reproduced it with electron-builder (so I guess issue lies in electron itself).
• This line throws the error during runtime.
• I did not find which line is responsible for saving file url with wrong slashes during build (I have no C++ knowledge 😞).

[welcome]

👋 Thanks for opening your first issue here! If you have a question about using Electron Packager, read the support docs. If you're reporting a 🐞 bug, please make sure you include steps to reproduce it. Development and issue triage is community-driven, so please be patient and we will get back to you as soon as we can.

To help make it easier for us to investigate your issue, please follow the contributing guidelines.

[continuous-auth]

🎉 This issue has been resolved in version 18.3.6 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀