Topic about huge bug in 1.4.3 deleted?

Help Desktop App
1

Hi,

yesterday the following topic has been created:
Update 1.4.3: Storage not possible

This topic is not available anymore - that should not happen !!!

The bigger problem is that nobody seems to care about the reported huge bug:
With 1.4.3. at least three people (incl. me) are not able to store any file at all. Copying files lasts very long and produces zero-byte files.

Please care about and please don’t delete this post again!

EDIT: I have to mention that I’m working on MacOS Mojave.

Cheers,
Ralf

2

Ralf,

I am having the same problem and I’m also on MacOS Mojave. For me it looks like a WebDAV issue. In the preferences, try switching the Preferred Volume Type to FUSE. This fixed the problem for me.

Cheers,
Paul.

3

Hi Paul,

thanks for your support!
Unfortunately I can’t change the Volume Type. It remains on WebDAV without any further option.

Any other idea?

Cheers,
Ralf

4

Ralf,

FUSE is a separate install so if it’s not listed you probably don’t already have it. You can get it from here: https://osxfuse.github.io/

Once installed you should see the extra option in Cryptomator preferences. You can switch from WebDAV to FUSE without needing to change anything about your vaults.

Cheers,
Paul.

5

Paul,

sorry, it seems I got you wrong as I expected this switch option as an internal function of Cryptomator :frowning:

Up to now I had no need to install Fuse and even Cryptomator worked without it until 1.4.2 except one little other problem:
Every time I start Cryptomator I get an Internal Error Message (in German) “Eine nicht abgefangene Ausnahme ist aufgetreten…”.

Detailed message:

Ausnahmename: NSInternalInconsistencyException
Beschreibung: Invalid parameter not satisfying: _type > 0 && _type <= kCGSLastEventType
Benutzerinformationen: (null)

0 CoreFoundation 0x00007fff458fbded __exceptionPreprocess + 256
1 libobjc.A.dylib 0x00007fff719c3720 objc_exception_throw + 48
2 CoreFoundation 0x00007fff45916a4a +[NSException raise:format:arguments:] + 98
3 Foundation 0x00007fff47cbae0d -[NSAssertionHandler handleFailureInMethod:object:file:lineNumber:description:] + 194
4 AppKit 0x00007fff42d9f4d5 -[NSEvent _initWithCGEvent:eventRef:] + 3272
5 AppKit 0x00007fff430f2b50 +[NSEvent eventWithCGEvent:] + 120
6 libglass.dylib 0x000000012a47620b listenTouchEvents + 59
7 SkyLight 0x00007fff6ba6cbc2 _ZL19processEventTapDataPvjjjPhj + 148
8 SkyLight 0x00007fff6b96ab44 _XPostEventTapData + 278
9 SkyLight 0x00007fff6ba6cad0 ZL22eventTapMessageHandlerP12__CFMachPortPvlS1 + 132
10 CoreFoundation 0x00007fff4585c9eb __CFMachPortPerform + 246
11 CoreFoundation 0x00007fff4585c8e9 CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE1_PERFORM_FUNCTION + 41
12 CoreFoundation 0x00007fff4585c847 __CFRunLoopDoSource1 + 527
13 CoreFoundation 0x00007fff458448c5 __CFRunLoopRun + 2574
14 CoreFoundation 0x00007fff45843c64 CFRunLoopRunSpecific + 463
15 HIToolbox 0x00007fff44adaab5 RunCurrentEventLoopInMode + 293
16 HIToolbox 0x00007fff44ada7eb ReceiveNextEventCommon + 618
17 HIToolbox 0x00007fff44ada568 _BlockUntilNextEventMatchingListInModeWithFilter + 64
18 AppKit 0x00007fff42d95363 _DPSNextEvent + 997
19 AppKit 0x00007fff42d94102 -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 1362
20 libosxapp.dylib 0x00000001289e5dbf -[NSApplicationAWT nextEventMatchingMask:untilDate:inMode:dequeue:] + 122
21 AppKit 0x00007fff42d8e165 -[NSApplication run] + 699
22 libosxapp.dylib 0x00000001289e5bbc +[NSApplicationAWT runAWTLoopWithApp:] + 157
23 libawt_lwawt.dylib 0x000000012895d344 +[AWTStarter starter:headless:] + 834
24 JavaNativeFoundation 0x00007fff49a0cf3c +[JNFRunLoop _performCopiedBlock:] + 17
25 Foundation 0x00007fff47c3fbab __NSThreadPerformPerform + 327
26 CoreFoundation 0x00007fff45861395 CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION + 17
27 CoreFoundation 0x00007fff4586133b __CFRunLoopDoSource0 + 108
28 CoreFoundation 0x00007fff45844dd1 __CFRunLoopDoSources0 + 195
29 CoreFoundation 0x00007fff4584437a __CFRunLoopRun + 1219
30 CoreFoundation 0x00007fff45843c64 CFRunLoopRunSpecific + 463
31 libjli.dylib 0x00000001115871e3 CreateExecutionEnvironment + 401
32 libjli.dylib 0x00000001115834dc JLI_Launch + 1568
33 libpackager.dylib 0x000000010fb12fd4 _ZN11JavaLibrary12JavaVMCreateEmPPc + 180
34 libpackager.dylib 0x000000010fb14d62 _ZN18JavaVirtualMachine8launchVMER11JavaOptionsRSt4listISsSaISsEEb + 1090
35 libpackager.dylib 0x000000010fb11ba1 _ZN18JavaVirtualMachine8StartJVMEv + 2817
36 libpackager.dylib 0x000000010fb10fb0 _Z5RunVM13JvmLaunchType + 48
37 libpackager.dylib 0x000000010fb1d65e start_launcher + 1870
38 Cryptomator 0x000000010fae5cec main + 220
39 libdyld.dylib 0x00007fff72a91ed9 start + 1

Maybe this can help to locate the problem…

Cheers,
Ralf

6

Hi Ralf,

Unfortunately I’m not a Cryptomator developer so I can’t help with that message. I’ve always had FUSE on my system as I use it for other things and it fixed this issue for me.

It’s clearly a problem with 1.4.3 and hopefully the devs will fix it soon.

Cheers,
Paul.

7

Hi Paul,

sorry for bothering you with these boring lines :slight_smile:

I’ll give FUSE a try and hope it helps until we have a new stable version.

Thanks,
Ralf

8

Hi all,

I have this problem too in the newest release of the MacOs desktop app. Files stay 0kb after transfering into the vault.

Please release a hotfix for this!

9

I’m on windows. Saving files under 1.43 creates 0-bytes files. After downgrading to 1.42 everything works again.

10

Hotfix was released.
Please see change log for fixed issues.

11

I just looked into the moderation history and saw that “system” deleted the thread. Apparently this is due to the fact that the OP deleted his/her account. I’m sorry if that caused confusion but I can assure you that it is not our intend to cover a bug. As you can see in the GitHub repo we’ve always publicly documented bugs, even in the early times when there were some security fixes.

1 Like