Have to clear the cache at every start of the app to get access to WebDAV vault using mailbox.org

Can you please enable debug mode, reproduce the error and send us the log file or take a look into it.
A short time ago a user also had problems with mailbox.org and the cache. The server replied with a 412 HTTP status code. Please check the log if you find something like this:

PrepareUnlockUseCase	started 48878533
OkHttp	--> GET https://dav.mailbox.org/servlet/webdav.infostore/Userstore/xxx/mailbox/masterkey.cryptomator http/1.1 (unknown length)
OkHttp	--> END GET
OkHttp	<-- 412 Precondition Failed https://dav.mailbox.org/servlet/webdav.infostore/Userstore/xxx/mailbox/masterkey.cryptomator (98ms)
...
OkHttp	<-- END HTTP
PrepareUnlockUseCase	failed 48878533
ExceptionHandler	Unexpected error
org.cryptomator.domain.exception.FatalBackendException: Response code isn't between 200 and 300: 412
	at org.cryptomator.data.cloud.webdav.network.WebDavClient.void checkExecutionSucceeded(int)(:1)
	at org.cryptomator.data.cloud.webdav.network.WebDavClient.java.io.InputStream readFile(java.lang.String)(:5)
	at org.cryptomator.data.cloud.webdav.network.ConnectionHandlerHandlerImpl.java.io.InputStream readFile(java.lang.String)(:1)
	at org.cryptomator.data.cloud.webdav.WebDavImpl.void read(org.cryptomator.domain.CloudFile,java.io.OutputStream,org.cryptomator.domain.usecases.ProgressAware)(:34)
	...
	at org.cryptomator.domain.usecases.vault.PrepareUnlockUseCase$Launcher$2.org.cryptomator.domain.usecases.vault.UnlockToken call()(:4)
	at org.cryptomator.domain.usecases.vault.PrepareUnlockUseCase$Launcher$2.java.lang.Object call()(:1)
	at io.reactivex.internal.operators.flowable.FlowableFromCallable.void subscribeActual(org.reactivestreams.Subscriber)(:3)

If this is the case as a workaround you can disable in the Cryptomator settings the caching mechanism Settings — Cryptomator 1.7.0 documentation

1 Like