MacFuse - Not able to start

[BishopRed90]

Describe the bug

When trying to start up a mount with MacFuse installed - an error is thrown stating that FUSE-T is missing.

Documentation states that FUSE-T or MacFuse are supported for mounting.

Possibly this line here needs to have an additional check to see if MacFuse is installed !(await isMacFUSEInstalled())

To Reproduce

1. Have MacFuse Installed
2. Attempt to mount a network drive as stated in Documentation
3. Receive error stating that FUSE-T is missing

Expected behavior

Drive Mounts

Screenshots

OS (please complete the following information):

• OS: macOS
• Hardware configuration - Mac Air (M4)
• Filesystem and Disk type used: SSD - APFS

[nbca2]

i've the same problem with the same hardware, any solution?
thanks

[seffs]

The solution is as provided by @BishopRed90 . I'll open a PR for it.

In the meantime, you can force your way into mounting your drive by editing the source files in the NPM release.

1. Install or replace your current installation with the npm package: npm i -g @filen/cli@latest (currently: v0.0.39)

2. Edit the index.js from the package. Mine is located at /Users/<me>/.nvm/versions/node/v20.19.5/lib/node_modules/@filen/cli/build/index.js.

   Look for the (0, utils_1.isFUSETInstalledOnMacOS string.

   Update the whole line to:
   if (process.platform === "darwin" && !await (0, utils_1.isFUSETInstalledOnMacOS)() && !await (0, utils_1.isMacFUSEInstalled)()) {

3. Save your changes

You can execute filen mount now

---

I figured this out while trying to mount Filen in an even older MacOS version (10.14). It took a series of steps worthy of a gist. For anyone curious here's the TL;DR. My two cents:

• If you're in 10.14 just like me, you can still compile Go v1.23 by installing the v1.20 release first. The go project will do the rest for you. This will save you lots of time. More details here.
• ALWAYS CHECK THE RCLONE VERSION IN USE . Look for the rclone build number in index.js from the version (tag) you want to build. Filen.io is looking forward to release its own integration as well as a Rust rewrite from the CLI so it can change at any time.

I TAKE NO RESPONSABILITY FOR INCOMPATIBLE SPECS AND DATA LOSS. BUILD AT YOUR OWN RISK