Getting started with 1Password for your growing team, or refining your setup? Our Secured Success quickstart guide is for you.
Forum Discussion
5 days 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 version of the Chrome browser (when apps redirect to the "light" version of Chrome for logins) does not work. Either the 1password popup never shows above the keyboard or near the login fields, or they show up but do not paste the login info. The "full" version of Chrome works fine
- This is probably unrelated to the Pixel 10 itself, but setting up my Google account on the new phone broke the passkey within 1Password. I get the error "You’re trying to sign in on a device Google doesn’t recognize, and we don’t have enough information to verify that it’s you. For your protection, you can’t sign in here right now" when attempting to sign in on the web. I deleted the passkey in 1password and created a new one and all is working now. The Pixel 10 did set up a hardware passkey when the account was first added, but it was never used.
The autofill thing is a bit weird, as I was previously on a Pixel 8, which was also on Android 16 and worked great. If there is a workaround please let me know, but I'm guessing this was caused Google breaking something!
1 Reply
- GolferWHHOccasional Contributor
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