Android: Auto fill dialog only shows entries with standard match detection

[quthla]

Entries with other match detection not shown. No issues with same entries on either iOS or browser.

[kspearrin]

Not enough information. Please explain the issue further.

[quthla]

Example

Url xyz.com/test

Add 2 entries. One with regular match detection, one with url starts with match detection. Navigate to xyz.com/test, it will only show the first entry

I'm using Chrome on Android in case that matters

[kspearrin]

Which autofill service are you using? Accessibility or Oreo/Pie autofill?

[quthla]

Pie autofill

[djboge]

I'm pretty sure I have this issue as well.

I have a bunch of logins for various subdomains of ".state.xx.us" i.e. mail or apps or payroll, etc. I have them all set to "begins with" match detection, because they all have separate logins.

When I visit any of them on Android Chrome, it says "no logins" if I tap the little box that comes up next to the login fields. If I tap out of that and go to the notification, it will show the login there.

[cognition9144]

Setting match detection to Host also still has the same effect as Base Domain.

E.g. A Login entry with URI www.example.com matches website abc.example.com

[Loakii]

I have the same issue with Pie autofill.

Bitwarden version: 2.1.0 (8 Jul 2019) (beta)
Google Chrome version: 75.0.3770.101

For example: I have a password stored for https://example.com:8443 with start with detection. Bitwarden would fail to give an option to autofill the information as shown below. Tapping "Go to my vault" shows the message "There are no items in your vault for ***".

If I set the detection to base domain the autofill option works as shown below.

[kspearrin]

The reason this happens is that the autofill APIs were only returning the "WebDomain" property of the page, which is just "domain.com" and does not include the scheme (http vs https). Therefore, when no scheme is present, we assume http://. If your "starts with" match detection is on a URI such as https://domain (s), then we do not have a match.

However, in Android Pie (API 28), they added an additional property to get the scheme as well (called WebScheme). We can now accurately detect the scheme of the page. I have added a fix. You can test the latest dev build with this fix here if you like: https://ci.appveyor.com/project/bitwarden/mobile/build/job/4ai23fw0a3frhsrm/artifacts

Devices on < Pie (28) will still default to http:// scheme and match detection against https:// stored URIs will not work.

[kspearrin]

Fix is also going out to play store beta, build 2019.

[Loakii]

I'm either doing something wrong or it's still not working on the dev build.

URI is saved with https://

Current version: 2.1.0 (2020)

[kspearrin]

@Loakii Are you using Android P? I was able to reproduce the issue before, but seems to work in my tests now.

1. URI: starts with "https://gith"
2. Visit github sign in page
3. Login is properly shown

[Loakii]

@kspearrin Ah yes! I guess it's the ports at the end that screw it up in my case.
I assume there's no way of making that work for now?

I have one domain with multiple webapps running on different ports and they all use different credentials.

[kspearrin]

Unfortunately, I do not think that android autofill APIs will give me the ports. Only the domain and scheme.

[Loakii]

I can work with base domains it's not a problem at all.
My purpose of using it was to add an extra filter.

The start with works correctly on pie with partial domains now. Cheers!