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 #6826] [BWA-252] Authenticator list display error #39482

New Issue
Open
opened 2026-04-23 18:24:47 -05:00 by GiteaMirror · 9 comments
GiteaMirror commented 2026-04-23 18:24:47 -05:00
Owner
Copy Link

Originally created by @humbleoxygen12 on GitHub (Apr 23, 2026).
Original GitHub issue: https://github.com/bitwarden/android/issues/6826

Steps To Reproduce

  1. Turn on "Allow authenticator syncing" in password manager
  2. Go to the authenticator list

Expected Result

Items with an authenticator key should appear in the list with the username.

Actual Result

  1. Some items show authenticator key instead of username
  2. Some items have an empty authenticator key but still appear in the list

Screenshots or Videos

No response

Additional Context

No response

Build Version

© Bitwarden Inc. 2015-2026 Version: 2026.4.0 (1497)

What server are you connecting to?

US

Self-host Server Version

No response

Environment Details

No response

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 @humbleoxygen12 on GitHub (Apr 23, 2026). Original GitHub issue: https://github.com/bitwarden/android/issues/6826 ### Steps To Reproduce 1. Turn on "Allow authenticator syncing" in password manager 2. Go to the authenticator list ### Expected Result Items with an authenticator key should appear in the list with the username. ### Actual Result 1. Some items show authenticator key instead of username 2. Some items have an empty authenticator key but still appear in the list ### Screenshots or Videos _No response_ ### Additional Context _No response_ ### Build Version © Bitwarden Inc. 2015-2026 Version: 2026.4.0 (1497) ### What server are you connecting to? US ### Self-host Server Version _No response_ ### Environment Details _No response_ ### 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.
GiteaMirror added the app:authenticatorbug labels 2026-04-23 18:24:47 -05:00
GiteaMirror commented 2026-04-23 18:24:49 -05:00
Author
Owner
Copy Link

@bitwarden-bot commented on GitHub (Apr 23, 2026):

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

<!-- gh-comment-id:4302451736 --> @bitwarden-bot commented on GitHub (Apr 23, 2026): Thank you for your report! We've added this to our internal board for review. ID: [BWA-252](https://bitwarden.atlassian.net/browse/BWA-252) [BWA-252]: https://bitwarden.atlassian.net/browse/BWA-252?atlOrigin=eyJpIjoiNWRkNTljNzYxNjVmNDY3MDlhMDU5Y2ZhYzA5YTRkZjUiLCJwIjoiZ2l0aHViLWNvbS1KU1cifQ
GiteaMirror commented 2026-04-23 18:24:49 -05:00
Author
Owner
Copy Link

@Krychaz commented on GitHub (Apr 23, 2026):

Hello there,

Can you please share a screenshot of the error you are receiving?

<!-- gh-comment-id:4304761800 --> @Krychaz commented on GitHub (Apr 23, 2026): Hello there, Can you please share a screenshot of the error you are receiving?
GiteaMirror commented 2026-04-23 18:24:51 -05:00
Author
Owner
Copy Link

@pamperer562580892423 commented on GitHub (Apr 23, 2026):

Another user here.

Besides the screenshot @Krychaz asked for - since it's about synced codes, could you add the version info of your BW Android password manager app? - This was only your authenticator app version:

Build Version
© Bitwarden Inc. 2015-2026 Version: 2026.4.0 (1497)

<!-- gh-comment-id:4304905742 --> @pamperer562580892423 commented on GitHub (Apr 23, 2026): Another user here. Besides the screenshot @Krychaz asked for - since it's about synced codes, could you add the version info of your BW Android password manager app? - This was only your authenticator app version: > Build Version > © Bitwarden Inc. 2015-2026 Version: 2026.4.0 (1497)
GiteaMirror commented 2026-04-23 18:24:53 -05:00
Author
Owner
Copy Link

@humbleoxygen12 commented on GitHub (Apr 23, 2026):

Hi, my current password manager version is:
2026.4.0 (21434)

Image

Here is the screenshot. GitHub correctly shows the username, but the other one shows the authenticator key

<!-- gh-comment-id:4305322107 --> @humbleoxygen12 commented on GitHub (Apr 23, 2026): Hi, my current password manager version is: 2026.4.0 (21434) <img width="5760" height="2380" alt="Image" src="https://github.com/user-attachments/assets/a1db1a80-3fa8-41ea-96c9-9f4cfb0f2a2d" /> Here is the screenshot. GitHub correctly shows the username, but the other one shows the authenticator key
GiteaMirror commented 2026-04-23 18:24:54 -05:00
Author
Owner
Copy Link

@pamperer562580892423 commented on GitHub (Apr 23, 2026):

but the other one shows the authenticator key

And that is a valid login item with an existing item name, username and TOTP authenticator key? - I'm also asking because there is another issue with "hallucinated (invalid) TOTP codes" and I wonder if you might be experiencing this other issue (also?)?

<!-- gh-comment-id:4305431061 --> @pamperer562580892423 commented on GitHub (Apr 23, 2026): > but the other one shows the authenticator key And that is a valid login item with an existing item name, username and TOTP authenticator key? - I'm also asking because there is [another issue with "hallucinated (invalid) TOTP codes"](https://github.com/bitwarden/android/issues/6526) and I wonder if you might be experiencing this other issue (also?)?
GiteaMirror commented 2026-04-23 18:24:55 -05:00
Author
Owner
Copy Link

@humbleoxygen12 commented on GitHub (Apr 23, 2026):

GitHub is clearly my username, but the masked one shows the authenticator key instead of username or email.

Regarding your example, I have this issue too: the authenticator field is empty, but the Clear button is still shown. I guess there's probably an empty string.

<!-- gh-comment-id:4305503221 --> @humbleoxygen12 commented on GitHub (Apr 23, 2026): GitHub is clearly my username, but the masked one shows the authenticator key instead of username or email. Regarding your example, I have this issue too: the authenticator field is empty, but the Clear button is still shown. I guess there's probably an empty string.
GiteaMirror commented 2026-04-23 18:24:56 -05:00
Author
Owner
Copy Link

@pamperer562580892423 commented on GitHub (Apr 23, 2026):

but the masked one shows the authenticator key instead of username or email.

Yeah, but then... is there a corresponding login item to it? Does it have a username (that is not the authenticator key)? Or is there not even a corresponding login item for that entry in your authenticator app? If it's the latter, then your issue in fact seems to be the "hallucinating TOTP codes" issue.

Regarding your example, I have this issue too: the authenticator field is empty, but the Clear button is still shown. I guess there's probably an empty string.

Hm, are you talking now about (e.g.) that masked entry from your screenshot? Or are you referring to other TOTP entries? And what exactly do you mean by "Clear button"?

<!-- gh-comment-id:4305656453 --> @pamperer562580892423 commented on GitHub (Apr 23, 2026): > but the masked one shows the authenticator key instead of username or email. Yeah, but then... is there a corresponding login item to it? Does it have a username (that is **not** the authenticator key)? Or is there not even a corresponding login item for that entry in your authenticator app? If it's the latter, then your issue in fact seems to be the "hallucinating TOTP codes" issue. > Regarding your example, I have this issue too: the authenticator field is empty, but the Clear button is still shown. I guess there's probably an empty string. Hm, are you talking now about (e.g.) that masked entry from your screenshot? Or are you referring to other TOTP entries? And what exactly do you mean by "Clear button"?
GiteaMirror commented 2026-04-23 18:24:56 -05:00
Author
Owner
Copy Link

@pamperer562580892423 commented on GitHub (Apr 23, 2026):

PS: If your "list display error" is completely based on "hallucinated TOTP codes", then your issue could probably be closed as a duplicate of this other issue. So please clarify if the display error is based on valid login items with valid username (that are not shown correctly) and valid TOTP codes - or on "hallucinated TOTP codes".

<!-- gh-comment-id:4305730903 --> @pamperer562580892423 commented on GitHub (Apr 23, 2026): PS: If your "list display error" is completely based on "hallucinated TOTP codes", then your issue could probably be closed as a duplicate of this other issue. So please clarify if the display error is based on valid login items with valid username (that are not shown correctly) and valid TOTP codes - or on "hallucinated TOTP codes".
GiteaMirror commented 2026-04-23 18:24:57 -05:00
Author
Owner
Copy Link

@humbleoxygen12 commented on GitHub (Apr 23, 2026):

Yeah, but then... is there a corresponding login item to it? Does it have a username (that is not the authenticator key)? Or is there not even a corresponding login item for that entry in your authenticator app?

Yep, the item does have a username. So the masked field is the new issue.

Hm, are you talking now about (e.g.) that masked entry from your screenshot? Or are you referring to other TOTP entries? And what exactly do you mean by "Clear button"?

I am talking about the issue you referenced. Some of my items do have an empty authenticator key, but TOTP is still shown. In the screenshots from the issue you referenced, the authenticator key field also has an X button, which is the Clear button. Since it is possible to clear an already empty input field, I guess an empty string is stored in that field, which leads to hallucinated TOTP codes.

<!-- gh-comment-id:4305787360 --> @humbleoxygen12 commented on GitHub (Apr 23, 2026): > Yeah, but then... is there a corresponding login item to it? Does it have a username (that is not the authenticator key)? Or is there not even a corresponding login item for that entry in your authenticator app? Yep, the item does have a username. So the masked field is the new issue. > Hm, are you talking now about (e.g.) that masked entry from your screenshot? Or are you referring to other TOTP entries? And what exactly do you mean by "Clear button"? I am talking about the issue you referenced. Some of my items do have an empty authenticator key, but TOTP is still shown. In the screenshots from the issue you referenced, the authenticator key field also has an X button, which is the Clear button. Since it is possible to clear an already empty input field, I guess an empty string is stored in that field, which leads to hallucinated TOTP codes.
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#39482
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?