Autofill on Android 12 doesn't seem to work

@mvettosi that's so great to hear. Thanks for the update!

We are aware of two issues that may be causing problems with Autofill using 1Password.

If you’re using Gboard, please make sure you have updated to the latest version on Google Play. Recent versions of Gboard had an issue where Autofill suggestions did not always appear on the suggestion strip.

We’ve also identified an issue in the 1Password Beta where Autofill is not available when signing into an app that uses the Android WebView. This includes apps like Amazon, Outlook, and Fastmail. We plan to have this fixed in the next beta release (7.9.1.BETA-3).

If you're using the latest version of Gboard and do not use 1Password Beta on Android, please let us know the app or website you’re having trouble with and we’ll do further investigation on our end.

Hi @"jack.platten" ,
thanks for your reply! Actually later in the day I tried rebooting the device and everything started to work... Sorry about that!

And thanks for the accessibility explanation, it really wasn't clear to me what it was supposed to do.

All good for now!
Cheers

I have been unable to access my passwords on pretty much every app on my pixel 6 pro because of this bug. A lot of people talk about gboard but I don't think it's related to keyboards, it doesn't work on SwiftKey either. My passwords are just stored with my Google account account and I don't use any other software to store or retrieve them so I would have thought it'd be smooth sailing like on my iPad device with the Apple passwords chain. disappointing

Hey @mvettosi:

I've just been doing some testing, by chance are you using Gboard or a different keyboard? With 1Password set as my Autofill provider in Android Settings, I was able to successfully fill my Amazon credentials in Chrome when using Gboard, but if I switched to SwiftKey, I needed to enable the accessibility option for 1Password as well for SwiftKey to show the option to Autofill using 1Password .

The accessibility shortcut you touched on does not actually trigger filling, it merely turns the accessibility option off and on.

Let me know how that goes!

Jack

Hello! I just installed 1password on my Pixel 4 with Android 12, and I also can't seem to get the app working at all.
I disabled google password manager in Chrome browser, also enabled all the 1password features, also rebooted my device, but when I tap on an empty login form in Chrome (for example, amazon.it) it prompts me Google's saved passwords, and 1password is nowhere to be seen.

Moreover, I tried enabling the 1password accessibility shortcut that places a 1password icon on the side of my screen, but it doesn't seem to be doing anything, I can move it around but any other interactions does nothing.

Am I missing something, or is the app just broken for Android 12 atm?

I have a pixel 4xl running the latest of Android 12 and am seeing this issue as well. I did see it mentioned that there was a relation to forms that split user and password fields to separate views. I see this issue in forms with both user and password fields on the same view.

Thanks for clarifying that jmjm and letting others know about the Gboard beta.

I hope your Pixel 6 arrives quickly, I think I'll be upgrading soon too!

1P_Timothy, I am still waiting to take delivery of my Pixel 6 Pro before I can say if Gboard beta "works" with 1Password for me.

Hello jmjm thanks for joining the conversation!

Have 1Password prompts returned to the inline suggestion bar for you since switching to the Gboard beta?