Keyboard and Quick Tile auto fill items inconsistent

[OJ7]

Steps To Reproduce

1. Create a login for 192.168.1.5:1234 and set URI match detection to Host
2. Create a login for 192.168.1.5:5678 and set URI match detection to Host
3. Navigate to 192.168.1.5:1234 (a page with a login form)

Expected Result

The keyboard auto fill and quick tile auto fill should both only have the login for 192.168.1.5:1234 show up.

Actual Result

The keyboard suggests both 192.168.1.5:1234 and 192.168.1.5:5678 (incorrect) while the quick tile only suggests 192.168.1.5:1234 (correct).

Screenshots or Videos

No response

Additional Context

I have many services running on one IP address with various ports. When I try to login to a service, the keyboard auto fill is useless since it shows a bunch of suggestions that match the IP address instead of the full host.

Build Version

Version: 2025.1.2 (19740)

What server are you connecting to?

US

Self-host Server Version

No response

Environment Details

• Device: Samsung Galaxy S22 Plus
• OS Version: Android 14 / One UI 6.1

Issue Tracking Info

• I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.

[bitwarden-bot]

Thank you for your report! We've added this to our internal board for review.
ID: PM-18593

[SergeantConfused]

Hello @OJ7,

Thank you for your report. I have raised this to the Engineering department for review; please feel free to post additional information, such as screenshots or a screen video recordings, if you wish.

Thank you again,

[SaintPatrck]

@OJ7 this occurs because of the different data available from the two methods. When using accessibility we are able to "scrape" the screen ourselves. When the Auto fill framework triggers we only have the domain and scheme available to match with.

Unfortunately, until more information is provided from the Autofill framework there will be an inconsistency in the results.

See my recent comment on #4586 for more details.