PhilippC / PhilippC/keepass2android
[BUG] Endless saving dialog (can not reproduce)
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:
After creating a new entry, a saving dialog appeared and stayed there forever. As stated in the title, i cannot reproduce the behaviour and just wanted to open the issue in case someone else experiences it in future.
Where i encountered the bug exactly:
- In a banking app, i wanted to create a new user/password.
- I used the Keepass2Android autofill to create a new entry.
- For saving, i needed to show my fingerprint and then my YubiKey via NFC.
- After the successful authentication, it started the endless saving loop.
Context: I use a KeepassXC Database synced over Dropbox and the "Password and Challenge-Response for Keepass XC" option with the helper app ykDroid and my YubiKey 5 with NFC.
Additional debugging information:
When i closed and reopened the app, the issue was still there. When i restarted the phone, the new entry wasn't there anymore and the saving loop was gone.
I then created the entry from Keepass2Android itself, so not redirected from my banking app, and it worked! I then used the entry in the banking app and also edited the entry from the autofill open to include the package name of the banking app in the keepass entry which also worked!
Using adb logcat, i found no warnings or errors from Keepass2Android. The only thing that made me curious was this log message:
03-11 09:50:22.764 1385 2421 W UsageStatsService: Unexpected activity event reported! (keepass2android.keepass2android/crc64c98c008c0cd742cb.SelectCurrentDbActivity event : 23 instanceId : 77745317)
I could not reproduce this bug again. I tried creating a new entry from another (browser) application but this time it worked. Maybe the restart of the phone fixed some wrong state.
Describe what you expected to happen:
I expected the new entry to be saved to my dropbox keepass xc database and the dialog to disappear.
What version of Keepass2Android are you using?
1.14-r4
Which version of Android are you on?
15
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
No source file, test, or entry point is identified. Start by trying the reported Keepass2Android autofill flow with fingerprint, YubiKey NFC, and the KeepassXC database context; done requires reproducing or isolating the failure and verifying that the saving dialog closes and the new entry persists.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, csharp
- Domain
- authentication, mobile, security
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100