github-starred/android
2
0
Fork 0
mirror of https://github.com/bitwarden/android.git synced 2026-03-13 13:44:36 -05:00
Code Issues 144 Packages Projects Releases 116 Wiki Activity

Match detection doesn't recognize .lan URIs #2129

New Issue
Closed
opened 2025-11-26 23:08:48 -06:00 by GiteaMirror · 7 comments
GiteaMirror commented 2025-11-26 23:08:48 -06:00
Owner
Copy Link

Originally created by @timfeierabend on GitHub (Jan 15, 2025).

Steps To Reproduce

  1. In Chrome, browse to http://openwrt.lan/cgi-bin/luci/
  2. Select the username field.
  3. Select 'My vault' autofill option.

Expected Result

Display matching credentials for openwrt.lan.

Actual Result

No matching credentials found.

Screenshots or Videos

No response

Additional Context

openwrt.lan is my home router.

I have two URIs setup in the below order. Both use default match detection.

  1. http://192.168.1.1/
  2. http://openwrt.lan/

Match detection works for accessing via IP address.

When I manually find my credentials and select 'Autofill and save', http://openwrt.lan with default match detection is added as a new URI. This URI doesn't match either. I can repeat this process multiple times, each time resulting in the same URI being added.

Build Version

2025.1.0 (19622)

What server are you connecting to?

US

Self-host Server Version

No response

Environment Details

  • Device: Samsung Galaxy S24 FE (SM-S721U1)
  • Android version: 14
  • Google Play system update: January 1, 2025
  • Android security patch level: December 1, 2025
  • Input method: Gboard

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 @timfeierabend on GitHub (Jan 15, 2025). ### Steps To Reproduce 1. In Chrome, browse to `http://openwrt.lan/cgi-bin/luci/` 2. Select the username field. 3. Select 'My vault' autofill option. ### Expected Result Display matching credentials for `openwrt.lan`. ### Actual Result No matching credentials found. ### Screenshots or Videos _No response_ ### Additional Context `openwrt.lan` is my home router. I have two URIs setup in the below order. Both use default match detection. 1. `http://192.168.1.1/` 2. `http://openwrt.lan/` Match detection works for accessing via IP address. When I manually find my credentials and select 'Autofill and save', `http://openwrt.lan` with default match detection is added as a new URI. This URI doesn't match either. I can repeat this process multiple times, each time resulting in the same URI being added. ### Build Version 2025.1.0 (19622) ### What server are you connecting to? US ### Self-host Server Version _No response_ ### Environment Details - Device: Samsung Galaxy S24 FE (SM-S721U1) - Android version: 14 - Google Play system update: January 1, 2025 - Android security patch level: December 1, 2025 - Input method: Gboard ### 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 2025-11-26 23:08:48 -06:00
GiteaMirror commented 2025-11-26 23:08:49 -06:00
Author
Owner
Copy Link

@bitwarden-bot commented on GitHub (Jan 15, 2025):

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

@bitwarden-bot commented on GitHub (Jan 15, 2025): Thank you for your report! We've added this to our internal board for review. ID: PM-17112
GiteaMirror commented 2025-11-26 23:08:50 -06:00
Author
Owner
Copy Link

@Krychaz commented on GitHub (Jan 15, 2025):

Hello there,

Can you please try using different match detection option for this item like base domain or exact - https://bitwarden.com/help/uri-match-detection/

This should solve the issue. I'm closing this for now as it doesn't look like a bug.

@Krychaz commented on GitHub (Jan 15, 2025): Hello there, Can you please try using different match detection option for this item like base domain or exact - https://bitwarden.com/help/uri-match-detection/ This should solve the issue. I'm closing this for now as it doesn't look like a bug.
GiteaMirror commented 2025-11-26 23:08:50 -06:00
Author
Owner
Copy Link

@timfeierabend commented on GitHub (Jan 15, 2025):

Hi @Krychaz

Tested real quick with both base domain and exact match detection - no change in behavior.

When I am on my PC with the Bitwarden Password Manager browser extension (Firefox and Chrome), it correctly detects the credentials.

The MAUI Bitwarden app also correctly detected the credentials.

@timfeierabend commented on GitHub (Jan 15, 2025): Hi @Krychaz Tested real quick with both base domain and exact match detection - no change in behavior. When I am on my PC with the Bitwarden Password Manager browser extension (Firefox and Chrome), it correctly detects the credentials. The MAUI Bitwarden app also correctly detected the credentials.
GiteaMirror commented 2025-11-26 23:08:50 -06:00
Author
Owner
Copy Link

@Krychaz commented on GitHub (Jan 15, 2025):

@timfeierabend

Are you sure the URL is not modified in any way when accessing it via mobile?

@Krychaz commented on GitHub (Jan 15, 2025): @timfeierabend Are you sure the URL is not modified in any way when accessing it via mobile?
GiteaMirror commented 2025-11-26 23:08:50 -06:00
Author
Owner
Copy Link

@timfeierabend commented on GitHub (Jan 15, 2025):

@Krychaz

Yes. The URL is the same regardless whether I access it via my PC or my phone.

http://openwrt.lan/cgi-bin/luci/

Screenshot_20250115_111623_Chrome.png

@timfeierabend commented on GitHub (Jan 15, 2025): @Krychaz Yes. The URL is the same regardless whether I access it via my PC or my phone. `http://openwrt.lan/cgi-bin/luci/` ![Screenshot_20250115_111623_Chrome.png](https://github.com/user-attachments/assets/bc35361f-0f2e-4ea7-bca1-c97f6ed93a68)
GiteaMirror commented 2025-11-26 23:08:50 -06:00
Author
Owner
Copy Link

@timfeierabend commented on GitHub (Jan 22, 2025):

Hi @Krychaz, following up on this. Since I've opened this issue, I've tested trying to connect to my Synology NAS on my network via DNS name on my phone. Same behavior as reported above. Let me know if you need additional details or have questions. Thanks!

@timfeierabend commented on GitHub (Jan 22, 2025): Hi @Krychaz, following up on this. Since I've opened this issue, I've tested trying to connect to my Synology NAS on my network via DNS name on my phone. Same behavior as reported above. Let me know if you need additional details or have questions. Thanks!
GiteaMirror commented 2025-11-26 23:08:51 -06:00
Author
Owner
Copy Link

@timfeierabend commented on GitHub (Jan 31, 2025):

Update: I reached out to Bitwarden technical support regarding this issue. This issue is a known limitation with Android. Changing my URI match detection to Host resolved the issue. Hopefully this helps someone else!

The issue you're experiencing with the Android password manager not matching URIs for local .lan domains is a known problem. This issue often arises because Android has a history of difficulties resolving local domains, such as .local or .lan, which can affect how password managers like Bitwarden match URIs. The problem is compounded by the fact that some Android browsers, like Samsung Internet, do not handle local hostnames correctly, showing them as '--' and failing to match them properly. A workaround is to use IP addresses instead of local DNS names, although this can be inconvenient and may not resolve issues with port numbers. Another potential solution is to adjust the URI match detection settings in Bitwarden to 'Host', which can help in some cases by ensuring that the exact hostname is matched, though this may not fully resolve the issue with local domains.

@timfeierabend commented on GitHub (Jan 31, 2025): Update: I reached out to Bitwarden technical support regarding this issue. This issue is a known limitation with Android. Changing my URI match detection to **Host** resolved the issue. Hopefully this helps someone else! > The issue you're experiencing with the Android password manager not matching URIs for local .lan domains is a known problem. This issue often arises because Android has a history of difficulties resolving local domains, such as .local or .lan, which can affect how password managers like Bitwarden match URIs. The problem is compounded by the fact that some Android browsers, like Samsung Internet, do not handle local hostnames correctly, showing them as '--' and failing to match them properly. A workaround is to use IP addresses instead of local DNS names, although this can be inconvenient and may not resolve issues with port numbers. Another potential solution is to adjust the URI match detection settings in Bitwarden to 'Host', which can help in some cases by ensuring that the exact hostname is matched, though this may not fully resolve the issue with local domains.
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 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#2129
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?