Labhansh Agrawal

If I run electron-installer-snap directly against the linux arm64 unpacked dir I get ``` node:internal/process/promises:227 triggerUncaughtException(err, true /* fromPromise */); ^ [Error: ENOENT: no such file or directory, open '/home/labhansh/hyper/dist/linux-arm64-unpacked/version']...

electron-packager created a new folder and it had a version file with the electron version (11.2.3) so I copied that and ran it again. I got basically the same output...

I have multipass installed already, though haven't done any specific setup if required.

I applied that patch but it wasn't having any effect. I found out that the args are coming from `node_modules/electron-installer-snap/src/index.js` line 53 I added the `destructive-mode` argument and reran The...

Note - The above is not from when I'm building arm64 snap with electron-builder directly. It's from the script in https://github.com/electron-userland/electron-builder/issues/5626#issuecomment-780451154

With the patch, on running via electron-builder it failed saying that the arguments are unknown. The arguments that are changed on the patch are supplied to app-builder-bin/.../app-builder not directly to...

That didn't change the outcome, It's still saying x64. Since it's using prebuilt binaries, I'm guessing the goarch variable is sort of built in. But it all works when targetting...

Ok in armv7l case there's this ` --exclude chrome-sandbox --template-url electron4:armhf` extra bit at the end of the command maybe we'd need arm64 template or something for this to be...

I haven't looked much further yet I just noticed that template thing as I was wondering why it wasn't failing for armv7l and saw that the command getting run is...

> Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward? > > This issue has been automatically marked...