You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I agree to follow the code of conduct that this project uses.
I have searched the issue tracker for a bug that matches the one I want to file, without success.
Electron Forge version
7.6.1
Electron version
34.0.2
Operating system
Ubuntu 24.04
Last known working Electron Forge version
No response
Expected behavior
Running
$ npx electron-forge make --arch=arm64
should correctly build an arm64/aarch64 Flatpak
Actual behavior
Currently this will fail
❯ Making distributables
✖ Making a flatpak distributable for linux/arm64
› flatpak failed with status code 1
Bit useless, but the trace is:
Error: flatpak failed with status code 1
at ChildProcess.<anonymous> (/home/pano/Programming/0_repos/TriliumNextNotes/node_modules/@malept/flatpak-bundler/index.js:73:16)
at ChildProcess.emit (node:events:520:28)
at ChildProcess.emit (node:domain:488:12)
at maybeClose (node:internal/child_process:1105:16)
at ChildProcess._handle.onexit (node:internal/child_process:305:5)
However if I enable the debugging messages, we can see it trying to use "arm64" as platform, which fails, because Flatpak does not use "arm64", but "aarch64" as identifier:
Will open up a PR that fixes this in a second and link it back here.
It'll do the same thing, that is currently done for "x64" architecture, where Flatpak actually uses "x86_64" as their arch identifiert
The text was updated successfully, but these errors were encountered:
Pre-flight checklist
Electron Forge version
7.6.1
Electron version
34.0.2
Operating system
Ubuntu 24.04
Last known working Electron Forge version
No response
Expected behavior
Running
should correctly build an arm64/aarch64 Flatpak
Actual behavior
Currently this will fail
Bit useless, but the trace is:
However if I enable the debugging messages, we can see it trying to use "arm64" as platform, which fails, because Flatpak does not use "arm64", but "aarch64" as identifier:
if we manually call the last command, it shows why it fails:
If we manually call the last command, but exchange arm64 with the correct arch identifier, it succeeds and starts downloading/installing
Steps to reproduce
Additional information
Will open up a PR that fixes this in a second and link it back here.
It'll do the same thing, that is currently done for "x64" architecture, where Flatpak actually uses "x86_64" as their arch identifiert
The text was updated successfully, but these errors were encountered: