@Nail1684
PS. I’m guessing that’s why the other threads on this topic have gone cold because people just moved on to other password managers and authenticators that just work without issue.
@PennilessConsent Hmm, maybe…
But I could reproduce now with a code from a site (code still the same??) that was mentioned before: https://authenticationtest.com/totpChallenge/
We’ll see if it gets anywhere…
opened 01:46AM - 14 Dec 25 UTC
bug
app:authenticator
### Steps To Reproduce
1. Open `https://authenticationtest.com/totpChallenge/` … on a desktop browser.
2. In the authenticator app, go to `+`
3. ... then click on `Scan a QR code`
4. Try to scan the QR code on `https://authenticationtest.com/totpChallenge/`
### Expected Result
The QR code gets scanned as instantly as it worked on the same phone (!) with Aegis, 2FAS, Microsoft Authenticator and Google Authenticator.
### Actual Result
Out of about ten (mostly longer) attempts, only one time I could scan the QR code successfully. The other times, the QR code wasn't scanned at all. (I did not even get an error message -- it just didn't get "scanned successfully")
### Screenshots or Videos
The TOTP code in question:
<img width="216" height="215" alt="Image" src="https://github.com/user-attachments/assets/1502013c-8f3d-44a5-a65a-ba452c9fbb56" />
Video of one attempt, where I tried to scan the code from different distances etc.:
https://github.com/user-attachments/assets/1c68872a-4aa1-42e2-a775-9d985f36b083
### Additional Context
There is an open thread on the Community Forum where other users also reported the same thing happening: https://community.bitwarden.com/t/unable-to-scan-qr-codes-bw-authenticator-app/84749
Some reports, I think, may also indicate that it could also be dependent on certain devices/phones. (I don't know if the cameras might be different, or how the authenticator app can make use of it - or both... or something entirely different)
As written before, I tried to scan that specific test code also with four other authenticator apps (Aegis, 2FAS, Microsoft Authenticator and Google Authenticator) on the same phone (!) - and could scan that code in an instant with all other four authenticator apps.
### Build Version
2025.11.1 (1083)
### What server are you connecting to?
EU
### Self-host Server Version
_No response_
### Environment Details
- Fairphone 5
- Android 15 (Stock-ROM, latest available update)
### Issue Tracking Info
- [x] I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.
1 Like
Ah… Small update – I found an interesting (or hilarious?!) new workaround :
The TOTP QR code from https://authenticationtest.com/totpChallenge/ fails only with the authenticator app for me, but not with the mobile app.
But if I scan it with the mobile app first (successfully), and change then to the authenticator app, suddenly the authenticator app can scan it too.
@Nail1684 Thanks for creating the github issue and (glad?) you were able to reproduce the issue.
As for me, I have had 0% success rate using either Bitwarden app.
As I don’t have a github account, it would be appreciated if you could add to your git issue that other users are reporting 0% success rate.
1 Like
… 2025.12.0 just arrived on my phone. “Problem” now is: the QR code I couldn’t scan is now scannable for me every time. I’m not very confident that my newly opened GitHub issue survives that new development.
And I believe you, when you write you have 0% success rate. But that’s really “crazy” and I wonder all the more what is going on there…
