Host matching on Android returns all androidapp:// entries #1035

Closed
opened 2025-11-26 22:37:17 -06:00 by GiteaMirror · 5 comments
Owner

Originally created by @realansgar on GitHub (Jun 9, 2020).

Originally assigned to: @mpbw2 on GitHub.

Describe the Bug

On Android with Host URI matching, all androidapp:// entries match login forms instead of the only the expected matching ones.

Steps To Reproduce

  1. Set Default URI matching detection to host.
  2. Have more than one password entry with different androidapp:// URIs
  3. Go to any app of your choice with a login form that is not a browser. For example com.example.app.
  4. Use the Bitwarden Autofill Popup to get matches for that login form.

Expected Result

Only the matching androidapp://com.example.app entries should match and be displayed.

Actual Result

All existing androidapp:// entries match and are displayed.

Environment

  • Device: OnePlus 3
  • Operating system: Android 9
  • Build Version: 2.4.2 (2501)
  • Is this a Beta release? No

Additional Context

This maybe has to do with #944 since this PR got implemented because of https://github.com/bitwarden/browser/issues/1267 and I can't remember this being a problem before this fix.

Originally created by @realansgar on GitHub (Jun 9, 2020). Originally assigned to: @mpbw2 on GitHub. <!-- Comment: Please do not submit feature requests. The [Community Forums][1] has a section for submitting, voting for, and discussing product feature requests. [1]: https://community.bitwarden.com --> ## Describe the Bug On Android with Host URI matching, all `androidapp://` entries match login forms instead of the only the expected matching ones. ## Steps To Reproduce <!-- Comment: How can we reproduce the behavior: --> 1. Set Default URI matching detection to host. 1. Have more than one password entry with different `androidapp://` URIs 1. Go to any app of your choice with a login form that is not a browser. For example `com.example.app`. 2. Use the Bitwarden Autofill Popup to get matches for that login form. ## Expected Result <!-- Comment: A clear and concise description of what you expected to happen. --> Only the matching `androidapp://com.example.app` entries should match and be displayed. ## Actual Result All existing `androidapp://` entries match and are displayed. <!-- Comment: A clear and concise description of what is happening. --> <!-- Comment: If applicable, add screenshots and/or a short video to help explain your problem. --> ## Environment - Device: OnePlus 3 - Operating system: Android 9 - Build Version: 2.4.2 (2501) - Is this a Beta release? No ## Additional Context <!-- Comment: Add any other context about the problem here. --> This maybe has to do with #944 since this PR got implemented because of https://github.com/bitwarden/browser/issues/1267 and I can't remember this being a problem before this fix.
Author
Owner

@Racle commented on GitHub (Jun 22, 2020):

+1
Annoying issue.

I've changed manually every androidapp:// uri to use "Starts with" detection mode so it won't interfere anymore. Quick but unnecessary workaround.

@Racle commented on GitHub (Jun 22, 2020): +1 Annoying issue. I've changed manually every androidapp:// uri to use "Starts with" detection mode so it won't interfere anymore. Quick but unnecessary workaround.
Author
Owner

@timcappalli commented on GitHub (Jul 2, 2020):

Seeing the same thing here. And when I click Use and Save, it just keeps creating additional URI entries.

IMG_20200702_095319

@timcappalli commented on GitHub (Jul 2, 2020): Seeing the same thing here. And when I click Use and Save, it just keeps creating additional URI entries. ![IMG_20200702_095319](https://user-images.githubusercontent.com/6476604/86368091-c829b600-bc4a-11ea-972d-0a8843f65c6a.jpg)
Author
Owner

@timcappalli commented on GitHub (Aug 19, 2020):

Has there been any movement on this? This is a pretty major bug to be sitting idle for so long.

@timcappalli commented on GitHub (Aug 19, 2020): Has there been any movement on this? This is a pretty major bug to be sitting idle for so long.
Author
Owner

@bugQ commented on GitHub (Nov 30, 2020):

I've changed manually every androidapp:// uri to use "Starts with" detection mode so it won't interfere anymore. Quick but unnecessary workaround.

Here to thank you for the hint, and to mention that "Default" match detection also works properly. This issue popped up for me when I switched the order of the URIs without checking match detection modes to work around #1120, which is also pretty annoying.

Despite the existence of workarounds, I agree that this deserves attention.

@bugQ commented on GitHub (Nov 30, 2020): > I've changed manually every androidapp:// uri to use "Starts with" detection mode so it won't interfere anymore. Quick but unnecessary workaround. Here to thank you for the hint, and to mention that "Default" match detection also works properly. This issue popped up for me when I switched the order of the URIs without checking match detection modes to work around #1120, which is also pretty annoying. Despite the existence of workarounds, I agree that this deserves attention.
Author
Owner

@WROIATE commented on GitHub (May 6, 2021):

+1

@WROIATE commented on GitHub (May 6, 2021): +1
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/android#1035