Duplicate of #5641

As AppImage doesn't support fuse 3, it is not possible for us to provide an AppImage that uses fuse 3, their official documentation says to install fuse 2 (linked in the provided issue).

Duplicate of #5641

As AppImage doesn't support fuse 3, it is not possible for us to provide an AppImage that uses fuse 3, their official documentation says to install fuse 2 (linked in the provided issue).

This is actually possible and it is done by plenty of appimages already, examples include: Cemu (since like 2 years ago), duckstation, PCSX2 and Zen-browser.

Will see if I can make the PR like I just did here

The AppImage documentation is outdated, very outdated.

@Samueru-sama If you know a way of doing it that would be great!
We don't actually build the AppImage (or any of the other packages) ourselves, we call our to electron-builder and that takes care of it for us. So you'll have to make modifications to electron-builder and it's various dependencies, to change how the AppImage is built.

Probably not useful to you, but the file that invokes electron-builder is _scripts/build.js and the configuration it passes to electron-builder is in _scripts/ebuilder.config.js.

@Samueru-sama If you know a way of doing it that would be great! We don't actually build the AppImage (or any of the other packages) ourselves, we call our to electron-builder and that takes care of it for us. So you'll have to make modifications to electron-builder and it's various dependencies, to change how the AppImage is built.

Probably not useful to you, but the file that invokes electron-builder is _scripts/build.js and the configuration it passes to electron-builder is in _scripts/ebuilder.config.js.

I was actually asking for help understanding how the CI worked here, because I checked the workflow files and noticed that it immediately went from build to upload appimage and I was like wait what where is the rest lol so thank you for the explanation.

This means there are two ways to fix this issue.

• A) Open an issue at electron-builder to update to a different appimagetool that automatically uses the static appimage runtime, hopefully they are using the appimagetool from AppImage/AppImageKit, because in that case there is the appimagetool from AppImage/appimagetool which is a drop in replacement that pulls the static runtime by default. AKA just change one word in the download link.

• B) Right after the appimage gets build here, extract it and wget appimagetool and remake the appimage, it is a bit hacky but will work, this method will also allow for generating the .zsync files for delta updates.