A post was merged into an existing topic: Unable to scan QR code (“integrated authenticator” / BW password manager)
This issue seems to be quite common with a wide variety of phones, and many users expressing their frustration on multiple channels (this forum, reddit, Github, etc..). For me, neither the BW Password Manager nor the BW Authenticator will recognise QR codes, while all of my other apps have no issue at all recognising 2FA QR codes. It is very definitely just a Bitwarden issue.
-
Make/Model: Motorola G84 5G (XT2347-2)
-
Android Version: 15
-
Bitwarden Password Manager: 2025.11.1 (Google Play & F-Droid)
-
Bitwarden Authenticator: 2025.10.2 (Google Play)
Cross-posting this as well for reference:
I was looking to purchase 22 licences, but if something that no other authenticator app has any issue with cannot be resolved by Bitwarden soon, I fear I will have to look at alternatives 
A possible workaround
Often times, the page that displays the QR code also shows the secret itself, which can be copy/pasted directly. I have done it this way for about 50 TOTP secrets in Password Manager. From what I have seen in this conversation, it appears the same workaround may work for authenticator.
In the few cases where one has not choice but to scan the QR code, perhaps use the native camera app and then copy/paste the URL into the TOTP secret field.
Not interested in workarounds for something that should just work. No other authenticator or QR scanner has issues recognising QR codes. This problem has been raised so many times with Bitwarden and outstanding for years now from what I have been reading. Bitwarden seemingly can’t or has no interest in fixing the issue. Quite pathetic, really.
Tbh, reading all the other issues and then that BW is toying with raising prices for a sub-par product, I’m giving Bitwarden a miss and taking my business elsewhere.
I just bought a year of BW because of this feature. Also I wanted to test it so i can buy some more licenses, actually much more. But I’m afraid I’ll have to drop this solution because of such a basic fault.
Ummm…. This conversation is about a free product, Bitwarden Authenticator that has only existed for a year and a half.
2 Likes
Sidenote: I added the targeted BW apps to the title of this thread and the equivalent thread for the password manager app – and added short staff notices. Hopefully this makes the threads more distinguishable.
1 Like
It is the same issue in both the main Bitwarden app AND the Authenticator app, hence why I cross-posted on the same issue in another thread in the Password Manager channel.
A post was merged into an existing topic: Unable to scan QR code (“integrated authenticator” / BW password manager)
I just looked (again) into both threads here and the GitHub issues. As far as I see, so far no one provided any “problematic” QR code (per screenshot), so that others could test a code.
Would be interesting to know if other devices could scan those codes – or couldn’t also. (and also the BW developers might have a more concrete lead to follow, if there were some QR codes that all or some devices couldn’t scan – and they could test it with)
So, I would suggest to post one or two of those problematic QR codes. – You can make every “QR code” invalid, if you privately deactivate TOTP and set it up again for the corresponding account, using a new QR code for yourself, which you don’t post here.
PS: Though a privacy caveat: IIRC, many QR codes not only contain the “TOTP seed code”, but could also contain e.g. an account email address, so make sure you’re either okay with that or don’t post that code. (hopefully that then is not a part of what makes those codes “unreadable”).
This is a very good idea. The QR includes more than just the secret. It could be one of these parameters getting in the way. That would only be uncovered with an actual failed example.
1 Like
For me, every QR code is problematic for the Bitwarden apps - I have never had Bitwarden recognise a single 2FA QR code ever (neither the main Bitwarden app or the Authenticator app).
I have tried scanning 2FA QR codes with the Bitwarden apps on different websites, different computer screens, tried at different angles, holding my phone close to screen, holding my phone further away, turning the phone 90 degrees, holding my phone upside-down, holding the phone steady for more than 30 seconds, zooming in on the QR code to make the QR as big as the entire computer screen, zooming out - nothing works. Meanwhile, if I change to any of my other authenticator apps or even native camera app, they all recognise the same QR code immediately.
Here’s an example:- every other authenticator app on my phone can recognise the QR codes generated by the 2FAS check ( Check your 2FAS app - scan the QR code or rewrite the Secret Words ). The Bitwarden apps? NOPE!
For me, Bitwarden Pasword Manager app 2025.11.0 on IOS 26.1 had no issues scanning the sample QR at https://2fas.com/auth/check-token/ . The QR was displayed on my Windows 11 PC, using the iPhone camera to capture
For me, Bitwarden Authenticator 2025.12.0 (375) on IOS 26.1 had no issues scanning the sample QR at https://2fas.com/auth/check-token/ or at https://authenticationtest.com/totpChallenge/. The QR was displayed on my Windows 11 PC, using the iPhone camera to capture.
For me, Bitwarden Password Manager extension 2025.11.1 on Chrome 142.0.74444.176 Windows 11 had no issues scanning the sample QR at https://2fas.com/auth/check-token/ , although this “scans” the webpage behind the extension without the use of a camera.
Given that all problems reports indicating an operating system are android based (pixel, galaxy, etc.) and that I have a positive experience on iOS, I added the “auth:android” tag to this conversation.
If you have a counter-example, please do post so that one of us mods can again update.
Ah, thanks! Seems like a “static” QR code/image.
I could scan this code instantly with my BW authenticator app. (2025.11.1, Android 15, Fairphone 5)
What is your app version, Android version, and phone brand/model?
Already provided here:
1 Like
UPDATE: I have just installed the latest update to Bitwarden Authenticator - 2025.12.0 (1114) from Google Play. No difference, still does not work.
@PennilessConsent Sorry. I’m blind, obviously.
Hmm, it would be good to have someone else replicating this with that 2FAS code… but on the other hand, that might be enough to raise it again on GitHub. – If you consider it, you should document it well enough. And you’d have to avoid getting it closed as a “duplicate” directly. 
@Nail1684 thanks for taking interest in the issue.
Unfortunately, I don’t have time to mess around any more and I’ve actually already moved on to another password manager that just works out of the box and has a far better UI/UX as well. I’ll continue to monitor and answer any questions on this thread for a little while longer to help document if it is any help for the devs or anyone else following, but I don’t have the time or interest in opening up a git issue as well.
1 Like
I guess then we have to wait until someone else comes along. 
(I would report it, but it would be anything else than ideal, as I can’t reproduce it myself)