Preliminaries
I have ensured that:
Versions
On iOS:
- Device: iPhone 14 Pro
- OS: 26.3.1
** Strongbox Version **
Describe the bug
When trying to sync a file that is contained in a Cryptomator Vault, I get an error saying I don't have the correct rights to open the file. I tried to switch to the "Directly Write to Database File (Dangerous)" setting in KeepassXC, but to no avail (the error happens from time to time even when the database hasn't changed).
To Reproduce
Steps to reproduce the behavior:
- Place a KeePass vault in a Cryptomator vault (with auto unlock duration)
- Unlock the Cryptomator vault through the Files app
- Add and unlock the vault in Strongbox
- Wait some time (a few days)
- Try to sync the vault
- See error
I can bypass the error by going back in the Cryptomator vault in the Files app, clicking on the KeePass vault, it opens Strongbox, then I cancel the "add vault" prompt, and then I can sync my vault. No errors for a few days, then it happens again kinda randomly.
Expected behavior
No error, sync works everytime.
Additional context
I don't know how to provide additional context, I guess this error could be linked to Cryptomator but I have no idea how to make sure of it.
Preliminaries
I have ensured that:
Versions
On iOS:
** Strongbox Version **
Describe the bug
When trying to sync a file that is contained in a Cryptomator Vault, I get an error saying I don't have the correct rights to open the file. I tried to switch to the "Directly Write to Database File (Dangerous)" setting in KeepassXC, but to no avail (the error happens from time to time even when the database hasn't changed).
To Reproduce
Steps to reproduce the behavior:
I can bypass the error by going back in the Cryptomator vault in the Files app, clicking on the KeePass vault, it opens Strongbox, then I cancel the "add vault" prompt, and then I can sync my vault. No errors for a few days, then it happens again kinda randomly.
Expected behavior
No error, sync works everytime.
Additional context
I don't know how to provide additional context, I guess this error could be linked to Cryptomator but I have no idea how to make sure of it.