WEBAUTHN IOS Error

Ask the Community Password Manager
, , ,
1

Having issue when trying to login to my bitwarden via iOS. I changed my master password but now I can’t login. I can’t proceed to use my security key. I can access the https://vault.bitwarden.com/ via Windows PC and also via the Windows Bitwarden App

image
image1179×2556 116 KB

Bitwarden Error
 Error Date: 2026-03-30T17:09:31-04:00
 Bitwarden 2026.3.0 (3023)
 Bundle: com.8bit.bitwarden
 Device: iPhone15,2
 System: iOS 18.6.2
 SDK: 2.0.0-4735-26e2b10
 Commit: bitwarden/ios/release/2026.3-rc44@9c1e16a5a651af4621e26b44babe598442e8de8b
 Build Source: bitwarden/ios/actions/runs/23023384383/attempts/1
 User ID: n/a

Error Domain=com.apple.AuthenticationServices.AuthorizationError Code=1004 "Unable to verify webcredentials association of LTZ2PFU5D6.com.8bit.bitwarden with domain vault.bitwarden.com. Please try again in a few seconds." UserInfo={NSLocalizedFailureReason=Unable to verify webcredentials association of LTZ2PFU5D6.com.8bit.bitwarden with domain vault.bitwarden.com. Please try again in a few seconds.}
The operation couldn’t be completed. Unable to verify webcredentials association of LTZ2PFU5D6.com.8bit.bitwarden with domain vault.bitwarden.com. Please try again in a few seconds.

Stack trace:
0   BitwardenKit                        0x00000001054b2efc __swift_memcpy0_1 + 30736
1   BitwardenShared                     0x000000010491193d __swift_memcpy1_1 + 6169
2   BitwardenKit                        0x000000010546cc91 __swift_mutable_project_boxed_opaque_existential_1 + 1993
3   BitwardenKit                        0x0000000105465445 __swift_instantiateGenericMetadata + 2777
4   BitwardenKit                        0x000000010546d07d __swift_mutable_project_boxed_opaque_existential_1 + 2997
5   BitwardenShared                     0x0000000104d9f499 __swift_memcpy35_8 + 36709
6   BitwardenShared                     0x0000000104da00ed __swift_memcpy35_8 + 39865
7   BitwardenShared                     0x000000010491692d objectdestroyTm + 1133
8   libswift_Concurrency.dylib          0x0000000193769241 7D7AD359-D240-391B-8E01-A01153D84033 + 414273

Binary images:
Bitwarden:                   0x0000000104630000
BitwardenShared:             0x0000000104908000
AuthenticatorBridgeKit:      0x0000000105424000
BitwardenKit:                0x0000000105458000
BitwardenResources:          0x00000001056c8000
BitwardenSdk_464161978EAC5FCE_PackageProduct: 0x0000000105788000
2

@yuber Welcome to the forum!

Could you first try to deinstall the BW app, restart your phone, reinstall it and try to log in again?

3

Still getting the same error

4

Hm. I’m not an iOS user myself…

I would recommend to contact BW support.

You could also see if there is a matching open (or closed) GitHub issue for this: Issues · bitwarden/ios · GitHub

PS: Do you use a hardware security key with always_UV set to enabled?

5

Sorry I don’t know how to set the always_uv, but I do have Hardware Security key for my BW Vault

6

Does your hardware security key enforce User Verification? (i.e. that you have to enter the PIN every time, also when you use it as a 2FA-passkey for Bitwarden?)

Only newer keys allow that, and it depends on the manufacturer how to enable that. – But if it’s not enabled on your key, then it’s not an issue here.

7

Ah, okay…

8

Yes. It always ask me to enter PIN. I’m using Yubikeys

9

@yuber To further clarify this: what exact YubiKey model do you have in use?

10

Hey all, the team is looking into this one, thanks for your patience!

1 Like
11

I have Yubikey Security Keys the Blue one with USB A and USB C the black ones

12

From what I found: I don’t think that they have always_UV enabled. :thinking:

EDIT: I meant to write “not enabled by default”. And since @yuber wrote, they wouldn’t even know how to change that setting, I also meant to express: then it’s very likely not enabled now on their YubiKey(s).

13

The alwaysUv option can be enabled or disabled by the user, and it is supported on the Yubikey Security Key series for firmware versions as of 5.7. However, the blue Yubikeys were discontinued in 2023, whereas version 5.7 of the firmware was not released until May, 2024. Thus, @yuber’s blue security key cannot have alwaysUv enabled. My understanding is that for later Security Key series hardware, the alwaysUv option is disabled by default. Thus, unless @yuber’s black Security Key has firmware version 5.7 and the alwaysUv option was enabled after purchase, then we can assume that neither key enforces alwaysUv.