Cryptomator vaults on Google Cloud Storage

[cyberduck]

2905bcc created the issue

This is a Cryptomator issue - running in Cyberduck 7.7.2 and Mountain Duck 4.3.3

When I setup Cyberduck with a Google Cloud Storage bucket, either using S3 interoperability, or native - if I create a cryptomator vault within the bucket it succeeds, makes a bunch of files, but it cannot mount the vault. No option is given to unlock.

If i open the same connection in MountainDuck - and go into the mountain duck menu in Finder, it does give me an option to unlock the vault. But it doesn't work, no error message - but this stack trace gets dumped to the macOS console:

error	08:49:59.714732-0800	Mountain Duck	Exception java.lang.NullPointerException running cleanup task
default	08:49:59.714988-0800	Mountain Duck	java.lang.NullPointerException
default	08:49:59.715023-0800	Mountain Duck		at ch.iterate.mountainduck.nativity.contextmenu.VaultMenuItemBuilder$UnlockVaultMenuItemSelectionHandler$1.cleanup(VaultMenuItemBuilder.java:238)
default	08:49:59.715043-0800	Mountain Duck		at ch.iterate.mountainduck.nativity.contextmenu.VaultMenuItemBuilder$UnlockVaultMenuItemSelectionHandler$1.cleanup(VaultMenuItemBuilder.java:235)
default	08:49:59.715059-0800	Mountain Duck		at ch.cyberduck.core.threading.WorkerBackgroundAction.cleanup(WorkerBackgroundAction.java:90)
default	08:49:59.715078-0800	Mountain Duck		at ch.cyberduck.core.threading.BackgroundCallable$1.run(BackgroundCallable.java:74)
default	08:49:59.715091-0800	Mountain Duck		at org.rococoa.internal.MainThreadUtils$3.callback(MainThreadUtils.java:91)
default	08:49:59.715106-0800	Mountain Duck		at jdk.internal.reflect.GeneratedMethodAccessor58.invoke(Unknown Source)
default	08:49:59.715121-0800	Mountain Duck		at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
default	08:49:59.715136-0800	Mountain Duck		at java.base/java.lang.reflect.Method.invoke(Unknown Source)
default	08:49:59.715255-0800	Mountain Duck		at com.sun.jna.CallbackReference$DefaultCallbackProxy.invokeCallback(CallbackReference.java:520)
default	08:49:59.715352-0800	Mountain Duck		at com.sun.jna.CallbackReference$DefaultCallbackProxy.callback(CallbackReference.java:551)
default	08:49:59.715434-0800	Mountain Duck		at com.sun.jna.Native.invokeVoid(Native Method)
default	08:49:59.715552-0800	Mountain Duck		at com.sun.jna.Function.invoke(Function.java:415)
default	08:49:59.715596-0800	Mountain Duck		at com.sun.jna.Function.invoke(Function.java:361)
default	08:49:59.715667-0800	Mountain Duck		at com.sun.jna.Function.invoke(Function.java:315)
default	08:49:59.715734-0800	Mountain Duck		at org.rococoa.internal.MsgSendHandler.invoke(MsgSendHandler.java:111)
default	08:49:59.715801-0800	Mountain Duck		at com.sun.jna.Library$Handler.invoke(Library.java:263)
default	08:49:59.715847-0800	Mountain Duck		at com.sun.proxy.$Proxy2.syntheticSendMessage(Unknown Source)
default	08:49:59.715920-0800	Mountain Duck		at org.rococoa.Foundation.send(Foundation.java:209)
default	08:49:59.715997-0800	Mountain Duck		at org.rococoa.Foundation.send(Foundation.java:195)
default	08:49:59.716069-0800	Mountain Duck		at org.rococoa.internal.ObjCObjectInvocationHandler.sendOnThisOrMainThread(ObjCObjectInvocationHandler.java:270)
default	08:49:59.716140-0800	Mountain Duck		at org.rococoa.internal.ObjCObjectInvocationHandler.invokeCocoa(ObjCObjectInvocationHandler.java:233)
default	08:49:59.716257-0800	Mountain Duck		at org.rococoa.internal.ObjCObjectInvocationHandler.intercept(ObjCObjectInvocationHandler.java:192)
default	08:49:59.716335-0800	Mountain Duck		at ch.cyberduck.binding.application.NSApplication$$ByRococoa.run(<generated>)
default	08:49:59.716432-0800	Mountain Duck		at ch.iterate.mountainduck.application.StatusBarApplication.main(StatusBarApplication.java:246)

[cyberduck]

@dkocher commented

Refer to Unlock Vault how to set the preference to auto detect vaults to unlock or manually unlock using the toolbar option in Cyberduck.

[cyberduck]

@dkocher commented

I can reproduce the problem with unlocking the vault.

[cyberduck]

@ylangisc commented

In d4e1b32.