Can't Open Vault After Migration

Help
1

I installed the new update and I accidentally pressed the migration button while there was an awaiting file sync in Dropbox/Mega.

I cannot open it now and I downgraded back to 1.5.17. The error shows:

org.cryptomator.cryptolib.api.UnsupportedVaultFormatException: Tried to open vault of version 999, but can only handle version 7
	at org.cryptomator.cryptolib.v1.CryptorProviderImpl.createFromKeyFile(CryptorProviderImpl.java:117)
	at org.cryptomator.cryptolib.v1.CryptorProviderImpl.createFromKeyFile(CryptorProviderImpl.java:108)
	at org.cryptomator.cryptolib.v1.CryptorProviderImpl.createFromKeyFile(CryptorProviderImpl.java:40)
	at org.cryptomator.cryptofs.CryptoFileSystemModule.provideCryptor(CryptoFileSystemModule.java:41)
	at org.cryptomator.cryptofs.CryptoFileSystemModule_ProvideCryptorFactory.provideCryptor(CryptoFileSystemModule_ProvideCryptorFactory.java:56)
	at org.cryptomator.cryptofs.CryptoFileSystemModule_ProvideCryptorFactory.get(CryptoFileSystemModule_ProvideCryptorFactory.java:43)
	at org.cryptomator.cryptofs.CryptoFileSystemModule_ProvideCryptorFactory.get(CryptoFileSystemModule_ProvideCryptorFactory.java:11)
	at dagger.internal.DoubleCheck.get(DoubleCheck.java:47)
	at org.cryptomator.cryptofs.CryptoFileSystemImpl_Factory.get(CryptoFileSystemImpl_Factory.java:110)
	at org.cryptomator.cryptofs.CryptoFileSystemImpl_Factory.get(CryptoFileSystemImpl_Factory.java:16)
	at dagger.internal.DoubleCheck.get(DoubleCheck.java:47)
	at org.cryptomator.cryptofs.DaggerCryptoFileSystemProviderComponent$CryptoFileSystemComponentImpl.cryptoFileSystem(DaggerCryptoFileSystemProviderComponent.java:337)
	at org.cryptomator.cryptofs.CryptoFileSystems.lambda$create$0(CryptoFileSystems.java:47)
	at java.base/java.util.concurrent.ConcurrentHashMap.compute(Unknown Source)
	at org.cryptomator.cryptofs.CryptoFileSystems.create(CryptoFileSystems.java:40)
	at org.cryptomator.cryptofs.CryptoFileSystemProvider.newFileSystem(CryptoFileSystemProvider.java:301)
	at org.cryptomator.cryptofs.CryptoFileSystemProvider.newFileSystem(CryptoFileSystemProvider.java:93)
	at java.base/java.nio.file.FileSystems.newFileSystem(Unknown Source)
	at java.base/java.nio.file.FileSystems.newFileSystem(Unknown Source)
	at org.cryptomator.cryptofs.CryptoFileSystemProvider.newFileSystem(CryptoFileSystemProvider.java:134)
	at org.cryptomator.common.vaults.Vault.createCryptoFileSystem(Vault.java:130)
	at org.cryptomator.common.vaults.Vault.unlock(Vault.java:147)
	at org.cryptomator.ui.unlock.UnlockWorkflow.attemptUnlock(UnlockWorkflow.java:100)
	at org.cryptomator.ui.unlock.UnlockWorkflow.call(UnlockWorkflow.java:81)
	at org.cryptomator.ui.unlock.UnlockWorkflow.call(UnlockWorkflow.java:44)
	at javafx.concurrent.Task$TaskCallable.call(Task.java:1425)
	at java.base/java.util.concurrent.FutureTask.run(Unknown Source)
	at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
	at java.base/java.util.concurrent.FutureTask.run(Unknown Source)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
	at java.base/java.lang.Thread.run(Unknown Source)
2

The migration does only to some changes on the Masterkey file and creates a new file called „vault.Cryptomator“). It does not make changes to the content vault files.

As the 1.5.x version claims that it cannot open the vault due to version 999, it seems that the migration was done successfully.
Please installl the laustest Cryptomator and try to open your vault and report if that worked, or if not which error message is thrown.