PhilippC / PhilippC/keepass2android
Database changed externally when synchronised using Nexcloud
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 6.2k
- Forks
- 478
- Avg merge
- 1h 4m
- Merged PRs (30d)
- 2
Description
Currently I am using version 1.12-r5-test2848.
Making changes to the database works for the first time after adding it to Keepass2Android but when opening the database for a second time Keepass2Android always reports that the database has been changed externally although it isn't.
Even when removing the database and the local backup from the App and adding it again the behaviour remains the same.
These are the toasts popping up when unlocking the database:
Unlock database: Source file and cache are synchronized
Quick unlock: Files are in sync
This message appears when trying to save the database:
Merge changes?
The database file was changed externally. Do you want to load and save the changes before merging? Select no if you want to overwrite the external changes.
Cancel
No, overwrite
Yes, merge
If then I choose overwrite or merge I can make changes without problems, even after locking it is still fine but as soon as I close the database and re-open, it happens again.
This is a bit irritating because one can never be sure if there are indeed external changes.
Something I noticed as well but I am not sure if it is related. The toasts with the same messages sometimes have a blue and sometimes a red background.
I will gladly provide additional information if required.
Contributor guide
No contributing guide indexed for this repository
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 file or test is identified in the report. Reproduce the repeated external-change warning with Keepass2Android 1.12-r5-test2848 using the described add, close, and reopen sequence, then trace the synchronization and save flow; done means the warning appears only when the database really changed externally.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, csharp
- Domain
- database, mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100