PhilippC / PhilippC/keepass2android

After phone /Android upgrade: 1. App closes silently - 2. (forced) re-open needs reauthentication

Open
#3,047 7 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

question
Dominant language
C#
Stars
6.2k
Forks
478
Avg merge
1h 4m
Merged PRs (30d)
2

Description

Been using a previous version on my previous Android phone for years. A database kdbx could stay opened for weeks, even months - able to unlock via "quickunlock".

Now I switched hardware (phone), now on Samsung S23 , Andoid 15, OneUI 7.0. I open the kdbx-database, and when I wake up next morning - I find it closed. Sometimes it stays open for a few days, but will close silently.
It's an issue, as I need physical keygenerator to open it - I don't take that with me when leaving for the bank or supermarket.

1. Why does Keepass2Andoid close frequently, without prior ask or note?

2. Different issue: "Changes to the DB, Re-open it ?" - Always happened when having the kdbx opened on Desktop simultaneously. In previous installation (see above) however, the reopen was possible without full re-authentication . Nowadays, the "re-open?" behaves as if I open first time. Can it be avoided?Thanks!
Chris

v1.12r5

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing both reported behaviors on the stated Samsung S23 running Android 15 and One UI 7.0 with Keepass2Android v1.12r5. Investigate the silent database closure and the reauthentication required after simultaneous desktop use; done means both behaviors are explained and the agreed fixes are verified without disrupting database access.

Written by the indexing model from the issue text.

Assessment

Tech stack
android
Domain
mobile
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.