PhilippC / PhilippC/keepass2android
[QUESTION] Cant sync my DB - How to see latest changes before deleting the local DB?
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 6.2k
- Forks
- 478
- Avg merge
- 1h 4m
- Merged PRs (30d)
- 2
Description
Version 1.14-r4
I made some changes in the local Keepass DB on my mobile phone. I still can access this local version and make changes. Its a very huge DB with lots of folders and entries.
For some unknown reason, it cant sync with the file on my webdav (Nextcloud) location anymore. Its also not possible to edit the webdav-location or credentials of this DB.
Is there any way to fix this issue so I can sync the local DB with the file on the webdav again?
If not:
I would like to delete this DB and readd it. But before I do so, I would like to view the latest changes and sync these manually with the DB on webdav.
How can i view the latest changes in the local keepass2android? I know how to sort by “Last modified,” but that doesn't help me if I have too many folders and don't know exactly which one I last edited entries in. Is there any way to see all entries in a plain view without folders and sort it by "Last modified"?
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 files, tests, or entry points are identified. Start by investigating database synchronization and WebDAV credential editing in version 1.14-r4, then determine whether the local database can expose all entries sorted by last modification. Done means restoring synchronization or documenting a reliable way to inspect and manually reconcile the latest changes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, csharp
- Domain
- databases, mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100