Getting started with 1Password for your growing team, or refining your setup? Our Secured Success quickstart guide is for you.
Pixel 10 Pro Issues
I recently switched from an iPhone 16 to a Pixel 10 Pro and am experiencing significant functionality issues with 1Password that need to be addressed. The autofill feature is consistently unreliable. In Chrome, username and password autofill succeeds roughly half the time. When automatic filling fails, I have to manually click and hold to select "Autofill," which still frequently doesn't populate the form fields correctly. This forces me to open the 1Password app and manually copy credentials multiple times per day, which is both inefficient and frustrating. Native app integration has similar problems. Login functionality is inconsistent at best, and browser-based authentication within apps rarely works (I've had it succeed perhaps once since switching devices). Passkey functionality is particularly problematic. 1Password consistently fails to recognize available passkeys across multiple sites. This is reproducible every time I attempt to authenticate on Microsoft's website, where the passkey option simply doesn't function. Additionally, OTP codes still require manual copying and pasting rather than seamless integration. I've been a loyal 1Password user for years without experiencing these issues on iOS. The Android performance gap is substantial enough that it's affecting my daily workflow and making me reconsider the platform entirely. Could you please confirm whether your team is aware of these Android-specific issues and provide an estimated timeline for fixes? I need to understand if these problems are being actively addressed or if I should evaluate alternative solutions. I appreciate your time and look forward to your response.
Unable to create and save a passkey in Costco android app
I am getting the error message when trying to create a passkey in the Costco android app on my Samsung S22 Ultra phone: "Unable to save passkey. For security reasons, 1Password did not save this passkey. The associated URL for this passkey does not match the selected app."Passkeys Not Working On Android 16
Hi all, I set up a Passkey for my government portal site on my PC. The Passkey works fine on both my PCs, but not on Android (16). How do I set up 1Password so it will use my Passkey on the government app on my phone? Or, is there a way to export my Passkey from 1Password to my phone? How do I get it working? Thanks :)
Passkey Beta issues
Hello, Edit: Apologies in advance if this feels rant-y, please order the replies by oldest so that it makes sense! I just signed up for a test account to be able to use new login with Passkey beta. Super smooth setup, and I was surprised at how quickly I got signed into the new account on my laptop and have all my data in the new account! I have SSH keys in my vault for my NAS, GIT server and commit signing. They imported fine into the new account, and I signed out of my old account. Using a second passkey I saved to a yubikey, I was able to check out a repo, sign a commit and push changes back to the repo. I was also able to sign into a terminal on my NAS without any issue. On that same laptop I have a virtual machine for development work. I use MSTSC to remote into this machine, and I have WebAuthn devices forwarded to it. I'm using a Windows Hello and a Microsoft account to sign into the RDP session. I was also able to easily sign into my 1Password account, lock and unlock my account using the Yubikey connected to the host. When I tried to check out the repo using SSH I ran into an issue. It asked me to authenticate with my passkey for my git client to use my SSH key. Windows asked which device I wanted to use, I picked my Yubikey, entered the PIN and touched the key as normal. It did not succeed, I got a message saying "Unable to sign in, please try again later or contact support". Looking at the logs I see: INFO 2025-07-08T01:09:45.308+00:00 runtime-worker(ThreadId(18)) [1P:op-webauthn-authentication\src\models\sign_in_request_interpreter.rs:75] Found existing device key from disk or backup INFO 2025-07-08T01:09:45.308+00:00 runtime-worker(ThreadId(18)) [1P:op-webauthn-authentication\src\handlers\sign_in.rs:173] webauthn sign in -- Querying auth methods in an attempt to locate a passkey public key credential and challenge INFO 2025-07-08T01:09:45.475+00:00 runtime-worker(ThreadId(15)) [1P:op-webauthn-authentication\src\handlers\sign_in.rs:206] webauthn sign in -- Attempting to sign a challenge to authenticate a passkey INFO 2025-07-08T01:09:52.813+00:00 runtime-worker(ThreadId(15)) [1P:op-webauthn-authentication\src\handlers\sign_in.rs:216] webauthn sign in -- Authenticator assertion succeeded. Now verifying the authenticator's response with B5. INFO 2025-07-08T01:09:52.867+00:00 runtime-worker(ThreadId(15)) [1P:op-webauthn-authentication\src\handlers\sign_in.rs:248] webauthn sign in -- Assertion has been verified. Responding with an appropriate view model. INFO 2025-07-08T01:09:52.868+00:00 runtime-worker(ThreadId(15)) [1P:op-webauthn-authentication\src\models\authentication_coordinator.rs:186] Attempting unlock ERROR 2025-07-08T01:09:52.868+00:00 runtime-worker(ThreadId(15)) [1P:app\op-app\src\app\backend\webauthn_authentication.rs:201] General(WebAuthn unlock failed: AccountAlreadyUnlocked) ERROR 2025-07-08T01:09:52.869+00:00 runtime-worker(ThreadId(15)) [1P:op-webauthn-authentication\src\handlers\sign_in.rs:56] webauthn sign in -- General(WebAuthn unlock failed: AccountAlreadyUnlocked) INFO 2025-07-08T01:10:00.322+00:00 runtime-worker(ThreadId(18)) [1P:ssh\op-ssh-agent\src\lib.rs:639] Session was not authorized It might be worth noting that when signed into a RDP session like this, Windows Hello on the VM is not available. It's part of the reason I signed up for the beta, Passkey was easier than entering my 44 character master password every time I wanted to make a commit lolConfused With Passkey?
I have just created a Passkey for my government portal, as there were five hack attempts. After I created it and turned off my password, I logged out to check it. It logged in with no problems. It did not, however, scan my face. I figured it was in some sort of "cache". Then I locked 1Password and tried again. It logged in again, no problems, but still did not scan my face. EDIT - I just tried on my other PC. The same thing. It did not ask for my fingerprint. Is this because it already verified me with a Passkey when I logged in to Windows 11? I'm confused by this behaviour. Can anyone explain?How do I create Passkeys?
Everybody talks about but I can't do anything about it. Does anybody actually know how to create passkeys? reliably I have created 1 or 2 accidentally but I don't know what I did to make it happen. I cannot anything understandable on the Apple boards, I'm hoping to get better results here
iOS Passkey authentication request does not present correct passkey when provided with credentialId
We have an application at keys.coinbase.com that allows for webauthn registration and attestation with passkeys. A user can create a passkey and authenticate with that passkey. A user can also have multiple passkeys. After a recent iOS update, when a user has multiple registered passkeys for our Relying Party Domain (keys.coinbase.com) whose passkey names are identical (i.e. "Smart Wallet"), 1Password fails to request authentication for a specific one of the identical passkeys even an allowed credential is passed to the authentication function. For instance: Passkey 1 Name: "Smart Wallet" CredentialID: "123abc" Passkey 2 Name: "Smart Wallet" CredentialID: "456def" If both credentials exist and I try to authenticate specifically with Passkey 1 by providing the credentialId "123abc" to the authorization request, 1Password fails to display the appropriate credential. Instead, I see cross-platform prompts and an option to choose a 1Password credential from a subsequent tray (see screenshot). You can reproduce this issue on an iOS device with the latest version of 1Pass iOS by: 1. Go to https://coinbase.github.io/coinbase-wallet-sdk/ 2. Under "Wallet connection" > "eth_requestAccounts" > press Submit 3. Popup opens to "Sign in with Base" > Select "Create account" 4. Do not enter a "Passkey name" > Press "Continue" 5. Save passkey to 1Pass iOS by pressing "Continue" on the "Create a passkey?" system tray 6. In 1Pass UI tray that pops up, make sure you select to "Create new item for..." and press "Save" 7. Once you've saved the passkey, you will automatically land back on https://coinbase.github.io/coinbase-wallet-sdk/ 8. Scroll down to "Sign Message" section > "Personal Sign" > Press "Example Message" 9. A popup will open and ask you to sign an Example message, press "Sign" 10. Passkey authentication tray opens and suggests correct passkey, but DO NOT CONTINUE. Just note that 1Pass presented the correct passkey to sign with. 11. Now, close the passkey prompt with signing 12. In the top right corner of the page open (keys.coinbase.com), press the settings "gear" icon > Scroll down > Press "Sign out" 13. Popup closes and https://coinbase.github.io/coinbase-wallet-sdk/ warns you that your wallet was disconnected > Press "Yes" 14. Repeat steps 2 - 9 15. Passkey authentication tray opens and suggests cross-platform options with 1Pass listed at the bottom, but it does not offer a preselected passkey based on the credentialId. This is the bug.
