PhilippC / PhilippC/keepass2android
[BUG] App only opens every other attempt
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:
When the app is on the Unlock database screen it only opens every 2nd time I try to press the button to open it from the home screen or the app drawer. Every other time an animation plays, but the app does not open.
When I'm in the settings screen inside the app or have unlocked my database I can open the app from the home screen just fine every time. Switching to it via the recent apps menu also works every time, no matter what state the app is in.
I have enabled "Always show crash dialogue" in the developer options, but there's no crash dialogue when the app doesn't open.
This is a new phone, running HyperOS 3.0.4.0 on Android 16. My previous phone running Android 11 with the same app version does not experience this issue. I also disabled battery restrictions for this app, no change in behaviour.
https://github.com/user-attachments/assets/6451eaad-3863-469d-9ac1-6865e23b6b5d
Describe what you expected to happen:
No response
What version of Keepass2Android are you using?
1.14-r4
Which version of Android are you on?
16
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 launch attempt from the home screen or app drawer while the app is on the Unlock database screen, using Android 16 and Keepass2Android 1.14-r4. Compare this with launches from settings, the recent-apps menu, and an already unlocked database; done means the app opens on every attempt without regressing those working paths.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, csharp
- Domain
- mobile-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100