github-starred/android
2
0
Fork 0
mirror of https://github.com/bitwarden/android.git synced 2026-05-08 04:16:40 -05:00
Code Issues 1.1k Packages Projects Releases 122 Wiki Activity

[GH-ISSUE #5720] [PM-24828] Autofill does not propose correct vault entries (URI match detection) #14954

New Issue
Open
opened 2026-04-15 01:12:26 -05:00 by GiteaMirror · 3 comments
GiteaMirror commented 2026-04-15 01:12:26 -05:00
Owner
Copy Link

Originally created by @mu88 on GitHub (Aug 17, 2025).
Original GitHub issue: https://github.com/bitwarden/android/issues/5720

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

  • 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.
Originally created by @mu88 on GitHub (Aug 17, 2025). Original GitHub issue: https://github.com/bitwarden/android/issues/5720 ### 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: <img width="1651" height="349" alt="Image" src="https://github.com/user-attachments/assets/44fca669-3882-49b1-aa78-b566d9ff124a" /> <img width="1350" height="441" alt="Image" src="https://github.com/user-attachments/assets/42ff525d-4a98-4165-bfcd-ebe0e1cd97c4" /> As you can see, Bitwarden autofill finds two matches, which is correct. Here's the corresponding config from within the Bitwarden Windows app: <img width="608" height="710" alt="Image" src="https://github.com/user-attachments/assets/17f984cd-466d-49b4-bdc7-530a31c30b70" /> 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_: <img width="606" height="709" alt="Image" src="https://github.com/user-attachments/assets/063b5c95-6c81-4899-8760-6be559f9def5" /> ### 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.
GiteaMirror added the app:password-managerbug labels 2026-04-15 01:12:26 -05:00
GiteaMirror commented 2026-04-15 01:12:27 -05:00
Author
Owner
Copy Link

@bitwarden-bot commented on GitHub (Aug 17, 2025):

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

<!-- gh-comment-id:3194413519 --> @bitwarden-bot commented on GitHub (Aug 17, 2025): Thank you for your report! We've added this to our internal board for review. ID: PM-24828
GiteaMirror commented 2026-04-15 01:12:28 -05:00
Author
Owner
Copy Link

@pamperer562580892423 commented on GitHub (Aug 17, 2025):

Another user here... and just two things:

  1. Android and "ports" don't go well together - see this comment of a Bitwarden developer: https://github.com/bitwarden/android/issues/5084#issuecomment-2845722782

  2. The title of your issue is "PM-24828 Autofill does propose correct vault entries (URI match detection)" - so if it is correct, your issue could be closed already?!

<!-- gh-comment-id:3194535122 --> @pamperer562580892423 commented on GitHub (Aug 17, 2025): Another user here... and just two things: 1. Android and "ports" don't go well together - see this comment of a Bitwarden developer: https://github.com/bitwarden/android/issues/5084#issuecomment-2845722782 2. The title of your issue is "[PM-24828] Autofill does propose correct vault entries (URI match detection)" - so if it is correct, your issue could be closed already?! [PM-24828]: https://bitwarden.atlassian.net/browse/PM-24828?atlOrigin=eyJpIjoiNWRkNTljNzYxNjVmNDY3MDlhMDU5Y2ZhYzA5YTRkZjUiLCJwIjoiZ2l0aHViLWNvbS1KU1cifQ
GiteaMirror commented 2026-04-15 01:12:29 -05:00
Author
Owner
Copy Link

@h3kt0rx commented on GitHub (Oct 26, 2025):

Another user here... and just two things:

  1. Android and "ports" don't go well together - see this comment of a Bitwarden developer: Host Match Detection broken for URLs with ports #5084 (comment)
  2. The title of your issue is "PM-24828 Autofill does propose correct vault entries (URI match detection)" - so if it is correct, your issue could be closed already?!

I have the same issue as OP except with different application. Trying multiple variations without the port and all combinations of match detections, switching between Chase Bank website to see if it would auto fill there (it did every time) and jellyfin.local.

<!-- gh-comment-id:3448831928 --> @h3kt0rx commented on GitHub (Oct 26, 2025): > Another user here... and just two things: > > 1. Android and "ports" don't go well together - see this comment of a Bitwarden developer: [Host Match Detection broken for URLs with ports #5084 (comment)](https://github.com/bitwarden/android/issues/5084#issuecomment-2845722782) > 2. The title of your issue is "[PM-24828](https://bitwarden.atlassian.net/browse/PM-24828?atlOrigin=eyJpIjoiNWRkNTljNzYxNjVmNDY3MDlhMDU5Y2ZhYzA5YTRkZjUiLCJwIjoiZ2l0aHViLWNvbS1KU1cifQ) Autofill does propose correct vault entries (URI match detection)" - so if it is correct, your issue could be closed already?! I have the same issue as OP except with different application. Trying multiple variations without the port and all combinations of match detections, switching between Chase Bank website to see if it would auto fill there (it did every time) and jellyfin.local. [PM-24828]: https://bitwarden.atlassian.net/browse/PM-24828?atlOrigin=eyJpIjoiNWRkNTljNzYxNjVmNDY3MDlhMDU5Y2ZhYzA5YTRkZjUiLCJwIjoiZ2l0aHViLWNvbS1KU1cifQ
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
app:authenticator
app:password-manager
bug
bug-passkey
customer-support
duplicate
enhancement
good first issue
help wanted
needs-reply
needs-response
pull-request
Mirrored from GitHub Pull Request
 question
No Label app:password-manager bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/android#14954
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?