Skip to main content
June 13, 2023
Question

Bug: Unable to add an account to 1Password on iOS when using a Security Key for 2FA

  • June 13, 2023
  • 25 replies
  • 1529 views

When 2FA is enabled with a security key, all login attempts using 1Password 8 on iOS result in “perhaps there’s a typo” error. Tested on iPhone 12 Pro Max with iOS version 16.5 on 1Password v8.10.7. Logins on all other platforms including the Windows app, Firefox extension, and Safari browser work just fine.

A work-around for this issue is to disable 2FA for 1Password. Logins will succeed with no security key required. However after re-enabling 2FA, 1Password 8 shows as being offline. Tapping Sign In from the pop up warning or the red cloud icon does nothing.

25 replies

1P_Dave
1Password Employee
June 28, 2023

@kvr

I'm sorry that you're also affected by the issue. Our developers are still working on a fix and I don't have an ETA to share at the moment. When the fix is released you'll see it noted in our release notes: 1Password Releases

To workaround the issue and add your account to 1Password for iOS you can temporarily add a TOTP authenticator as a second factor and then remove it once the account is added to the app: Turn on two-factor authentication for your 1Password account

I'm sorry for the inconvenience.

-Dave

ref: dev/core/core#20680

June 29, 2023

The issue has been fixed in v8.10.8 in the BETA channel. To install the beta ios app, go to https://support.1password.com/betas/

1P_Dave
1Password Employee
June 29, 2023

@kvr

I'm not seeing a fix in beta 8.10.8-42 and the internal work item for the issue remains open. Can you confirm that you're able to use your security key to add your account to 1Password for iOS version 8.10.8-42 (BETA)? I'd be happy to pass along your report to our developers.

-Dave

June 29, 2023

@1P_Dave I can confirm that after installing ios beta 8.10.8-42, I could add my 1Password account to the app even though I only have hardware security keys as my 2FA method.

1P_Dave
1Password Employee
July 4, 2023

@kvr

I'm happy to hear that things are now working for you. The issue doesn't affect everyone so it's possible that something changed to get things working for you specifically. Our developers are continuing to investigate this issue and plan to release a permanent fix in a future update.

-Dave