cryptomator
I am able to navigate the folder structure before the password dialog appears
Summary
If I tap on an encrypted folder before the unlock dialog appears, I am able to navigate it and also see some cached content.
Please agree to the following
- [x] I have searched existing issues for duplicates
- [x] I agree to follow this project's Code of Conduct
System Setup
- iOS: 26.1
- Cryptomator: 2.7.3
- iPad Pro
Cloud Type
iCloud Drive
Steps to Reproduce
- Tap on the "Folder" icon
- Tap on the Cryptomator Location
- Quickly tap on an encrypted (cached?) folder before the unlock dialog shows up
Expected Behavior
No content should be rendered. The Unlock Dialog is the only available option.
Actual Behavior
It's possible to tap deeper into the folder structure. The cached content of the encrypted folder is rendered.
Reproducibility
Always
Relevant Log Output
Anything else?
No response
I think that's the nature of how caching is done in the files app by Apple. We already invalidate the working set as soon as the vault gets locked so that recent files do not appear in the spotlight search on iOS.
Do you also see this behavior if you manually lock the vault and you are currently not inside the vault in the files app?
That's correct. I can navigate the vault even when it's locked. I also tested it by clearing the cache inside the Cryptomator settings, but the content is still visible. The documents cannot be opened, but the icons for each document show a portion of the related content, and the folder structures can be navigated. Until the "unlock dialog" takes control, that is.
Sounds like a duplicate of #423 or at least the observed behavior is related.
I can navigate the vault even when it's locked.
Can you be more specific for how long this is possible? In my experience, when opening the Files app, it takes just a few seconds until the unlock dialog appears (even without any interaction).
As @phil1995 has already mentioned, that's the best that we can do. The Files app by Apple has an internal cache that we can't access, so we do not have control over it. If we ever get the chance to improve this, we will, but that's up to Apple.
