Android Android autofill is inconsistent with custom autofill behavior.

chutz
chutz
Community Member

@ag_timothy

This is a follow-up on https://1password.community/discussion/142758/android-autofill-is-inconsistent-with-custom-autofill-behavior.

However, with the 8.10.36 version even the workaround does not work anymore.

Now even when I open the pop up I get all the domains instead of only the one that I need.

Full report 👇

I open a site on Android Chrome and the autofill offers me seven options to fill in username and password, often none of which are correct. They are all entries on different domains under the same top level domain, with autofill set to "Only fill on this exact domain". There is also an eighth option "🔍 Open 1Password" and if I press it I am offered only one autofill entry, for the exact domain I am on (which also has "Only fill on this exact domain").

E.g., I have maybe 20 entries for services under various domains of internal.example.com and I have separate entries with URLs like:

https://apple.internal.example.com
https://banana.internal.example.com
https://cherry.internal.example.com
https://durian.internal.example.com
.....
https://zucchini.internal.example.com
The URL for each entry has autofill set to "Only fill on this exact domain".

I open https://durian.internal.example.com/ in my Android Chrome browser and when I tap the password prompt, the autofill on top of the Android keyboard offers me seven suggestions from the above list, sometimes none of which is the one I need.

Previously, in 8.10.16 when I tap on the eighth button "🔍 Open 1Password" I only see the one entry for durian.internal.example.com but with version 8.10.36 even in this case I see all the irrelevant domains I have, from a to z.

The desktop browser extension behaves as expected and gives me one choice for this domain.


1Password Version: 8.10.36
Extension Version: Not Provided
OS Version: Android 14
Browser: Not Provided

Comments

  • Cheesehed
    Cheesehed
    Community Member

    Maybe @Dave_1P can help?

  • Hello @chutz! 👋

    Thank you for following up. This issue is still open in our developer's backlog and I've let them know that you're still affected and that the workaround isn't working anymore.

    I'm sorry for the continued inconvenience.

    -Dave

    ref: dev/core/core#21542