Adding an existing vault over SMB from Windows machine causes the error ‘"vault.cryptomator" couldn't be copied to "tmp".‘ with error codes 22, 512 in log
System Setup
iOS: 17.5.1
Cryptomator iOS: 2.5.2 (1228)
Windows 10 22H2
Cryptomator Windows: 1.12.4
Seagate SCIS exFAT HDD
Cloud Type
Other File Provider
Steps to Reproduce
Created test vault with Cryptomator GUI at top directory level of external HDD in Windows using default settings
In iOS app, Add Vault > Open Existing Vault > Other File Provider > Select Vault Folder
Navigate into the vault folder /host/HDD/testvault within the Files overlay > Open
Expected Behavior
The vault contents should be available
Actual Behavior
The error ‘vault.cryptomator" couldn't be copied to "tmp".‘ appears on a dialog box. After dismissing, the app remains on the Open Existing Vault page.
Reproducibility
Always
Relevant Log Output
org.cryptomator.ios.fileprovider 2024-06-08--09-02-20-228.log:
2024/06/08 09:05:29:932 enumerator(for:
NSFileProviderItemIdentifier(_rawValue: NSFileProviderRootContainerItemIdentifier)) failed as the extension is not initialized
—
org.cryptomator.ios 2024-06-08--09-03-16-840.log:
2024/06/08 18:21:18:751 Error: Error Domain=NSCocoaErrorDomain Code=512 "“vault.cryptomator” couldn’t be copied to “tmp”." UserInfo={NSSourceFilePathErrorKey=/private/var/mobile/Library/LiveFiles/com.apple.filesystems.smbclientd/<redacted>/testvault/vault.cryptomator, NSUserStringVariant=(
Copy
), NSDestinationFilePath=/private/var/mobile/Containers/Data/Application/7AC6E709-7438-49C6-8A11-A69329410552/tmp/B02DE745-0AFE-4F24-B1B5-DF6F2C6B1B2D, NSFilePath=/private/var/mobile/Library/LiveFiles/com.apple.filesystems.smbclientd/<redacted>/testvault/vault.cryptomator, NSUnderlyingError=0x302f0e5e0 {Error Domain=NSPOSIXErrorDomain Code=22 "Invalid argument"}}
Anything else?
I also tried this with a preexisting vault already containing data and got the same error.
Please agree to the following
Summary
Adding an existing vault over SMB from Windows machine causes the error ‘"vault.cryptomator" couldn't be copied to "tmp".‘ with error codes 22, 512 in log
System Setup
Cloud Type
Other File Provider
Steps to Reproduce
Expected Behavior
The vault contents should be available
Actual Behavior
The error ‘vault.cryptomator" couldn't be copied to "tmp".‘ appears on a dialog box. After dismissing, the app remains on the Open Existing Vault page.
Reproducibility
Always
Relevant Log Output
Anything else?
I also tried this with a preexisting vault already containing data and got the same error.