Incorrect targeting of asar file on Linux
garrettmflynn opened this issue · comments
When running traces on a Linux machine at the Catalyst Neuro retreat, certain assets were unable to be found because of incorrect targeting of the asar file.
This issue seems to have been documented already (electron/electron#6262).
I'll test whether this happens again on my own Linux machine—as I have to dual-boot on my PC—and fix it from there. Anyone else who sees this is welcome to push a fix as well!
Switched to asar: false to ensure that service binaries can be executed.