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

Saved logins for subdomains not autofilling on Android Oreo #232

New Issue
Closed
opened 2025-11-07 08:32:00 -06:00 by GiteaMirror · 3 comments
GiteaMirror commented 2025-11-07 08:32:00 -06:00
Owner
Copy Link

Originally created by @Techn1x on GitHub (Jun 5, 2018).

I have a user/pass login saved, with URI for the login set to some-dev.testing.fakedomain.com:8080

Then, when I access the site

  • in Chrome, I right click the field > Bitwarden > it offers the correct autofill options for that whole domain, so this works
  • in Android, the notification to autofill appears, I tap it, then it takes me to "items for fakedomain.com" - but there are no items in there.

I have checked that Android has definitely synced the login, and it appears in the vault.
Am I doing something wrong? Or does the app not yet recognize subdomains?

OS: Android Oreo 8.0.0
Device: OnePlus 3

Originally created by @Techn1x on GitHub (Jun 5, 2018). I have a user/pass login saved, with URI for the login set to `some-dev.testing.fakedomain.com:8080` Then, when I access the site * in **Chrome**, I right click the field > Bitwarden > it offers the correct autofill options for that whole domain, so this works * in **Android**, the notification to autofill appears, I tap it, then it takes me to "items for fakedomain.com" - but there are no items in there. I have checked that Android has definitely synced the login, and it appears in the vault. Am I doing something wrong? Or does the app not yet recognize subdomains? OS: Android Oreo 8.0.0 Device: OnePlus 3
GiteaMirror commented 2025-11-07 08:32:01 -06:00
Author
Owner
Copy Link

@kspearrin commented on GitHub (Jun 5, 2018):

What URI match setting are you using?

@kspearrin commented on GitHub (Jun 5, 2018): What URI match setting are you using?
GiteaMirror commented 2025-11-07 08:32:01 -06:00
Author
Owner
Copy Link

@Techn1x commented on GitHub (Jun 5, 2018):

Didn't even see that setting! :D (I'm new to Bitwarden)

It's set to "Default Match Detection", which after reading the Match Detection documentation, seems to default to "Base Domain". I am guessing this is still an issue because the match behaviour between Chrome and Android probably shouldn't be different.

After some more investigation I found the following;

  • Removing the port number at the end of the URI makes no difference
  • Adding http:// to the start of the URI fixes the match detection on Android (this is fine since the website is HTTP only - perhaps this has something to do with it?)

So basically, on Android:
some-dev.testing.fakedomain.com:8080 doesn't work
http://some-dev.testing.fakedomain.com:8080 does work

@Techn1x commented on GitHub (Jun 5, 2018): Didn't even see that setting! :D (I'm new to Bitwarden) It's set to "Default Match Detection", which after reading the Match Detection documentation, seems to default to "Base Domain". I am guessing this is still an issue because the match behaviour between Chrome and Android probably shouldn't be different. After some more investigation I found the following; * Removing the port number at the end of the URI makes no difference * Adding `http://` to the start of the URI fixes the match detection on Android (this is fine since the website is HTTP only - perhaps this has something to do with it?) So basically, on Android: `some-dev.testing.fakedomain.com:8080` doesn't work `http://some-dev.testing.fakedomain.com:8080` does work
GiteaMirror commented 2025-11-07 08:32:01 -06:00
Author
Owner
Copy Link

@eliykat commented on GitHub (Apr 29, 2021):

Thanks for reporting this issue. Autofill problems can affect different sites, apps, or devices, and we’re working on improving this feature. To help us track and analyze affected sites, please lodge a report using the Google Form mentioned in this issue: #1389. Please also direct any discussion or questions to that issue. This issue will now be closed.

@eliykat commented on GitHub (Apr 29, 2021): Thanks for reporting this issue. Autofill problems can affect different sites, apps, or devices, and we’re working on improving this feature. To help us track and analyze affected sites, please lodge a report using the Google Form mentioned in this issue: #1389. Please also direct any discussion or questions to that issue. This issue will now be closed.
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
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#232
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?