Latest Cryptomator won't open vault in MacOS Catalina

Hello, I haven’t been able to use Cryptomator since I upgraded to MacOS Catalina, When I try to open a vault, cryptomator crashes.

I am running the latest version of Cryptomator and the latest version of fuse. The crash occurs as soon as I click on the plus to add a vault.

Process:               Cryptomator [829]
Path:                  /Applications/
Identifier:            org.cryptomator
Version:               1.4.17 (1451)
Code Type:             X86-64 (Native)
Parent Process:        ??? [1]
Responsible:           Cryptomator [829]
User ID:               501

Date/Time:             2020-02-13 11:37:02.075 -0700
OS Version:            Mac OS X 10.15.3 (19D76)
Report Version:        12
Bridge OS Version:     4.2 (17P3050)
Anonymous UUID:        65D40AD7-805A-AAC9-678B-7CE9D677713B

Time Awake Since Boot: 200 seconds

System Integrity Protection: disabled

Crashed Thread:        0  Dispatch queue:

Exception Type:        EXC_BAD_ACCESS (SIGABRT)
Exception Codes:       KERN_PROTECTION_FAILURE at 0x000000010c4c5008
Exception Note:        EXC_CORPSE_NOTIFY

VM Regions Near 0x10c4c5008:
    __LINKEDIT             000000010c4b7000-000000010c4c5000 [   56K] r--/rwx SM=COW  /Applications/
--> VM_ALLOCATE            000000010c4c5000-000000010c4c6000 [    4K] ---/rwx SM=NUL  
    VM_ALLOCATE            000000010c4c6000-000000010c4c7000 [    4K] r--/rwx SM=PRV  

Application Specific Information:
*** Terminating app due to uncaught exception 'NSObjectNotAvailableException', reason: 'GlassOpenPanel is not a supported subclass for sandboxing'
abort() called
terminating with uncaught exception of type NSException

+1 Same happens when trying to create a new vault. Happy to provide any details that might help chase this down.

Habe you seen these threads?

Edit: Oh sorry, just read that you have the latest version of fuse.

Might be this issue:, however I don’t understand why not all users are affected by this. We will discuss, if our next beta version uses OpenJFX 14, which will contain a fix for this issue.

Can you retest this using 1.5.0-beta2? I expect this still to occur, but just to make sure.

Bug report on GitHub:

1 Like