Files in file app can not be referenced by KeePassium / dupes on file change
Nobody has claimed this yet.
- Dominant language
- Swift
- Stars
- 2.5k
- Forks
- 1k
- Avg merge
- 2d 18h
- Merged PRs (30d)
- 13
Description
Expected behaviour
Keepassium (in my case) references a kdbx file in ios files app which is hosted on nextcloud. File could be changed by another client (KeePassXC on W10) an will be updated in nextcloud and files app for use in Keepassium.
There is similar issue in #1432 but it's not the same. See "Actual behaviour".
Actual behaviour
If a file was updated with KeePassXC, there are dupes on in files app for each save until I refresh. Dupes can be seen permanently in "Recent" tab. Seems to be a "new" file. Keepassium says (the former) "file not exists".
I can reproduce this with KeePassXC or KeePass-Client.
I tried with an text file without repro.
Also no repro by using another webdav integation for files app (e. g. Boxcryptor, FE FileExplorer).
Steps to reproduce
- Reference KDBX-file in Keepassium
- Change KDBX-file in KeePass or KeePassXC
- Nextcloud Webinterface shows no dupes.
- Nextcloud App shows no dupes.
- Files app in iOS shows dupes.
- KeePass shows "file no exists".


iOS version
14.3
App version
3.2.0.30
Server configuration
Operating system:
Ubuntu Server 20.04.2 LTS
Web server:
Apache 2.4.41
Database:
MySQL 8.0.22
PHP version:
PHP-FPM 2.7.4
Nextcloud version: (see Nextcloud admin page)
20.0.6
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source files, tests, or entry points are named. Start by reproducing the issue with an iOS Files reference to a KDBX file updated through Nextcloud, then trace the file-provider update and reference handling; done means updates no longer create duplicates or make KeePassium report that the file is missing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- swift
- Domain
- mobile-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100