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

Vault version 999 is unsupported #356

Open
2 tasks done
ejm554 opened this issue Apr 25, 2024 · 1 comment
Open
2 tasks done

Vault version 999 is unsupported #356

ejm554 opened this issue Apr 25, 2024 · 1 comment
Labels
type:bug Something isn't working

Comments

@ejm554
Copy link

ejm554 commented Apr 25, 2024

Please agree to the following

Summary

Error message “999” appears when attempting to open a vault in iOS Files app

What software is involved?

  • Operating System: iOS 17.5 (21F5058e)
  • Cryptomator: 2.5.2 (1228)
  • OneDrive: 15.10.3

Volume Type

None

Steps to Reproduce

  1. Go to Cryptomator app
  2. Attempt to open desired vault
  3. Error message appears (see ”Actual behavior“)

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.

Vault version 999 is unsupported. This vault has been created with an older or newer version of Cryptomator.

image

Reproducibility

Always

Relevant Log Output

No response

Anything else?

No response

@ejm554 ejm554 added the type:bug Something isn't working label Apr 25, 2024
@ejm554 ejm554 closed this as completed Apr 25, 2024
@ejm554 ejm554 reopened this Apr 25, 2024
@ejm554 ejm554 closed this as completed Apr 25, 2024
@ejm554
Copy link
Author

ejm554 commented Apr 25, 2024

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:

  1. A more useful error message after a containing folder is renamed; the 999 error was unhelpful.

  2. Ensuring that the “move” feature works better given the scenario described herein; the “already exists” message was unhelpful.

@ejm554 ejm554 reopened this Apr 25, 2024
@tobihagemann tobihagemann transferred this issue from cryptomator/cryptomator Apr 25, 2024
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

1 participant