PhilippC / PhilippC/keepass2android

[BUG] Autofill doesn't work & returns user back to password database on cold start

Open
#3,213 0 comments 0 reactions 0 assignees View on GitHub

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:
  1. Start with some other keyboard, like Swiftkey.
  2. Force stop Keepass2Android to make sure you get a cold start
  3. Start some app, say Venmo, and tap the password field.
  4. When the autofill option comes up, select it, and type your database password to unlock it.
  5. Select the entry you want to autofill with.
  6. Observe that you are taken back to the password database, with no way to actually fill in the text with the entry you selected.
  7. Press Back to get out of the database screen.
  8. Select autofill again, and type your database password again, to unlock it again.
  9. Select the entry you want to autofill with again.
  10. 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

  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

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.