You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Cryptomator creates new vaults using full pathnames. When re-opening a vault by double-clicking its masterkey.cryptomator file, a new vault with relative pathname shows up.
(Not a terrible problem, after deleting the entry with the full pathname, no more duplicates show up.)
System Setup
Operating system and version: macOS 10.13.6
Cryptomator version: 1.4.17
Drive: FUSE
Steps to Reproduce
Create new vault (=> creates vault with absolute pathname)
open vault by double-clicking on masterkey.cryptomator file
Expected Behavior
Cryptomator should use the vault entry with the full pathname (or, possibly, use the relative pathname when creating a new vault
Actual Behavior
In the Vaults list, a 2nd entry with relative path name (starting at ~/) is created
Reproducibility
Always
Additional Information
The text was updated successfully, but these errors were encountered:
Well, of course this is an unwanted behaviour and we should fix this. However it isn't a major issue and has a workaround, therefore I'd suggest to fix this for the upcoming major release 1.5.0.
Description
Cryptomator creates new vaults using full pathnames. When re-opening a vault by double-clicking its masterkey.cryptomator file, a new vault with relative pathname shows up.
(Not a terrible problem, after deleting the entry with the full pathname, no more duplicates show up.)
System Setup
Steps to Reproduce
Expected Behavior
Cryptomator should use the vault entry with the full pathname (or, possibly, use the relative pathname when creating a new vault
Actual Behavior
In the Vaults list, a 2nd entry with relative path name (starting at ~/) is created
Reproducibility
Always
Additional Information
The text was updated successfully, but these errors were encountered: