Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

duplicate vaults in macOS desktop app #1032

Closed
bh11 opened this issue Dec 27, 2019 · 3 comments
Closed

duplicate vaults in macOS desktop app #1032

bh11 opened this issue Dec 27, 2019 · 3 comments
Labels
type:bug Something isn't working
Milestone

Comments

@bh11
Copy link

bh11 commented Dec 27, 2019

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

  • Operating system and version: macOS 10.13.6
  • Cryptomator version: 1.4.17
  • Drive: FUSE

Steps to Reproduce

  1. Create new vault (=> creates vault with absolute pathname)
  2. 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

@bh11 bh11 added the type:bug Something isn't working label Dec 27, 2019
@overheadhunter
Copy link
Member

Is it reproducable with the latest version?

@overheadhunter overheadhunter added the state:awaiting-response We need further input from the issue author label Dec 27, 2019
@bh11
Copy link
Author

bh11 commented Dec 27, 2019

@overheadhunter Sorry, the version number in the report was a typo (now corrected) – I'm using the latest version 1.4.17 (1451).

@no-response no-response bot removed the state:awaiting-response We need further input from the issue author label Dec 27, 2019
@overheadhunter
Copy link
Member

Ah, I see. 😄

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.

@overheadhunter overheadhunter added this to the 1.5.0 milestone Dec 28, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type:bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants