PhilippC / PhilippC/keepass2android
[BUG] Database won't open since latest version
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:
Since version 1.15-r3, nothing happens when I try to open the keepass database. Neither the keyboard Enter nor the in app button for unlock does anything. Nothing happens. I already removed and reinstalled the app, restarted my phone. The buttons just won't do anything. No error, nothing.
EDIT: I switched back to 1.15-r2, and there, when I try to select the database on my onedrive, I get the error: authentication not successfull, but after that, I was able to login into my database (on onedrive) with my KeePass Password.
So 1.15-r2 is actually working for me.
Using Samsung S20.
Describe what you expected to happen:
The database will open as before, so I am actually able to use the app.
What version of Keepass2Android are you using?
1.15-r3
Which version of Android are you on?
13
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 on a Samsung S20 running Android 13 with Keepass2Android 1.15-r3: test both the Enter key and in-app unlock button, then compare with 1.15-r2 and the OneDrive database-selection flow. Trace the unlock path and OneDrive authentication behavior; done means an on-device database opens successfully in r3 without the unresponsive controls or failed authentication blocking login.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, csharp
- Domain
- authentication, cloud, mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100