PhilippC / PhilippC/keepass2android
[BUG] T-Mobile app auto-fill works incorrectly
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:
When I try to auto-fill the credentials into the official T-Mobile app, the password is autopopulated into both fields.
The entry in the app is maintained correctly
Describe what you expected to happen:
- I unlock the app
- Auto-fill is triggered
- The creds are going to the dedicated fields
What version of Keepass2Android are you using?
1.11-r0
Which version of Android are you on?
14
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 issue on Android 14 using the official T-Mobile app and Keepass2Android 1.11-r0, checking how the username and password fields are identified during auto-fill. The fix is done when the username and password populate only their dedicated fields while the stored entry remains unchanged.
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
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100