Bitwarden app signed me out & wont accept email or Yubikey!

iPhone 12 mini, latest iOS (26.0), latest Bitwarden (2025.8.1), etc. This VERY GOOD software decided to sign me out for some reason. Well, no problem, lets just sign back in…oh…wait…it wants my 2FA (Yubikey)…ok, it asks for Yubikey PIN…and it asks its again…and again…and again…it never completes it and never allows me to sign back in!

Oh well, Im just going to sign in with my computer and add some other 2FA method, like email. Nice. Done. Now, lets go to Bitwarden app and try that as 2FA… “AN ERROR HAS OCCURED. COULD NOT SEND VERIFICATION EMAIL. TRY AGAIN.”

Ok, I just use my recovery code to get in…oh wait…using recovery code AUTOMATICALLY deletes all my 2FA:s…nope, thats not what I want to do.

Finally got to the point of enabling TOTP as 2FA and that worked.

Yubikeys work, I tryed 2 of them on computer (login to Bitwarden) and on iPhone. iPhone works, no problem using Yubikeys on any sites etc. either. But when trying to actually sign into my Bitwarden, it never stops asking for PIN and never proceeds. Email 2FA works on computer just fine.

Maybe similiar to this problem?
Token2 Fido2 Key Androd 14 Issue - Ask the Community / Password Manager - Bitwarden Community Forums

:face_with_peeking_eye: :cold_face: Ok folks, this is a situation that should NEVER, EVER happen! Im completely unable to sign into my Bitwarden with my phones app. No 2FA works. Nothing helps. THIS SHOULD NOT HAPPEN. This is a major issue! Terrible! I cant use this kind of VERY GOOD software that completely locks me out of my account and stops working in critical time I need it to work!!! Unexcusable! :face_with_symbols_on_mouth:

@mmja Did you try do deinstall and reinstall the app?

If we are speaking of “passkey”-2FA (FIDO2), then you shouldn’t get asked for the FIDO2-PIN when logging in… Do you have a newer YubiKey model and changed the UV flag?

Hi @mmja when requesting help in this community supported space, please ensure you review the community guidelines.

Yes, new model and UV flag is set. It worked fine few versions ago, but Im not sure “since what version” this bug came, because I was signed in to the app, so I didnt need to use 2FA in it. But now I would need it, but cant get it to work. I might try to remove the UV flags temporary to see if it fixes the issue.

I tryed removing and then reinstalling the Bitwarden…guess what? Now I cant access ANY of my apps ANY settings in my iPhone!!! The settings menu freezes when I go to “settings” - “apps” and touch anything!!! This was DIRECT RESULT of me removing and reinstalling the Bitwarden app. I could access the “Settings” - “apps” - literally any apps settings BEFORE I removed and reinstalled Bitwarden. SO IN ESSENCE, BITWARDEN JUST BROKE MY IPHONE TOO!!! Rebooting the iPhone does not help. Only after I had again removed the Bitwarden and then rebooted, this bug was gone and I can again access the settings of my apps! HORRIBLE! Bitwarden literally broke my iPhone, I dont know how this is even theoretically possible to happen, but it did happen! Luckily rebooting, removing the app and rebooting again fixed the issue.

Also:
Please tell me, what is the logic in “using recovery code AUTOMATICALLY deletes all my 2FA:s”? Isnt the recovery code supposed to be used if 2FA cant be reached at the moment? Not just to destroy all 2FA:s on the account. If I destroy all the 2FA:s on my account, I would need to fetch one of my Yubikeys from bank vault, one from my safe, etc. (to be able to re-enable them) which is a terrible hassle.

ALSO:
Again, I could understand that there is a some small bug in the code, but the fact that neither Yubikeys NOR the email 2FA manages to work on the app is just horrible.

I think in about two years on the forum here, I can not remember any instance of the Bitwarden app breaking a phone. In all honesty: I think the possibility, that you have problems on your phone which also affected the Bitwarden app (and probably also your original issue here) is more likely than the other way round.

PS: Having issues and being frustrated is understandable. Your language and behaviour are not acceptable.

1 Like

Bitwarden is to one to blame that it signed me out of it. My iPhone did not sign me off from Bitwarden vault. It was Bitwarden that did that.

Bitwarden is the one to blame that email 2FA did not work. NOTHING that I or my phone could do cant possibly have anything to do with the fact that Bitwarden email 2FA does not work either.

Bitwarden is the one to blame that Yubikeys do not work as 2FA on Bitwarden, since they work fine with all the browsers I tryed them with.

Bitwarden is the one to blame that in my settings - apps menu freezed, because it was the presense of Bitwarden app that caused it to happen…and it required not only to remove the Bitwarden app, but also to reboot my iPhone (something I have never had to do because of a bug in the whole 4 years I have had it) to make it go away. If it was my phone, it would have also happened before this fiasco and also after I removed Bitwarden from my phone.

:face_with_bags_under_eyes: Oh, btw. I cant remove UV-flags on Yubikeys to test it without it, because UV-flags are tied on the servers end…I would need to reset the Yubikeys or remove all the Fido2/Passkeys and redo them in all the services Im using to make it happen, so no, Im not going to do it. And why would I, since currently the Bitwarden app, which is the problem here, freezes my iPhones settings - apps every time its installed in my phone anyway, so apparently I wont be using Bitwarden app in my phone anymore anway. :face_with_bags_under_eyes:

If Bitwarden app would start to work in my phone without freezing other apps settings, my only option is to add much more insecure TOTP to Bitwarden account as 2FA. Until this bug is fixed and Yubikeys can again be used as 2FA on Bitwarden app on my phone.

Aah, more censorship so that people wont findout what terrible app you have created and what problems it is causing to people…what was “against community guides” in that flagged post once again? Impossible to say, because apparently nothing. You just want to hide the facts and problems your app is causing.

@mmja We have a strict policy here to adhere to the Community Guidelines.

I unlisted the topic again, because most of your posts here go at least against these rules we have:

  • Be Respectful

    • Respect facilitates collaboration and collective progress. Communicate with consideration, professionalism, and patience. Disagreements are natural; strive to express views with courtesy, and respect other perspectives.
  • Avoid spreading misinformation

  • Open and Constructive Communication

    • Help make this a great place for discussion by always aiming to improve the dialogue. Be open to constructive feedback and offer it in a helpful and considerate manner. […]

If you’ve followed another language - and didn’t make accusations out of the blue - then no one would have flagged your posts and unlisted the topic. But we can’t accept going against the Community Guidelines that you also accepted by joining the forum.

Hi @mmja, just to close the loop on this post, I sent you a DM with details on how to connect with the official support team, and clarified that we don’t censor product issue posts (as is evidenced in the forum and other community spaces).

This post specifically was hidden due to language used in accordance with our community guidelines.

Rest assured the team is looking into the issue you are describing.