PhilippC / PhilippC/keepass2android
[BUG] Failed to create the passkey
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:
When using Keepass2Android to save passkeys on GitHub or Microsoft, it won't save them
The phone is Honor Magic8, and the operating system is Magic OS. It runs Android 16
When the option to save the passkey appears on the website, Keepass2Android can't save it automatically. When prompted to save it to Keepass2Android, there are no password entries displayed. You have to manually create a new entry, and then you can see the details of the passkey. But the website can't verify the passkey, so adding it fails. Could this be due to the keyboard or the Android system?
Describe what you expected to happen:
No response
What version of Keepass2Android are you using?
v1.16-pre1
Which version of Android are you on?
honor magic8 Android16
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 by reproducing passkey creation on GitHub or Microsoft with Keepass2Android v1.16-pre1 on the reported Honor Magic8 running Android 16. Investigate why no password entries are shown when saving to Keepass2Android, then verify whether a manually created entry can complete website verification. Done means passkey creation and verification work without manual entry creation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, csharp
- Domain
- authentication, mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100