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

[GH-ISSUE #6450] [BWA-224] Local codes sorted alphabetically; cloud codes are not #39415

New Issue
Open
opened 2026-04-23 18:17:09 -05:00 by GiteaMirror · 6 comments
GiteaMirror commented 2026-04-23 18:17:09 -05:00
Owner
Copy Link

Originally created by @tayl on GitHub (Jan 30, 2026).
Original GitHub issue: https://github.com/bitwarden/android/issues/6450

Steps To Reproduce

  1. Open the application
  2. Have both local and cloud entries
  3. Note local entries are sorted alphabetically
  4. Note cloud entries are not sorted

Expected Result

All entries are sorted

Actual Result

Only some entries are sorted

Screenshots or Videos

No response

Additional Context

I imported all of my local codes into the cloud and feel I made a big mistake because it's incredibly inefficient finding them now. This may not be a big deal with 10 or so codes, but with much more (I have 50+ at this point), the UI is forcing the user into a needle in haystack search.

Additional observation: there is no way to modify the nickname/desc of the cloud entries like you can with the local entries, even though this field is not something (apparently) synced to the cloud, since I see no way to modify it in either mobile or web.

Build Version

2026.1.0 (1167)

What server are you connecting to?

US

Self-host Server Version

No response

Environment Details

Pixel 7 Pro latest public android OS

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 @tayl on GitHub (Jan 30, 2026). Original GitHub issue: https://github.com/bitwarden/android/issues/6450 ### Steps To Reproduce 1. Open the application 2. Have both local and cloud entries 3. Note local entries are sorted alphabetically 4. Note cloud entries are not sorted ### Expected Result All entries are sorted ### Actual Result Only some entries are sorted ### Screenshots or Videos _No response_ ### Additional Context I imported all of my local codes into the cloud and feel I made a big mistake because it's incredibly inefficient finding them now. This may not be a big deal with 10 or so codes, but with much more (I have 50+ at this point), the UI is forcing the user into a needle in haystack search. Additional observation: there is no way to modify the nickname/desc of the cloud entries like you can with the local entries, even though this field is not something (apparently) synced to the cloud, since I see no way to modify it in either mobile or web. ### Build Version 2026.1.0 (1167) ### What server are you connecting to? US ### Self-host Server Version _No response_ ### Environment Details Pixel 7 Pro latest public android OS ### 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 app:authenticatorbug labels 2026-04-23 18:17:09 -05:00
GiteaMirror commented 2026-04-23 18:17:10 -05:00
Author
Owner
Copy Link

@bitwarden-bot commented on GitHub (Jan 30, 2026):

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

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

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

Another user here - and only to that part:

Additional observation: there is no way to modify the nickname/desc of the cloud entries like you can with the local entries, even though this field is not something (apparently) synced to the cloud, since I see no way to modify it in either mobile or web.

The codes are shown with the item name and username. When you change the item name and username of the corresponding login items in your BW vault, and don't forget to sync the vault in your Android password manager app (manually or automatically), then the authenticator app also shows the updated item names and usernames. So, those fields can absolutely be changed for synced codes.

(PS: Additional explanation: the sync between mobile password manager app and authenticator app is kind of a one-way sync: login items that have stored "authenticator keys" (TOTP seed codes) get synced to the authenticator app --> so, editing those login items in your vault will eventually show as "changes" in the authenticator app for those synced TOTP codes)

<!-- gh-comment-id:3828557939 --> @pamperer562580892423 commented on GitHub (Jan 31, 2026): Another user here - and only to that part: > Additional observation: there is no way to modify the nickname/desc of the cloud entries like you can with the local entries, even though this field is not something (apparently) synced to the cloud, since I see no way to modify it in either mobile or web. The codes are shown with the item name and username. When you change the item name and username of the corresponding login items in your BW vault, and don't forget to sync the vault in your Android password manager app (manually or automatically), then the authenticator app also shows the updated item names and usernames. So, those fields can absolutely be changed for synced codes. (PS: Additional explanation: the sync between mobile password manager app and authenticator app is kind of a one-way sync: login items that have stored "authenticator keys" (TOTP seed codes) get synced to the authenticator app --> so, editing those login items in your vault will eventually show as "changes" in the authenticator app for those synced TOTP codes)
GiteaMirror commented 2026-04-23 18:17:11 -05:00
Author
Owner
Copy Link

@tayl commented on GitHub (Jan 31, 2026):

Another user here - and only to that part:

Additional observation: there is no way to modify the nickname/desc of the cloud entries like you can with the local entries, even though this field is not something (apparently) synced to the cloud, since I see no way to modify it in either mobile or web.

The codes are shown with the item name and username. When you change the item name and username of the corresponding login items in your BW vault, and don't forget to sync the vault in your Android password manager app (manually or automatically), then the authenticator app also shows the updated item names and usernames. So, those fields can absolutely be changed for synced codes.

(PS: Additional explanation: the sync between mobile password manager app and authenticator app is kind of a one-way sync: login items that have stored "authenticator keys" (TOTP seed codes) get synced to the authenticator app --> so, editing those login items in your vault will eventually show as "changes" in the authenticator app for those synced TOTP codes)

Maybe so, but the entries in Authenticator contain names that do not exist in the associated entry in Bitwarden, even after syncing. So there's a discrepancy, possibly related to the fact that I converted the Authenticator entries from local to cloud and associated them one by one with the cloud entries?

Anyway that's a secondary issue that I suspect may be related to the underlying issue of sorting not happening or happening on an invisible (to the UI) field.

Edit: upon closer inspection, this second issue stems from parameters stored in the otpauth URI

otpauth://totp/Github.com%3Acantchangethis?secret=XXXXX&algorithm=SHA1&digits=6&period=30&issuer=Github.com%3Acantchange

<!-- gh-comment-id:3828707516 --> @tayl commented on GitHub (Jan 31, 2026): > Another user here - and only to that part: > > > Additional observation: there is no way to modify the nickname/desc of the cloud entries like you can with the local entries, even though this field is not something (apparently) synced to the cloud, since I see no way to modify it in either mobile or web. > > The codes are shown with the item name and username. When you change the item name and username of the corresponding login items in your BW vault, and don't forget to sync the vault in your Android password manager app (manually or automatically), then the authenticator app also shows the updated item names and usernames. So, those fields can absolutely be changed for synced codes. > > (PS: Additional explanation: the sync between mobile password manager app and authenticator app is kind of a one-way sync: login items that have stored "authenticator keys" (TOTP seed codes) get synced to the authenticator app --> so, editing those login items in your vault will eventually show as "changes" in the authenticator app for those synced TOTP codes) Maybe so, but the entries in Authenticator contain names that do not exist in the associated entry in Bitwarden, even after syncing. So there's a discrepancy, possibly related to the fact that I converted the Authenticator entries from local to cloud and associated them one by one with the cloud entries? Anyway that's a secondary issue that I suspect may be related to the underlying issue of sorting not happening or happening on an invisible (to the UI) field. Edit: upon closer inspection, this second issue stems from parameters stored in the otpauth URI `otpauth://totp/Github.com%3Acantchangethis?secret=XXXXX&algorithm=SHA1&digits=6&period=30&issuer=Github.com%3Acantchange`
GiteaMirror commented 2026-04-23 18:17:12 -05:00
Author
Owner
Copy Link

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

Maybe so, but the entries in Authenticator contain names that do not exist in the associated entry in Bitwarden...
...
Edit: upon closer inspection, this second issue stems from parameters stored in the otpauth URI

👍 (otherwise I would have guessed, that it would be due to "clone(d) items" that you were now aware of yet, as when you "move" local codes from the authenticator app to your vault - and make them part of the "sync" - those codes don't merge with existing login items, but are added as new login items)

<!-- gh-comment-id:3828735759 --> @pamperer562580892423 commented on GitHub (Jan 31, 2026): > Maybe so, but the entries in Authenticator contain names that do not exist in the associated entry in Bitwarden... > ... > Edit: upon closer inspection, this second issue stems from parameters stored in the otpauth URI 👍 (otherwise I would have guessed, that it would be due to "clone(d) items" that you were now aware of yet, as when you "move" local codes from the authenticator app to your vault - and make them part of the "sync" - those codes don't merge with existing login items, but are added as new login items)
GiteaMirror commented 2026-04-23 18:17:14 -05:00
Author
Owner
Copy Link

@rmcdowell-bitwarden commented on GitHub (Feb 2, 2026):

Hi there,

Thank you for your report!

I was able to reproduce this issue, and I have flagged this to our engineering team.

If you wish to add any further information/screenshots/recordings etc., please feel free to do so at any time - our engineering team will be happy to review these.

Thanks once again!

<!-- gh-comment-id:3832679887 --> @rmcdowell-bitwarden commented on GitHub (Feb 2, 2026): Hi there, Thank you for your report! I was able to reproduce this issue, and I have flagged this to our engineering team. If you wish to add any further information/screenshots/recordings etc., please feel free to do so at any time - our engineering team will be happy to review these. Thanks once again!
GiteaMirror commented 2026-04-23 18:17:15 -05:00
Author
Owner
Copy Link

@david-livefront commented on GitHub (Mar 30, 2026):

Changes have been made here to ensure the shared codes appear in alphabetical order.

The update should make it out to production in a few weeks.

<!-- gh-comment-id:4158204586 --> @david-livefront commented on GitHub (Mar 30, 2026): Changes have been made [here](https://github.com/bitwarden/android/pull/6740) to ensure the shared codes appear in alphabetical order. The update should make it out to production in a few weeks.
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#39415
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?