Getting started with 1Password for your growing team, or refining your setup? Our Secured Success quickstart guide is for you.
[BETA - WIN] Unlock with Device doesn't work
I'm using the 1Password BETA on Windows 11 and I've been trying out the "Unlock with Device" feature since its release. Unfortunately, I've never managed to get it to work. Each time it fails to unlock, I'm prompted for my master password, which makes the whole experience less convenient than just using Windows Hello/TPM on its own. I haven't seen a lot of discussion about this feature, and the dedicated Reddit thread seems to be quite inactive with little to no feedback or discussion. It's tough to tell if this is a widespread issue or if I'm doing something wrong. I've seen a few others mention similar problems, but I haven't come across any posts from users who have actually gotten it to work consistently. I'm keen to help get this feature off the ground. Are there any specific troubleshooting steps I can take or logs I can provide that would be helpful for the developers? I'm happy to provide any information that could assist in resolving this issue.
Transparency gone from drag and drop under Wayland
The fix that allows dragging and dropping credentials, at all, also breaks the transparency that facilitates hitting the drop target. It only occurs when the ELECTRON_OZONE_PLATFORM_HINT=auto environment variable is set, and it makes the content fully opaque, complete with little black triangles at the corners, outside the rounded blue corners of the dragged item.
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 lol
"Sign In With" Provider Not Available
When I add a "Sign in with" option to a login, I can't select any of my existing logins as the correct credentials. I seem to only be offered providers such as Google, Facebook, Twitter/X, etc. For example, Shop (shop.app, also known as Shopify?) is a provider that is linked to many, many stores ... at least in Australia. It's great that I can just sign in with Shop when I'm on a new site and checking out, but I'd like to remember that's how I logged in and 1PW just doesn't allow it. I see this has been raised before and there's a thank you message from the support staff along with these "ref" numbers, such as: ref: PB-48105670 ref: PB-48105687 What are these numbers? How can we use them to check up on the status of a request? Google only finds the one specific thread where this number was posted before the conversation was locked so it seems to perhaps just be a number to make people think something is being done when really the request is thrown onto a pile that is never really looked at? Any information on how to follow up on these would be helpful, the "Sign in with" feature has been out for a while and people have been requesting this a lot so if it's not even turned up in a beta build, I'm concerned at 1PW's turnaround time for adding an easy feature to their software; even if it's rolled out in two phases where the first is just cosmetic until the second phase actually introduces functions like auto-forwarding and selecting the provider for login etc. Thanks team.
TouchID / Apple Watch issues with macOS Tahoe RC1
I've observed this in versions 81112020 (Nightly), as well as the corresponding beta and release builds. After installing the Tahoe RC1 (26.0/25A353), I've found that Touch ID has become a bit quirky. Under Preferences → Security, altering the Touch ID and Apple Watch settings, I've seen the following, when trying to unlock 1Password (or access ssh keys, etc.): Touch ID On Touch ID off Apple Watch On One of two things happen: Touch ID prompt appears on top of the Apple Watch prompt. Using Touch ID dismisses the Touch ID prompt, but does not unlock 1Password until the Apple Watch prompt is dismissed by approving from the Apple Watch. Dismissing the Apple Watch prompt by pressing escape requires that I use my account password to unlock. If I unlock using my password with just Touch ID enabled, I can then enable Apple Watch, and unlocking works as expected. Works as expected. Apple Watch Off Prompted for my account password with the message, "Touch ID sensor is currently unavailable. You need to sign in using your account password." After that, I can lock and unlock using Touch ID. Works as expected.
date format still a problem on Mac
On my 1P for Mac, dates can entered according to the region settings but are shown in US standard. The date 18 June 2025 is shown as 6/18/2025 on my machine even though my OS region is set to a European country. If I go to edit the day, the layout switched back to a euro-standard view as it always should have been (i.e. 18/6/2025). You most recent update to 1O for iOS 8.10.28 has this fix: "Created and modified dates for items are now formatted according to your operating system's language settings and standards specified by the Unicode Consortium." Can this please be fixed on the Mac version also. 1Password Version: 8.10.30 Extension Version: Not Provided OS Version: Mac 14.3.1 Browser: Not Provided
