Change:
In the vault options, vaults can only be mounted as . Steps to reproduce the behavior: cryptomator to a vault options the tab, the combo box does not contain a FUSE item Vaults can be mounted as FUSE volumes In the console output, cryptomator seems to have access to the fuse3 libs in its PATH: Full console output:
I think this might be related to It seems since they switched to the new fuse integration they only search a predefined number of paths. This is also consistent as the nix build of cryptomator works on non nixos linux.
I have the same issue. Does somebody have some workaraound yet? EDIT: so what I am currently doing, which is really not ideal, is just mounting the webdav directory with rclone, which, well, uses FUSE. so yeah rclone has no problems with using FUSE...
The fix for this is merged but not yet released It's in the 4.0.0 milestone of fuse-nio-adapter. I'm currently using the flapak version of Cryptomator.
thank you for the answer! i don't quite understand what is. Is it a dependency of ? Is there a way to manually fetch this so that it works? I'm gonna try the flatpak version of Cryptomator out, thanks for the hint. I actually tried out appimage, but that didn't change anything.
In the 1.11.0-beta2 release of cryptomator, vaults are able to be mounted as FUSE volumes. So once 1.11.0 is fully released (and the nixpkgs version updated), this issue should be fixed. Until the new version of cryptomator is released, you could create an overlay to use the beta version, like I am doing at the moment. Apart from changing the version and hashes, I also needed to change the jdk used to a jdk21 and overriding it to enable JavaFX:
thank you for your response! i hope i am not rude to ask for your help in achieving this myself. i put the following in my : and i also did the overlay. i get the following error when building: haven't been able to successfully find a solution via search engines...
For overlays, I simply copy the nix files and doing the following overlay: This is quite crude, and there is probably a better way to do it, but it at least avoids any weird errors like the one you are having.

Discussion:
assert stdenv.isLinux; # better than `called with unexpected argument 'enableJavaFX'` mavenJdk.buildMavenPackage rec { pname = "cryptomator"; <del> version = "1.10.1"; </del> <ins> version = "1.11.0"; </ins> src = fetchFromGitHub { owner = "cryptomator"; repo = "cryptomator"; rev = version; <del> hash = "sha256-xhj7RUurBRq9ZIDAlcq7KyYGnLqc+vTjaf2VMNStpVQ"; </del> <ins> hash = "sha256-NMNlDEUpwKUywzhXhxlNX7NiE+6wOov2Yt8nTfbKTNI="; </ins> }; mvnParameters = "-Dmaven.test.skip=true"; <del> mvnHash = "sha256-XAIwKn8wMqILMQbg9wM4kHAaRSGWQaBx9AXQyJuUO5k="; </del> <ins> mvnHash = "sha256-jIHMUj7ZQFu4XAvWUywj4f0PbmLHGtU5VRG0ZuKm3mA="; </ins> preBuild = '' VERSION=${version}

--add-flags "--enable-preview"  --add-flags "--class-path '$out/share/cryptomator/libs/*'"  --add-flags "--module-path '$out/share/cryptomator/mods'"  <del> --add-flags "-Dcryptomator.logDir='~/.local/share/Cryptomator/logs'"  --add-flags "-Dcryptomator.pluginDir='~/.local/share/Cryptomator/plugins'"  --add-flags "-Dcryptomator.settingsPath='~/.config/Cryptomator/settings.json'"  --add-flags "-Dcryptomator.ipcSocketPath='~/.config/Cryptomator/ipc.socket'"  --add-flags "-Dcryptomator.mountPointsDir='~/.local/share/Cryptomator/mnt'"  </del> <ins> --add-flags "-Dfile.encoding='utf-8'"  --add-flags "-Dcryptomator.logDir='@{userhome}/.local/share/Cryptomator/logs'"  --add-flags "-Dcryptomator.pluginDir='@{userhome}/.local/share/Cryptomator/plugins'"  --add-flags "-Dcryptomator.settingsPath='@{userhome}/.config/Cryptomator/settings.json'"  --add-flags "-Dcryptomator.p12Path='@{userhome}/.config/Cryptomator/key.p12'"  --add-flags "-Dcryptomator.ipcSocketPath='@{userhome}/.config/Cryptomator/ipc.socket'"  --add-flags "-Dcryptomator.mountPointsDir='@{userhome}/.local/share/Cryptomator/mnt'"  </ins> --add-flags "-Dcryptomator.showTrayIcon=false"  --add-flags "-Dcryptomator.buildNumber='nix'"  --add-flags "-Dcryptomator.appVersion='${version}'" 

criu = callPackage ../os-specific/linux/criu { }; cryptomator = callPackage ../tools/security/cryptomator { <del> jdk = jdk20.override { enableJavaFX = true; }; </del> <ins> jdk = jdk21.override { enableJavaFX = true; }; </ins> }; cryptsetup = callPackage ../os-specific/linux/cryptsetup { };