github-starred/android
2
0
Fork 0
mirror of https://github.com/bitwarden/android.git synced 2026-08-30 17:33:42 -05:00
Code Issues 2.4k Packages Projects Releases 129 Wiki Activity

[GH-ISSUE #3910] BW APP for Android fails to auto fill using Starts With match detection #95236

New Issue
Closed
opened 2026-05-30 14:54:56 -05:00 by GiteaMirror · 9 comments
GiteaMirror commented 2026-05-30 14:54:56 -05:00
Owner
Copy Link
Copy Source

Originally created by @andreaippo on GitHub (Sep 11, 2024).
Original GitHub issue: https://github.com/bitwarden/android/issues/3910

Steps To Reproduce

This refers to the BW Android app

  1. Leave default match detection as it is
  2. Create an entry with a URI that overrides match detection to Starts With, e.g. http://192.168.1.1/myApp
  3. Go to http://192.168.1.1/myApp

Expected Result

BW proposes to autofill

Actual Result

BW does not propose to autofill

Screenshots or Videos

Screenshot_20240911-224338
Screenshot_20240911-224351
Screenshot_20240911-224411
Screenshot_20240911-224417

Additional Context

I need Starts with because I don't have just myApp hosted on my server, but several ones, each with its login info.

Therefore I need other entries for myApp2 etc under the same host.

Operating System

Android

Operating System Version

Android 14

Web Browser

Firefox

Browser Version

130.0

Build Version

Versione: 2024.8.1 (19099)

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 @andreaippo on GitHub (Sep 11, 2024). Original GitHub issue: https://github.com/bitwarden/android/issues/3910 ### Steps To Reproduce This refers to the BW Android app 1. Leave default match detection as it is 2. Create an entry with a URI that overrides match detection to Starts With, e.g. http://192.168.1.1/myApp 3. Go to http://192.168.1.1/myApp ### Expected Result BW proposes to autofill ### Actual Result BW does not propose to autofill ### Screenshots or Videos ![Screenshot_20240911-224338](https://github.com/user-attachments/assets/cb4675e1-8d38-43d2-95af-97bb3c8c43ca) ![Screenshot_20240911-224351](https://github.com/user-attachments/assets/23a6a14d-d347-4056-8817-164e047c4cdc) ![Screenshot_20240911-224411](https://github.com/user-attachments/assets/ef421e08-cd65-49a5-93c7-d0caa1ff96f8) ![Screenshot_20240911-224417](https://github.com/user-attachments/assets/102b9684-2e75-4390-b4b9-c33fbeb0caa4) ### Additional Context I need Starts with because I don't have just `myApp` hosted on my server, but several ones, each with its login info. Therefore I need other entries for `myApp2` etc under the same host. ### Operating System Android ### Operating System Version Android 14 ### Web Browser Firefox ### Browser Version 130.0 ### Build Version Versione: 2024.8.1 (19099) ### 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 bug label 2026-05-30 14:54:56 -05:00
GiteaMirror commented 2026-05-30 14:54:59 -05:00
Author
Owner
Copy Link
Copy Source

@andreaippo commented on GitHub (Sep 11, 2024):

I susepct that BW is not considering the full URI when looking up the vault. The 2nd screenshot shows a message saying "No element for 192.168.1.2", but it should've been looking for http://192.168.1.2/radar/login and so on...

Maybe the URI gets truncated too aggressively and no match could be found as a consequence?

<!-- gh-comment-id:2344760521 --> @andreaippo commented on GitHub (Sep 11, 2024): I susepct that BW is not considering the full URI when looking up the vault. The 2nd screenshot shows a message saying "No element for 192.168.1.2", but it should've been looking for http://192.168.1.2/radar/login and so on... Maybe the URI gets truncated too aggressively and no match could be found as a consequence?
GiteaMirror commented 2026-05-30 14:54:59 -05:00
Author
Owner
Copy Link
Copy Source

@andreaippo commented on GitHub (Sep 11, 2024):

Same problem with app 2024.5.1-10574.

I'm starting to think that it's by design...but then how can I have only ONE perfect match for each of my apps? They're all hosted on the same server, my home lab. Thanks

<!-- gh-comment-id:2344760525 --> @andreaippo commented on GitHub (Sep 11, 2024): Same problem with app 2024.5.1-10574. I'm starting to think that it's by design...but then how can I have only ONE perfect match for each of my apps? They're all hosted on the same server, my home lab. Thanks
GiteaMirror commented 2026-05-30 14:54:59 -05:00
Author
Owner
Copy Link
Copy Source

@bitwarden-bot commented on GitHub (Sep 11, 2024):

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

<!-- gh-comment-id:2344761247 --> @bitwarden-bot commented on GitHub (Sep 11, 2024): Thank you for your report! We've added this to our internal board for review. ID: PM-11999
GiteaMirror commented 2026-05-30 14:55:00 -05:00
Author
Owner
Copy Link
Copy Source

@sammbw commented on GitHub (Oct 22, 2024):

Hi there,

Your issue appears to be describing the intended behavior of the software. If you want this to be changed, it would be a feature request.

We use GitHub issues as a place to track bugs and other development related issues. The Bitwarden Community Forums has a Feature Requests section for submitting, voting for, and discussing requests like this one: https://community.bitwarden.com/c/feature-requests/

Please sign up on our forums (https://community.bitwarden.com/signup) and search to see if this request already exists. If so, you can vote for it and contribute to any discussions about it. If not, you can re-create the request there so that it can be properly tracked.

This issue will now be closed.

Thanks!

<!-- gh-comment-id:2428267823 --> @sammbw commented on GitHub (Oct 22, 2024): Hi there, Your issue appears to be describing the intended behavior of the software. If you want this to be changed, it would be a feature request. We use GitHub issues as a place to track bugs and other development related issues. The Bitwarden Community Forums has a Feature Requests section for submitting, voting for, and discussing requests like this one: https://community.bitwarden.com/c/feature-requests/ Please sign up on our forums (https://community.bitwarden.com/signup) and search to see if this request already exists. If so, you can vote for it and contribute to any discussions about it. If not, you can re-create the request there so that it can be properly tracked. This issue will now be closed. Thanks!
GiteaMirror commented 2026-05-30 14:55:00 -05:00
Author
Owner
Copy Link
Copy Source

@benkap commented on GitHub (Dec 18, 2024):

@sammbw, In what way this is the intended behavior? Using starts-with detection is not supported with auto fill?

<!-- gh-comment-id:2552082477 --> @benkap commented on GitHub (Dec 18, 2024): @sammbw, In what way this is the intended behavior? Using starts-with detection is not supported with auto fill?
GiteaMirror commented 2026-05-30 14:55:01 -05:00
Author
Owner
Copy Link
Copy Source

@Naushikha commented on GitHub (Aug 28, 2025):

When will this be fixed?
This issue is mentioned here as well: https://github.com/bitwarden/mobile/issues/1946

<!-- gh-comment-id:3231729543 --> @Naushikha commented on GitHub (Aug 28, 2025): When will this be fixed? This issue is mentioned here as well: https://github.com/bitwarden/mobile/issues/1946
GiteaMirror commented 2026-05-30 14:55:02 -05:00
Author
Owner
Copy Link
Copy Source

@SaintPatrck commented on GitHub (Aug 29, 2025):

Hi all,

The Autofill framework does not provide us the entire URL so we are unable to perform matching on path or port numbers, which according to the description is the expectation. We do mention this limitation in Match detection options on our Help page.

We have reported this lack of information to Google and requested the information be made available. As of now, we have not seen any movement on either ticket (https://issuetracker.google.com/issues/413521641 and https://issuetracker.google.com/issues/378464307).

As a temporary work-around, consider modifying the match type to Host so that at least partial matches are suggested instead of no suggestions showing.

You can also try using the Accessibility Quick Tile. We are often able to get the port and path information via this method because we have the ability to read and parse the screen ourself, instead of relying on the data provided by Android's Autofill API.

Also, feel free to +1 the linked tickets to let Google know it is negatively effecting your autofill experience.

<!-- gh-comment-id:3237633178 --> @SaintPatrck commented on GitHub (Aug 29, 2025): Hi all, The Autofill framework does not provide us the entire URL so we are unable to perform matching on **path** or **port numbers**, which according to the description is the expectation. We do mention this limitation in [Match detection options](https://bitwarden.com/help/uri-match-detection/#match-detection-options) on our Help page. We have reported this lack of information to Google and requested the information be made available. As of now, we have not seen any movement on either ticket (https://issuetracker.google.com/issues/413521641 and https://issuetracker.google.com/issues/378464307). As a temporary work-around, consider modifying the match type to Host so that at least _partial_ matches are suggested instead of no suggestions showing. You can also try using the Accessibility Quick Tile. We are often able to get the port and path information via this method because we have the ability to read and parse the screen ourself, instead of relying on the data provided by Android's Autofill API. Also, feel free to +1 the linked tickets to let Google know it is negatively effecting your autofill experience.
GiteaMirror commented 2026-05-30 14:55:03 -05:00
Author
Owner
Copy Link
Copy Source

@kaplanben commented on GitHub (Aug 31, 2025):

Anyone knows the behavior with other password manager clients? E.g. Lastpass, keeper? How do they handle this? Does all suffer from the same issue due to the lack of information returned by Android?

<!-- gh-comment-id:3240271013 --> @kaplanben commented on GitHub (Aug 31, 2025): Anyone knows the behavior with other password manager clients? E.g. Lastpass, keeper? How do they handle this? Does all suffer from the same issue due to the lack of information returned by Android?
GiteaMirror commented 2026-05-30 14:55:03 -05:00
Author
Owner
Copy Link
Copy Source

@SaintPatrck commented on GitHub (Sep 2, 2025):

@kaplanben, I briefly checked Dashlane and ProtonPass. This appears to be a consistent limitation.

Using https://fill.dev as a test site, I saved two different credentials with two different associated URI's; https://fill.dev/form/login-simple and https://fill.dev/form/registration-email

Image Image

Results

I could not locate "match type" options in either app. When I navigate to https://fill.dev/form/login-simple, both saved credentials are suggested by both apps, indicating the URI path is not respected by either.

Dashlane:

Image

Proton Pass:

Image
<!-- gh-comment-id:3245950039 --> @SaintPatrck commented on GitHub (Sep 2, 2025): @kaplanben, I briefly checked Dashlane and ProtonPass. This appears to be a consistent limitation. Using https://fill.dev as a test site, I saved two different credentials with two different associated URI's; https://fill.dev/form/login-simple and https://fill.dev/form/registration-email <img width="365" alt="Image" src="https://github.com/user-attachments/assets/60c874c4-7d39-419c-9aae-b5033aa074ec" /> <img width="365" alt="Image" src="https://github.com/user-attachments/assets/ca2bbc95-95b0-47db-a2e5-172b5dd6273a" /> ## Results I could not locate "match type" options in either app. When I navigate to https://fill.dev/form/login-simple, **both** saved credentials are suggested by both apps, indicating the URI **path** is not respected by either. ### Dashlane: <img width="365" alt="Image" src="https://github.com/user-attachments/assets/f2b26363-17d7-410e-aa6f-0c19cd2f4190" /> ### Proton Pass: <img width="365" alt="Image" src="https://github.com/user-attachments/assets/203b6bea-6b04-4172-8eac-6f091e56bf8f" />
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 labels bug
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
GiteaMirror ninjasurge (Kaehlen Rog)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/android#95236