bitwarden / bitwarden/android

[PM-24828] Autofill does not propose correct vault entries (URI match detection)

Open
#5,720 5 comments 3 reactions 0 assignees View on GitHub
app:password-manager bug
Dominant language
Kotlin
Stars
9.4k
Forks
1.1k
Avg merge
1d 14h
Merged PRs (30d)
67

Description

### Steps To Reproduce

Please see the following screenshots from Firefox running on Windows 11 with the Bitwarden extension enabled when visiting https://192.168.0.45/workoutTracker:

Image

Image

As you can see, Bitwarden autofill finds two matches, which is correct. Here's the corresponding config from within the Bitwarden Windows app:

Image

The entry is configured for two different websites, one for the IP address https://192.168.0.45/workoutTracker and another one for the hostname https://myRaspi/workoutTracker. Since there are multiple apps running on my `myRaspi`, the URI match detection _Starts with_ is used.

As already mentioned, this works fine on Firefox on Windows. However, when doing the same on Android using Firefox for Android and the Bitwarden Android app, two things happen:
1. Bitwarden does not suggest the correct item at all, neither when visiting https://192.168.0.45/workoutTracker or https://myRaspi/workoutTracker.
2. Bitwarden falsely suggests another vault entry of my Grafana app, running on https://192.168.0.45:3000 resp. https://myRaspi:3000

As you can see in the following screenshot from the Bitwarden Windows app for the Grafana entry, it is configured for port 3000 with URI match detection _Host_:

Image

### Expected Result

When visiting either https://myRaspi/workoutTracker or https://192.168.0.45/workoutTracker, Bitwarden should do the following on Android:
1. The two correct vault entries based on the URI match detection _Starts with_ are proposed.
2. Entries using the URI match detection _Host_ with a port (e.g. https://192.168.0.45:3000) must not be proposed.

### Actual Result

When visiting either https://myRaspi/workoutTracker or https://192.168.0.45/workoutTracker, Bitwarden does the following on Android:
1. The two correct vault entries based on the URI match detection _Starts with_ are not proposed.
2. Entries using the URI match detection _Host_ with a port (e.g. https://192.168.0.45:3000) are falsely proposed.

### Screenshots or Videos

_No response_

### Additional Context

_No response_

### Build Version

Android app 2025.7,2

### What server are you connecting to?

Self-host

### Self-host Server Version

bitwarden/self-host:2025.2.1-beta

### Environment Details

- Device: Fairphone 4
- OS: Android 14
- Firefox for Android `v142.0`

### Issue Tracking Info

- [x] 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.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.