Google Passkeys

Hello @shadowplayer! 👋

I'm sorry that you're having trouble logging into your Google account using a passkey. Do you see a button labeled Try another way? What happens when you press that?

If that doesn't work then, if you open chrome://settings/passwords in Chrome, do you see that "Offer to save passwords" is disabled? You should see a message that says that "1Password – Password Manager is controlling this setting".

Finally, do you happen to a period in your Google account email address? We're tracking an issue that might be related.

-Dave

ref: dev/core/core#22255

I am getting this same issue in Edge in the Dev and Production channels on Windows. I have the latest Beta app and Extension installed. I just get the system prompt. I don't have any saved passwords in Edge. 1Password is controlling the save password setting and I do not have a period in my Google account email address.

@shadowplayer

I have the same problem, as do a number of other people. There is another thread here:

https://1password.community/discussion/comment/691633

I have not seen any fix (that works) or formal acknoledgement of this - and its extremely annoying. If you see either please do highlight!

@1P_Dave - please can you comment on this

I have the same problem as the OP, but only with one of my three google accounts.

Of the other two, however, only one works, as the other is using the wrong pass key. It looks like it's trying to use the first pass key in the list.
Let's say that I have 3 google accounts, g1, g2, and g3.
g1 works fine with the pass key, g2 prompts me with the browser built in pass key prompt as the OP and g3 uses the pass key from g1.

I managed to find out why the browser prompts for the pass key, if you have automatically created passkeys (apparently android phones create one on login), you'll get the prompt.
After I deleted the automatically created passkeys, 1password was able to use the passkey.

@shadowplayer you might want to check if you have such automatically created passkeys as well.

@rco, I don't see any option to delete the automatically-created passkey for my Android device. How did you delete that passkey?

@oxalate >

1.Go to your Google Account.
2.On the left navigation panel, select Security.
3.On the Your devices panel, select Manage all devices.
4.Select the device and then Sign out.
If multiple sessions appear with the same device name, they could all come from the same device or multiple devices. If you want to make sure there’s no account access from a device, sign out of all the sessions with this device name.

Source: https://support.google.com/accounts/answer/13548313?hl=en#zippy=%2Cremove-a-passkey
Can be found under Remove a passkey automatically created by Android.

@rco, thanks; I didn't realise I needed to sign the Android device out.

I tried that, then logged out. When I try to log in again, Chrome prompts me to create a new passkey for Google, meaning that 1Password still isn't presenting my saved passkey. Meh.

@oxalate yeah, I forgot to mention that the passkey will be re-created once you login again using your android device, signing out is not really a valid fix for this anyway. It's up for 1password team (@1P_Dave) to figure this one out.

Question, you are doing all this on your android device correct? I was confused about you not being able to use the 1password passkey after removing the google autogenerated ones. But yes, if you are doing it on your android device, then you were doomed from the beginning because of the auto-generated passkey on login😅.

@rco, I was using Chrome on Windows 10 when I removed the Android passkey and then tried signing in again. 1Password had my Google passkey saved, but I couldn't get past the Chrome prompt for a physical key (a security key, or my phone), just as happened https://1password.community/discussion/141544/google-1pw-beta-browser-extension-doesnt-present-my-passkey.

For now, I've just deleted the 1Password passkey from my Google account and from my 1PW login for Google. Maybe I'll try again if the 1PW folks announce that this behavior has been corrected, but until then I'm back to a password and 2FA. :-(