PhilippC / PhilippC/keepass2android
[BUG] Need to open app twice after locking when screen off or during 1 minute idle
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:
On the Samsung Galaxy S10 and Samsung Galaxy S23 , if the app doesn't have battery optimisation disabled and the app runs in the background for more than 1 minute, or if lock when screen off is enabled and the screen is turned off, the next time the app is opened it will immediately close. Then the second time the app is opened it will bring up the unlock prompt. Also, with battery optimisation, after 1 minute the log recorded this and the Keepass2Android stopped:
W ActivityManager: Stopping service due to app idle: u0a661 -2m14s225ms keepass2android.keepass2android/crc64dd09b2a2e58bb27d.OngoingNotificationsService
It looks like the same thing happens if I force close the Keepass2Android service.
Describe what you expected to happen:
I expected the unlock prompt to open the first time I re-opened the app not for the app to just close.
What version of Keepass2Android are you using?
1.09e-r7
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 the behavior on Android 13 using a Samsung Galaxy S10 or S23, with battery optimisation enabled or lock when screen off enabled. Start by investigating the OngoingNotificationsService mentioned in the log and the force-closed service path; done means the unlock prompt appears on the first app launch after the screen is off or the app has been idle.
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