PhilippC / PhilippC/keepass2android
[BUG] Save credentials from autofill does not work
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:
The flow for creating credentials from the autofill service does not seem to work.
I enter in credentials
The browser offers to save the credentials using Keepass2Android
On this screen, it looks like it's just opened the DB. Nothing to indicate it as saved it or to pick the folder
I tried Add entry, thinking it would have populated the URL, username and password
I also did a quick search to see if it created it in a default directory, but nothing.
I did read https://github.com/PhilippC/keepass2android/wiki/Documentation#creating-a-new-account, and it implies this flow was never implemented, but I'm not sure why. It is a much simpler flow than the one in the FAQ.
Phone: Z Fold 7
Browser: Comet (Chromium)
Describe what you expected to happen:
After the "Save username" dialog, it should go into the flow to save the credentials. You should pick the folder and then save the credentials to that folder.
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
Start at the Android autofill service and the “Save username” dialog described in the report, then trace the credential-save flow. Done means the flow lets the user choose a folder and saves the submitted URL, username, and password after the dialog, as expected by the reporter.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, csharp
- Domain
- mobile, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100