ASAR integrity doesn't work under WSL
- Dominant language
- TypeScript
- Stars
- 7.1k
- Forks
- 641
- Avg merge
- 3d 1h
- Merged PRs (30d)
- 30
Description
### Pre-flight checklist
- [X] I have read the [contribution documentation](https://github.com/electron/forge/blob/main/CONTRIBUTING.md) for this project.
- [X] I agree to follow the [code of conduct](https://github.com/electron/electron/blob/main/CODE_OF_CONDUCT.md) that this project uses.
- [X] I have searched the issue tracker for a bug that matches the one I want to file, without success.
### Electron Forge version
7.4.0
### Electron version
30.0.7
### Operating system
Windows 10 (Version 10.0.19045 Build 19045)
### Last known working Electron Forge version
_No response_
### Expected behavior
Electron binary to run
### Actual behavior
Electron binary doesnt run and instead produces the error (when run from a command line):
[293384:0523/095224.285:FATAL:archive_win.cc(152)] Failed to find file integrity info for resources\app.asar
[293384:0523/095224.285:ERROR:crashpad_client_win.cc(868)] not connected
### Steps to reproduce
I use WSL for an Ubuntu 20.04 command line, but it shouldnt make a difference (since I build in a docker container):
1. npm init electron-app@latest my-app -- --template=webpack-typescript
2. cd my-app
3. docker run -it -v ${HOME}:${HOME} -v /etc/passwd:/etc/passwd -u `id -u`:`id -g` -v ${PWD}:/repo electronuserland/builder:wine-mono /bin/bash
4. cd /repo
5. yarn install
6. yarn run package --platform win32 (this succeeds without error)
To see error:
7. In windows, open file explorer to the 'out' directory
8. Double click electron-typescript.exe (nothing happens)
9. Open the same directory in powershell
10. ./electron-typescript.exe
11. Observe error
### Additional information
Note: when I use a native environment (e.g. powershell + windows node) the same steps above do work. They just dont work while running the docker image (which is what I would like to use for CI). I have also tried running the docker image from powershell and it produces the same result.
Contributor guide
Assessment
This issue has not been assessed yet.