PhilippC / PhilippC/keepass2android
[BUG] Autofill doesn't work & returns user back to password database on cold start
Open
Nobody has claimed this yet.
bug
- 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:
- Start with some other keyboard, like Swiftkey.
- Force stop Keepass2Android to make sure you get a cold start
- Start some app, say Venmo, and tap the password field.
- When the autofill option comes up, select it, and type your database password to unlock it.
- Select the entry you want to autofill with.
- Observe that you are taken back to the password database, with no way to actually fill in the text with the entry you selected.
- Press Back to get out of the database screen.
- Select autofill again, and type your database password again, to unlock it again.
- Select the entry you want to autofill with again.
- Observe that now it works.
Describe what you expected to happen:
Autofill should work the first time.
This was not always a problem. For example, v1.09e-r7 works fine. This bug was introduced sometime later.
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 cold-start autofill flow on Android 16 with Keepass2Android 1.14-r4, beginning from another keyboard such as SwiftKey and an app such as Venmo. Compare the first unlock and autofill attempt with the second attempt and with version 1.09e-r7; done means the selected entry fills the password field on the first attempt.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, csharp
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100