Open ejm554 opened 2 months ago
I discovered that this problem occurred after I renamed the vault’s containing folder, which exists on OneDrive. I then attempted to use the “move” feature, which didn’t work. (An error appeared saying the vault with the same name already existed.)
I was able to ultimately fix the issue by deleting the vault and then adding it from the re-named folder.
While my specific issue has been resolved, I think this still may need to be classified as a bug. An ideal fix could include:
A more useful error message after a containing folder is renamed; the 999 error was unhelpful.
Ensuring that the “move” feature works better given the scenario described herein; the “already exists” message was unhelpful.
Please agree to the following
Summary
Error message “999” appears when attempting to open a vault in iOS Files app
What software is involved?
Volume Type
None
Steps to Reproduce
Expected Behavior
I expected the vault to open, as it did in the past.
Actual Behavior
An error message appears. It suggests that I may be using an incorrect version of Cryptomator, and/or that my vault was created with an incompatible version.
Reproducibility
Always
Relevant Log Output
No response
Anything else?
No response