PhilippC / PhilippC/keepass2android
[BUG] Timestamp ≠ system time
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 6.2k
- Forks
- 478
- Avg merge
- 1h 4m
- Merged PRs (30d)
- 2
Description
Checks
- I have read the FAQ section, searched the open issues, and still think this is a new bug.
Describe the bug you encountered:
Changing a data record with subsequent saving of the database
Describe what you expected to happen:
Without additional information, it can be assumed from the user's perspective that the logged timestamp corresponds to the system time. However, that is not the case. In my case, there is a deviation of one hour.
Suggested solutions:
- Adjust timestamp to system time.
- Alternatively, output the time zone.
What version of Keepass2Android are you using?
1.10-pre
Which version of Android are you on?
14, One UI-Version 6.0
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
Reproduce the issue on Keepass2Android 1.10-pre with Android 14 and One UI 6.0 by changing a data record and saving the database. Compare the logged timestamp with system time, then verify that the result either matches system time or clearly displays the applicable time zone.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, csharp
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100