Forum Discussion

PLD99's avatar
PLD99
New Contributor
5 months ago

Pixel 10 issues

A new Pixel means new ways for Google to break things. Just wanted to see if anyone else can confirm and possibly make the 1Password team aware if they aren't already: Autofill within the app versi...
android
GolferWHH's avatar
GolferWHH
Occasional Contributor
5 months ago

I'm having similar problems since I got a new Pixel 10.    I've been going throught my Google Account and confirming everything is good.  I have 2-Step Verification on and when I try and change "Sensitive" information Google takes me off in a Catch 22 situation, starting with the same message as you note.  I'll try the delete and recreate a Passkey for my Google Account

  • mikeindc's avatar
    mikeindc
    New Contributor
    3 months ago

    Hopefully this helps someone...

    I started by changing the preferred autofill in chrome specifically from 1password back to Google. That allowed me to sign in. 

    Then I changed my preferred autofill for overall android settings under "passwords, passkeys & accounts" from 1password to none, and then back to 1password just to sort of force reset it. Then below that under additional services, I enabled google as well (it was disabled). This I think allows both to work. 

    Only downside now is Google sometimes overpowers 1password, but passkeys are working. Hopefully they'll work it out and I can turn off Google entirely. But for now you can toggle the settings based on what you're trying to do.