Skip to main content
laugher
August 23, 2025
Solved

1Password is not respected as the default passkey manager on Android

  • August 23, 2025
  • 6 replies
  • 2177 views

Google Pixel 8 Pro
Android 16
1Password for Android 8.11.6

Today, I decided it was the day to setup Passkeys across the supported website/services. Started 1Password for Android - > Watchtower and selected uber.com. Went to the suggested URL after tapping "Use Passkey". URL went to https://account.uber.com/passkeys.

Logged in. Was presented the Passkeys page for Uber. Tapped + Create a passkey. Tapped Create a passkey at the popup dialog. Bam!

Google Password Manager pops up asking if I would like to create a passkey to sign in to account.uber.com. Cancelled.

I remembered doing this already so I went to the following places to check settings.

  1. Chrome -> ... -> Settings -> Google Password Manager -> Settings. Checked the following; Offer to save passwords (disabled), Automatically create a passkey to sign in faster (disabled), Auto sign-in (disabled).
  2. Chrome -> ... -> Settings -> Autofill Services. Checked Autofill using another service (Enabled). Tapped Android Settings and this is the 3rd place I check next. Alternatively, I can get to it by navigating as per point 3.
  3. Android Home Screen -> Settings -> Passwords, passkeys and accounts -> 1Password (Preferred service) - Enabled. Additional services: Microsoft Authenticator (disabled), Google (disabled).

Can you put in checks in place please so this doesn't happen? If Google is doing something naughty, can you please work with them to resolve this? Please?

Besides this, my experience on Android has been a mixed bag. Some login prompts, 1Password will have no issues popping up offering to autofill. But the MAJORITY of apps and websites, 1Password Autofill simply doesn't do enough. I have to jump back and forth to copy and paste passwords.

Please let me know how I can help you folks resolve this.

Best answer by 1P_Dave

Hello folks,

I'm sorry that you're running into issues with passkeys on your Android devices. Please try the following steps: 

  1. Turn AutoFill off and then back on: Set up Autofill
  2. Update Chrome to version 141 or later: Update Google Chrome
  3. Open Chrome.
  4. Type chrome://flags into your address bar and open this page.
  5. Search for Android autofill in the search box at the top of the flags page.
  6. Tap the drop down below Android autofill updates context for WebContents (#autofill-update-context-for-web-contents), then tap Enabled
  7. Tap the Relaunch button within the prompt at the bottom of the page


The same steps apply to Brave if you're using that browser instead. If things still aren't working then please send an email to support@1Password.com along with the following: 

  • A link to this thread: https://www.1password.community/discussions/1password/1password-for-android-cannot-become-the-default-passkeys-manager-and-other-issue/161255
  • The website or app where you're unable to save or sign in with passkey (even if it's all of them, please specify one or two). If the issue is with a website then share which browser you're using. 
  • Your Android device model. 
  • Your version of Android. 


After emailing in, you'll receive a reply from BitBot, our friendly robot assistant with a Support ID that looks something like
[#ABC-12345-678]. Post that here, and I'll be able to locate your message and make sure it's gotten to the right place. 

-Dave

 

6 replies

1P_Dave
1Password Employee
September 3, 2025

Hello @laugher! 👋

I'm sorry that saving a passkey in the Uber app using 1Password isn't working. So that the team and I can look into this further, can you reproduce the issue one more time and then I'd like to ask you to create and share a 1Password diagnostics report from your Android device:

Send a diagnostics report (Android)

Attach the diagnostics to an email message addressed to support@1password.com

With your email please include:

  • A link to this thread: https://www.1password.community/discussions/1password/1password-for-android-cannot-become-the-default-passkeys-manager-and-other-issue/161255
  • Your forum username: laugher


You should receive an automated reply from our BitBot assistant with a Support ID number.  Please post that number here.  Thanks very much!

-Dave

December 6, 2025

I'm having the exact same issue on my Samsung Galaxy S24 Ultra, regardless of website or app, only getting Google passkey prompts and not 1password prompts, so can't use stored keys 

December 19, 2025

I can confirm same issue, S25 ultra android 16, 1pass can't be used for passkeys. Tried multiple browsers. 

September 26, 2025

Hi 1Password team and community,

I'm a long-time 1Password user on Android, and while password autofill works perfectly, passkeys have never worked for me except for one random instance (can't recall the app). Currently, passkeys fail across all my browsers and apps, always falling back to Google's password/passkey manager with no apparent way to bypass or force 1Password.

Here's what I've tried:

  • Browsers: Brave, Chrome, Edge, and Firefox – no passkey autofill or creation in any of them.
  • Apps: Tested in various passkey-supported apps, but it always defaults to Google.
  • Troubleshooting: Uninstalled/reinstalled 1Password, cleared cache, toggled autofill settings in Android (set 1Password as default autofill service), and reset passkey manager preferences. I'm using the latest 1Password version available on Google Play Store (v8.10.x or newer).
  • Device: Samsung S25 Ultra running Android 15.

It's super frustrating as I'd love to use passkeys for better security, but I'm at a loss here. Has anyone else seen this issue, especially on Android 15 or Samsung devices? Any fixes, workarounds, or known bugs? Would appreciate any help!

Thanks

November 15, 2025

Experiencing the same issue on multiple apps, the passkey flow just seems clunky and unpolished. Would it be possible to simply allow users to deactivate this security check? It's always the same error that pops up whenever it fails, always has to do with the URL. If we could simply allow it to connect it'd solve this issue. Doesn't make sense that it takes months to fix something as trivial as this. It's really hurting the UX. I just want something that works constantly, and if it does fail at least have the option to bypass it and not be blocked by something like the URL. As a user I should be able to make those decisions. 

1P_Dave
1Password Employee
November 24, 2025

@recrewt 

I'm sorry that you're running into multiple issues with passkeys, I've merged your posts together into one thread. Regarding the issue in your initial post, are you still seeing the same problems with the latest versions of Android and 1Password for Android? There have been quite a few improvements to autofill in the last few updates which might have improved the situation. Let me know if you're still seeing that issue today.

The security warning can be caused by multiple different issues, if you're seeing the warning in multiple apps then we'll need to investigate those separately. Are you able to share the name of the other apps, aside from Costco, where you're seeing the passkey security warning? 

-Dave

Issue=FS-4398

December 11, 2025

I recently updated 1Password and my current versions are:

1Password 8.11.22
Chrome 143.0.7499.53
Android 16, Pixel 9 Pro Build/BP3A.251105.015

Android settings:
Preferred Service - 1Password

Chrome Settings:
Google Password Manager - all settings disabled
Autofill Services - Autofill using another service
Flags - #autofill-update-context-for-web-contents=enabled (I've tried disabling as well)

Now, when I try and login to websites using a passkey, I only get the option to "Sign in another way > View options > Use a different device." However, websites that also support id/password login still autofill those fields correctly from 1Password. I did not have this issue before the update. I've tried force stopping both apps, toggling to another service and back, and rebooting my phone. 

Is there a fix for this? My search of previous discussions and other forums hasn't found a working solution.

December 22, 2025

Reporting from a S23 Ultra, Android 16. Passkeys from 1password are completely broken atm. When is 1password going to crack-on with google? 

Users are not able to login with passkeys!

 

1P_Dave
1P_DaveAnswer
1Password Employee
December 23, 2025

Hello folks,

I'm sorry that you're running into issues with passkeys on your Android devices. Please try the following steps: 

  1. Turn AutoFill off and then back on: Set up Autofill
  2. Update Chrome to version 141 or later: Update Google Chrome
  3. Open Chrome.
  4. Type chrome://flags into your address bar and open this page.
  5. Search for Android autofill in the search box at the top of the flags page.
  6. Tap the drop down below Android autofill updates context for WebContents (#autofill-update-context-for-web-contents), then tap Enabled
  7. Tap the Relaunch button within the prompt at the bottom of the page


The same steps apply to Brave if you're using that browser instead. If things still aren't working then please send an email to support@1Password.com along with the following: 

  • A link to this thread: https://www.1password.community/discussions/1password/1password-for-android-cannot-become-the-default-passkeys-manager-and-other-issue/161255
  • The website or app where you're unable to save or sign in with passkey (even if it's all of them, please specify one or two). If the issue is with a website then share which browser you're using. 
  • Your Android device model. 
  • Your version of Android. 


After emailing in, you'll receive a reply from BitBot, our friendly robot assistant with a Support ID that looks something like
[#ABC-12345-678]. Post that here, and I'll be able to locate your message and make sure it's gotten to the right place. 

-Dave

 

April 20, 2026

Replacing message as I cannot add/edit (looking to add support ID)

January 10, 2026

@1P_Dave I was able to reproduce the problem described in this
thread with passkey on Android.
The workaround you specified does not help for me.
I filed a ticket, and I believe that @BrendanR1P was able to reproduce the problem on Android 16.

My details:

Google Pixel 9 phone
Android 16, Build number BP4A.251205.006.E1
Chrome 143.0.7499.147
1Password for Android 8.11.22