Vault version 999 is unsupported

[ejm554]

Please agree to the following

• I have searched existing issues for duplicates
• I agree to follow this project's Code of Conduct

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.

Reproducibility

Always

Relevant Log Output

No response

Anything else?

No response

[ejm554]

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.

[iammajid]

@ejm554,

I've looked into the issue you've reported and was able to reproduce it. The problem occurs when the vault folder is renamed outside of Cryptomator, for example via the OneDrive interface. This causes Cryptomator to no longer find the vault because the path has changed, resulting in the error message "Vault version 999 is unsupported".

If you rename a folder within the vault, this error should not occur.

Solution:

• Option 1: Remove the vault in Cryptomator and then add it again from the new location (the renamed folder).
• Option 2: Rename the vault directly within the Cryptomator app. This ensures that all internal references are updated correctly.

We acknowledge that the error message is misleading. We'll work on improving it in future versions of Cryptomator to more clearly indicate the actual problem.

If your issue occurs differently, it would be great if you could enable Debug Mode in the app settings (if you haven’t already), reproduce the error in your case, and then send us the log files via our support email. This would help us investigate the problem further.

[ejm554]

Thank you for the thorough reply!

Just a clarification in response to option # 2, "rename the vault directly within the Cryptomator app."

I never renamed the vault outside of Cryptomator. Rather, I renamed the containing folder.

For example:
/OneDrive/SuperFolder/MyVault
renamed to
/OneDrive/TheBatFolder/MyVault