"Content Unavailable" error after unlocking vault

[HelixCA]

Please agree to the following

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

Summary

Vault crerated under 1.70 for Mac will not open in IOS

What software is involved?

• Operating System: Mac Montery
• Cryptomator: 1.70 DMG-4333
• …

Volume Type

macFUSE

Steps to Reproduce

1. [First Step] Create new Vault on OneDrive
2. [Second Step] Try to open this vault with the latest iOS app under iOS 15.7.1

Expected Behavior

The OneDrive vault would open in Files App

Actual Behavior

The app reports 'Content Unavailable', contents could not be displayed due to unknown error.
Tried repeatedly, same result.
None of this happened with a Vault created on OneDrive with the previous Cryptomator build.
Logs.zip

Reproducibility

Always

Relevant Log Output

No response

Anything else?

No response

[tobihagemann]

Can you please enable Debug Mode, trigger the error, and then send us the log files to [email protected]? https://docs.cryptomator.org/en/latest/ios/settings/

If you want, review the log files yourself first and redact any sensitive information.

[HelixCA]

Hello Tobias Thanks for your fast reply. I am afraid that I actually addressed the problem last night and am therefore unable to send a log file. What I did was : - Delete an existing OneDrive CM folder on my Mac - Removed the existing folder within CM on the Mac - Delete the connection to the folder on my iPhone - Created a new folder on OneDrive using the 1.70 build on my Mac - Went to CM on my iPhone and tried to open the new folder. The errors consistently started from that point and I was completely unable to view the new folder in the Files App, hence my bug report. I went to CM on an iPad and had no problem opening the folder there. So, I deleted CM on my iPhone and re-installed the app and the OneDrive connection. The folder now opens every time without any issue. Unfortunately I cannot be any more specific. I originally thought that the problem was older iOS app with new 1.70 folder. As it worked fine on the iPad, that was obviously not the issue. I hope this is of some help. Cheers Steven

…

On Mar 3, 2023, at 2:42 AM, Tobias Hagemann ***@***.***> wrote: Can you please enable Debug Mode, trigger the error, and then send us the log files to ***@***.*** ***@***.***>? https://docs.cryptomator.org/en/latest/ios/settings/ <https://docs.cryptomator.org/en/latest/ios/settings/> If you want, review the log files yourself first and redact any sensitive information. — Reply to this email directly, view it on GitHub <#310 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ANXAIU5CFO6ZFKZATXXTR2DW2GOFTANCNFSM6AAAAAAVOIWVHM>. You are receiving this because you authored the thread.

[tobihagemann]

Thank you for reporting this! I think I'm able to reproduce this issue but it's really hard to track down. It seems like a caching issue. And it's quite possible that it also affects other cloud storage services that use the same cache technique (Google Drive, pCloud). I believe the crucial step is that you removed and re-created the vault on your Mac at the same path.

So indeed, the current workaround is to somehow invalidate this internal cache. Obviously, this happens with a re-installation. But I believe it's enough to kill the Files app and to try again (maybe not, I'm not 100% sure).

[HelixCA]

Hi Tobias The cache theory makes a lot of sense. I had opened the ver 1.6x vault from OneDrive just before I shut it down, created the new ver 1.7x vault, and then tried to open it again, resulting in the error messages. The devices that easily opened the 1.7x vault without error had been recently rebooted (clear cache) and I did not open the older version first. So, I think you are onto something ! Good hunting Steven

…

On Mar 8, 2023, at 6:20 AM, Tobias Hagemann ***@***.***> wrote: Thank you for reporting this! I think I'm able to reproduce this issue but it's really hard to track down. It seems like a caching issue. And it's quite possible that it also affects other cloud storage services that use the same cache technique (Google Drive, pCloud). I believe the crucial step is that you removed and re-created the vault on your Mac at the same path. So indeed, the current workaround is to somehow invalidate this internal cache. Obviously, this happens with a re-installation. But I believe it's enough to kill the Files app and to try again (maybe not, I'm not 100% sure). — Reply to this email directly, view it on GitHub <#310 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ANXAIUZR5SUQVA5WFUYRF5DW3BTQ7ANCNFSM6AAAAAAVOIWVHM>. You are receiving this because you authored the thread.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.