PhilippC
After phone /Android upgrade: 1. App closes silently - 2. (forced) re-open needs reauthentication
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
Is such behavior normal ? ...the question too complex to troubleshoot, or stupid ?
1.) did you exempt KP2A from "battery optimization" settings in ANdroid? If the OS kills the app, you need to re-open the database. If the new OS is more "aggressive", the app can't change it.
2.) you mean when the app detects that the database has been changed and wants to reload it? Can you specify what exactly you selected as master password type? Sounds like you have a second factor?
Thank you for this tool - and the time to answer.
-
all settings I would know should be fine: screenshots.
-
yes that exact case. My kdbx is opened with keepass2android via "Password + OTP" and loading "OTP auxiliary file" on the App. (Guess that was your question).
1.) Your settings look fine. I cannot tell why you see the behavior, but app lifecycle is managed by Android, not by apps themself.
2.) For now, I suggest to update to 1.15 (https://github.com/PhilippC/keepass2android/releases/tag/v1.15-pre1) and only enable synchronization in your home wifi which should avoid unexpected syncs while on travel. I can't tell when I have time to look into this deeper, to be honest. Sorry.
I understand this has very much related to the OS / Android. I also understand, you would expect the app to stay operating in the background, with "quick unlock" to open it. Thanks for the feedback.