github-starred/android
2
0
Fork 0
mirror of https://github.com/bitwarden/android.git synced 2026-05-06 07:48:22 -05:00
Code Issues 1.1k Packages Projects Releases 122 Wiki Activity

[GH-ISSUE #6264] [BWA-213] QR code can't be scanned, while other authenticator apps can scan it instantly #50497

New Issue
Open
opened 2026-05-01 13:15:34 -05:00 by GiteaMirror · 9 comments
GiteaMirror commented 2026-05-01 13:15:34 -05:00
Owner
Copy Link

Originally created by @pamperer562580892423 on GitHub (Dec 14, 2025).
Original GitHub issue: https://github.com/bitwarden/android/issues/6264

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 (TOTP) 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")

So, important for reproducing: try it a few times, as it might work sometimes (maybe even with the first try).

Screenshots or Videos

The TOTP code in question:

Image

 

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.

 

Update 1:

I now tried to scan that same TOTP code with the BW mobile app (by adding a new login item and directly scanning for adding an "authenticator key" - it's a premium BW account). And here, every scan is successful, as instantly as the other four authenticator apps. So there seems to be at least difference between the BW authenticator app and the BW Android mobile app.

The "Environment Details" of my mobile app:
© Bitwarden Inc. 2015-2025
Version: 2025.12.0 (21003)
📱 Fairphone FP5 🤖 15@35 📦 prod
🧱 commit: bitwarden/android/release/2025.12-rc40@f02b374e989600a8458d2884abd2526244241c8a
💻 build source: bitwarden/android/actions/runs/19830126705/attempts/1
🦀 SDK: 1.0.0-3928-2cca3d46
🌩 Server: 2025.12.0 @ EU

 

Update 2:

I found something interesting now after my "Update 1". Because I decided to scan the same QR code with the authenticator app again, after scanning it with the BW mobile app first (i.e. just scanning it there like described in my Update 1, but changing directly after the successful scan to the authenticator app and trying to scan the code there as well). And guess what: when I do that, suddenly the authenticator app can scan that QR code successfully every time I tried it (I stopped after about five attempts - so, now all those five attempts were successful, where before, almost all attempts failed)

 

PS: Of course, the TOTP code here is only one example where the scan fails. I wonder what makes some codes fail and others not (or which devices have problems with some TOTP codes while other devices don't have issues at all with the same codes).

 

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

  • 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.
Originally created by @pamperer562580892423 on GitHub (Dec 14, 2025). Original GitHub issue: https://github.com/bitwarden/android/issues/6264 ### 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 (TOTP) 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") **So, important for reproducing: try it a few times, as it might work sometimes (maybe even with the first try).** ### 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" /> &nbsp; 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. &nbsp; **Update 1:** I now tried to scan that same TOTP code with the BW mobile app (by adding a new login item and directly scanning for adding an "authenticator key" - it's a premium BW account). And here, every scan is successful, as instantly as the other four authenticator apps. So there seems to be at least difference between the BW authenticator app and the BW Android mobile app. The "Environment Details" of my mobile app: © Bitwarden Inc. 2015-2025 Version: 2025.12.0 (21003) 📱 Fairphone FP5 🤖 15@35 📦 prod 🧱 commit: bitwarden/android/release/2025.12-rc40@f02b374e989600a8458d2884abd2526244241c8a 💻 build source: bitwarden/android/actions/runs/19830126705/attempts/1 🦀 SDK: 1.0.0-3928-2cca3d46 🌩 Server: 2025.12.0 @ EU &nbsp; **Update 2:** I found something interesting now after my "Update 1". Because I decided to scan the same QR code with the authenticator app again, after scanning it with the BW mobile app first (i.e. just scanning it there like described in my Update 1, but changing directly after the successful scan to the authenticator app and trying to scan the code there as well). And guess what: when I do that, suddenly the authenticator app can scan that QR code successfully every time I tried it (I stopped after about five attempts - so, now all those five attempts were successful, where before, almost all attempts failed) &nbsp; PS: Of course, the TOTP code here is only one example where the scan fails. I wonder what makes some codes fail and others not (or which devices have problems with some TOTP codes while other devices don't have issues at all with the same codes). &nbsp; ### 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.
GiteaMirror added the bugapp:authenticator labels 2026-05-01 13:15:34 -05:00
GiteaMirror commented 2026-05-01 13:15:37 -05:00
Author
Owner
Copy Link

@bitwarden-bot commented on GitHub (Dec 14, 2025):

Thank you for your report! We've added this to our internal board for review.
ID: BWA-213

<!-- gh-comment-id:3650039491 --> @bitwarden-bot commented on GitHub (Dec 14, 2025): Thank you for your report! We've added this to our internal board for review. ID: [BWA-213](https://bitwarden.atlassian.net/browse/BWA-213) [BWA-213]: https://bitwarden.atlassian.net/browse/BWA-213?atlOrigin=eyJpIjoiNWRkNTljNzYxNjVmNDY3MDlhMDU5Y2ZhYzA5YTRkZjUiLCJwIjoiZ2l0aHViLWNvbS1KU1cifQ
GiteaMirror commented 2026-05-01 13:15:39 -05:00
Author
Owner
Copy Link

@pamperer562580892423 commented on GitHub (Dec 14, 2025):

Haha, already an update: I just got authenticator app 2025.12.0 (1114) on my phone... And now with that new version, my "QR code in question" gets scanned instantly.

I'm aware, that this issue now probably will get closed - as the whole case I brought is gone now - but I would like to point out that in the Community Forum thread there is at least one user who reports that even with authenticator app 2025.12.0 they would have a success rate of scanning QR codes of 0% (!) - besides the other reports in the past.

So I can only suggest that this issue should still be further investigated.

Addition: I also now had the chance to test this QR code in question with two other phones (Motorola, Android 16) and authenticator app version 2025.11.1 again, and at least I could reproduce that those two phones also are not able to scan that QR code successfully. - I hope I have a chance to scan that QR code again, when those two phones get authenticator app 2025.12.0.

<!-- gh-comment-id:3651066823 --> @pamperer562580892423 commented on GitHub (Dec 14, 2025): Haha, already an update: I just got authenticator app 2025.12.0 (1114) on my phone... And now with that new version, my "QR code in question" gets scanned instantly. I'm aware, that this issue now probably will get closed - as the whole case I brought is gone now - but I would like to point out that in the Community Forum thread there is at least one user who reports that even with authenticator app 2025.12.0 they would have a success rate of scanning QR codes of 0% (!) - besides the other reports in the past. So I can only suggest that this issue should still be further investigated. **Addition:** I also now had the chance to test this QR code in question with two other phones (Motorola, Android 16) and authenticator app version 2025.11.1 again, and at least **I could reproduce** that those two phones also are **not** able to scan that QR code successfully. - I hope I have a chance to scan that QR code again, when those two phones get authenticator app 2025.12.0.
GiteaMirror commented 2026-05-01 13:15:39 -05:00
Author
Owner
Copy Link

@SergeantConfused commented on GitHub (Dec 14, 2025):

Hello @pamperer562580892423,

Thank you for that detailed report. I tested this on Android 14 with Bitwarden Authenticator 2025.11.1 and I was able to reproduce this somewhat. Upon first launching the Authenticator, it is able to scan the QR code in this GitHub report, but any subsequent attempts to scan it fail regardless if I deleted the saved TOTP seed or not; however, if I open the Task Switcher and dismiss the Authenticator and launch it anew, it is then able to scan the QR again even if it already is saved in (it saved another identical TOTP seed). I have flagged this to the Engineering team.

Please feel free to post additional information, such as screenshots or a screen video recordings, if you wish.

Thank you again,

<!-- gh-comment-id:3651689898 --> @SergeantConfused commented on GitHub (Dec 14, 2025): Hello @pamperer562580892423, Thank you for that detailed report. I tested this on Android 14 with Bitwarden Authenticator 2025.11.1 and I was able to reproduce this somewhat. Upon first launching the Authenticator, it is able to scan the QR code in this GitHub report, but any subsequent attempts to scan it fail regardless if I deleted the saved TOTP seed or not; however, if I open the Task Switcher and dismiss the Authenticator and launch it anew, it is then able to scan the QR again even if it already is saved in (it saved another identical TOTP seed). I have flagged this to the Engineering team. Please feel free to post additional information, such as screenshots or a screen video recordings, if you wish. Thank you again,
GiteaMirror commented 2026-05-01 13:15:39 -05:00
Author
Owner
Copy Link

@pamperer562580892423 commented on GitHub (Dec 14, 2025):

@SergeantConfused Thanks for your thoughtful and thorough testing.

I can already add, that for those two Motorola devices I also tested this with (authenticator app version 2025.11.1), I definitely was not able to scan the QR code at all - so, not even with the first attempt, after first launch of the app. (and as the password manager app is not used on those phones, I also didn't try my workaround from "Update 2" of the original post)

For my own phone (FP5) on authenticator app 2025.11.1 (!), I'm not sure if it was the first or a following attempt, where it worked... (only with my "workaround" / "Update 2", I could consistently scan the code every time then)

In sum, this looks very inconsistent across devices, and whatever other conditions. I think this should be kept in mind for further testing and reproducing.

<!-- gh-comment-id:3651750263 --> @pamperer562580892423 commented on GitHub (Dec 14, 2025): @SergeantConfused Thanks for your thoughtful and thorough testing. I can already add, that for those two Motorola devices I also tested this with (authenticator app version 2025.11.1), I definitely was **not** able to scan the QR code at all - so, not even with the first attempt, after first launch of the app. (and as the password manager app is not used on those phones, I also didn't try my workaround from "Update 2" of the original post) For my own phone (FP5) on authenticator app 2025.11.1 (!), I'm not sure if it was the first or a following attempt, where it worked... (only with my "workaround" / "Update 2", I could consistently scan the code every time then) In sum, this looks very inconsistent across devices, and whatever other conditions. I think this should be kept in mind for further testing and reproducing.
GiteaMirror commented 2026-05-01 13:15:39 -05:00
Author
Owner
Copy Link

@pamperer562580892423 commented on GitHub (Dec 16, 2025):

@SergeantConfused Short update.

One of the two Motorola phones got authenticator app 2025.12.0 yesterday. And out of about 8 attempts, I could scan the QR code from the original post zero (!) times now. (Moto G9 play, Android 16 / latest Lineage OS)

The user from the linked community forum thread who said they would have a success (!) rate of 0% (!) also has a Motorola device - those were their details:

Make/Model: Motorola G84 5G (XT2347-2)
Android Version: 15

That's only two instances and could be totally random - but I would also investigate a possible "Motorola incompatibility".

(though, I'm also still wondering what makes some QR codes scannable / unscannable - and if some QR codes have some problematic characteristics... at least for some cameras / devices / "drivers" / "software" or whatever...)

<!-- gh-comment-id:3661657672 --> @pamperer562580892423 commented on GitHub (Dec 16, 2025): @SergeantConfused Short update. One of the two Motorola phones got authenticator app 2025.12.0 yesterday. And out of about 8 attempts, I could scan the QR code from the original post zero (!) times now. (Moto G9 play, Android 16 / latest Lineage OS) The user from the linked community forum thread who said they would have a success (!) rate of 0% (!) also has a Motorola device - those were their details: > Make/Model: Motorola G84 5G (XT2347-2) > Android Version: 15 That's only two instances and could be totally random - but I would also investigate a possible "Motorola incompatibility". (though, I'm also still wondering what makes some QR codes scannable / unscannable - and if _some_ QR codes have _some_ problematic characteristics... at least for _some_ cameras / devices / "drivers" / "software" or whatever...)
GiteaMirror commented 2026-05-01 13:15:40 -05:00
Author
Owner
Copy Link

@pamperer562580892423 commented on GitHub (Dec 17, 2025):

@SergeantConfused Another short update: I now could also with the second Motorola phone (also Moto G9 play, Android 16 / latest LineageOS) and authenticator app 2025.12.0 (!) test our QR code here: as expected, it doesn't scan the code. (I only made about five attempts now)

So, summary for "my" two Motorola devices: both mentioned Moto G9 play phones can't scan "our" TOTP QR code at all - both with authenticator app versions 2025.11.1 and 2025.12.0, not one single attempt was successful. (but I also didn't try my "workaround" / "Update 2" from the original post with the Motorola phones!)

<!-- gh-comment-id:3662987977 --> @pamperer562580892423 commented on GitHub (Dec 17, 2025): @SergeantConfused Another short update: I now could also with the second Motorola phone (also Moto G9 play, Android 16 / latest LineageOS) and authenticator app 2025.12.0 (!) test our QR code here: as expected, it doesn't scan the code. (I only made about five attempts now) **So, summary for "my" two Motorola devices:** both mentioned Moto G9 play phones can't scan "our" TOTP QR code at all - both with authenticator app versions 2025.11.1 and 2025.12.0, not one single attempt was successful. (but I also didn't try my "workaround" / "Update 2" from the original post with the Motorola phones!)
GiteaMirror commented 2026-05-01 13:15:40 -05:00
Author
Owner
Copy Link

@pamperer562580892423 commented on GitHub (Jan 24, 2026):

@SergeantConfused Update for authenticator app version 2025.12.1 (1138).

With all three devices that I mentioned and tested before (my FP5/Android 15, and the two Motorola G9 play/LineageOS with Android 16), I now tried again to scan the code from my original post here. 10 times with each device. Results:

  • one Moto G9 play: 0/10 successful scans
  • the other Moto G9 play: 0/10 successful scans
  • my own FP5: 10/10 successful scans

I think we agree that it can't be a "random event", that both Motorola devices fail to scan that code so many times and with different versions of the authenticator app...

<!-- gh-comment-id:3795404719 --> @pamperer562580892423 commented on GitHub (Jan 24, 2026): @SergeantConfused Update for authenticator app version 2025.12.1 (1138). With all three devices that I mentioned and tested before (my FP5/Android 15, and the two Motorola G9 play/LineageOS with Android 16), I now tried again to scan the code from my original post here. 10 times with each device. Results: - one Moto G9 play: 0/10 successful scans - the other Moto G9 play: 0/10 successful scans - my own FP5: 10/10 successful scans I think we agree that it can't be a "random event", that both Motorola devices fail to scan that code so many times and with different versions of the authenticator app...
GiteaMirror commented 2026-05-01 13:15:40 -05:00
Author
Owner
Copy Link

@Bottommmm commented on GitHub (Mar 9, 2026):

I’m experiencing the same issue.
My device is a Vivo X200s running Android 16.
Bitwarden version: 2026.2.1 (21297)
Authenticator version: 2026.2.1 (1363)
☹️☹️

<!-- gh-comment-id:4024711444 --> @Bottommmm commented on GitHub (Mar 9, 2026): I’m experiencing the same issue. My device is a Vivo X200s running Android 16. Bitwarden version: 2026.2.1 (21297) Authenticator version: 2026.2.1 (1363) ☹️☹️
GiteaMirror commented 2026-05-01 13:15:41 -05:00
Author
Owner
Copy Link

@pamperer562580892423 commented on GitHub (Mar 9, 2026):

@Bottommmm Can you scan the QR code that is included in my original post here? If you can't - could you try it a few times? (as you can see above, with the two Moto G9 play devices within my reach, it really failed not just a few times, but more like every time)

PS: Latest test with the QR code from my OP above and with BW authenticator app 2026.2.1 (1363):

  • one of the two Moto G9 play phones (now on Android 16 with LineageOS 23.2): 0/10 successful scans
  • the other Moto G9 play phone (also now on Android 16 with LineageOS 23.2): 0/10 successful scans
  • my own FP5 (still Android 15): 10/10 successful scans
<!-- gh-comment-id:4027387621 --> @pamperer562580892423 commented on GitHub (Mar 9, 2026): @Bottommmm Can you scan the QR code that is included in my original post here? If you can't - could you try it a few times? (as you can see above, with the two Moto G9 play devices within my reach, it really failed not just a few times, but more like every time) PS: Latest test with the QR code from my OP above and with BW authenticator app 2026.2.1 (1363): - one of the two Moto G9 play phones (now on Android 16 with LineageOS 23.2): **0/10** successful scans - the other Moto G9 play phone (also now on Android 16 with LineageOS 23.2): **0/10** successful scans - my own FP5 (still Android 15): **10/10** successful scans
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
app:authenticator
app:password-manager
bug
bug-passkey
customer-support
duplicate
enhancement
good first issue
help wanted
needs-reply
needs-response
pull-request
Mirrored from GitHub Pull Request
 question
No Label app:authenticator bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/android#50497
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?