github-starred/android
2
0
Fork 0
mirror of https://github.com/bitwarden/android.git synced 2026-06-10 00:28:29 -05:00
Code Issues 2.2k Packages Projects Releases 127 Wiki Activity

[GH-ISSUE #6579] [PM-32721] Password history not sorted #15111

New Issue
Closed
opened 2026-04-15 01:29:13 -05:00 by GiteaMirror · 10 comments
GiteaMirror commented 2026-04-15 01:29:13 -05:00
Owner
Copy Link

Originally created by @fiorins on GitHub (Feb 25, 2026).
Original GitHub issue: https://github.com/bitwarden/android/issues/6579

Steps To Reproduce

  1. Go to one entry
  2. Click on password history

Expected Result

It should be a sorted list but it is not.
I uploaded screenshots from the web app because it was difficult for me to edit them from the mobile, but the order is the same as what appears on the app.

The two edited screens are entries that I don't remember where I created, whether mobile or web, but the other "mobile test" I created and edited only on mobile.

Actual Result

a mixed list not sorted by timestamps

Screenshots or Videos

Image Image Image

Additional Context

No response

Build Version

2026.2.0 (21203)

What server are you connecting to?

US

Self-host Server Version

No response

Environment Details

© Bitwarden Inc. 2015-2026

Version: 2026.2.0 (21203)
📱 samsung SM-S901B
🤖 16@36
📦 prod
🧱 commit: bitwarden/android/release/2026.2-rc46@cbe13d2015f97955de1e0f11a229330ddd4654c0
💻 build source: bitwarden/android/actions/runs/21762978463/attempts/1
🦀 SDK: 2.0.0-4872-065ef30b
🌩 Server: 2026.2.0 @ US

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 @fiorins on GitHub (Feb 25, 2026). Original GitHub issue: https://github.com/bitwarden/android/issues/6579 ### Steps To Reproduce 1. Go to one entry 2. Click on password history ### Expected Result It should be a sorted list but it is not. I uploaded screenshots from the web app because it was difficult for me to edit them from the mobile, but the order is the same as what appears on the app. The two edited screens are entries that I don't remember where I created, whether mobile or web, but the other "mobile test" I created and edited only on mobile. ### Actual Result a mixed list not sorted by timestamps ### Screenshots or Videos <img width="1176" height="998" alt="Image" src="https://github.com/user-attachments/assets/e72868f5-56f4-4c8c-985b-f4f36e695c22" /> <img width="1200" height="1000" alt="Image" src="https://github.com/user-attachments/assets/6bf85063-f21c-4ea6-a14d-88f913113f3c" /> <img width="1236" height="1190" alt="Image" src="https://github.com/user-attachments/assets/511a3ecd-419c-44cb-967a-f4e9760e3997" /> ### Additional Context _No response_ ### Build Version 2026.2.0 (21203) ### What server are you connecting to? US ### Self-host Server Version _No response_ ### Environment Details © Bitwarden Inc. 2015-2026 Version: 2026.2.0 (21203) 📱 samsung SM-S901B 🤖 16@36 📦 prod 🧱 commit: bitwarden/android/release/2026.2-rc46@cbe13d2015f97955de1e0f11a229330ddd4654c0 💻 build source: bitwarden/android/actions/runs/21762978463/attempts/1 🦀 SDK: 2.0.0-4872-065ef30b 🌩 Server: 2026.2.0 @ US ### 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:password-managerbug labels 2026-04-15 01:29:14 -05:00
GiteaMirror commented 2026-04-15 01:29:15 -05:00
Author
Owner
Copy Link

@bitwarden-bot commented on GitHub (Feb 25, 2026):

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

<!-- gh-comment-id:3959988447 --> @bitwarden-bot commented on GitHub (Feb 25, 2026): Thank you for your report! We've added this to our internal board for review. ID: [PM-32721](https://bitwarden.atlassian.net/browse/PM-32721) [PM-32721]: https://bitwarden.atlassian.net/browse/PM-32721?atlOrigin=eyJpIjoiNWRkNTljNzYxNjVmNDY3MDlhMDU5Y2ZhYzA5YTRkZjUiLCJwIjoiZ2l0aHViLWNvbS1KU1cifQ
GiteaMirror commented 2026-04-15 01:29:16 -05:00
Author
Owner
Copy Link

@pamperer562580892423 commented on GitHub (Feb 25, 2026):

Another user here.

And just for clarification: all three screenshots you did provide can't be from the Android app. - The Android app does not have the "header" Item history and the order of "Created:" etc. is different. The Android still looks like this in this section, even on version 2026.2.0:

Image

PS: So, I think you should at least clarify, if you only created and edited those vault items on the Android app before. -- And/or otherwise, it might be an issue with the other BW apps as well.

<!-- gh-comment-id:3960086900 --> @pamperer562580892423 commented on GitHub (Feb 25, 2026): Another user here. And just for clarification: all three screenshots you did provide can't be from the Android app. - The Android app does not have the "header" _Item history_ and the order of "Created:" etc. is different. The Android still looks like this in this section, even on version 2026.2.0: <img width="600" height="383" alt="Image" src="https://github.com/user-attachments/assets/13e56208-fc88-457f-b869-df78ddf85ab8" /> PS: So, I think you should at least clarify, if you only created and edited those vault items on the Android app before. -- And/or otherwise, it might be an issue with the other BW apps as well.
GiteaMirror commented 2026-04-15 01:29:17 -05:00
Author
Owner
Copy Link

@fiorins commented on GitHub (Feb 25, 2026):

Thanks you are right, I edited the issue

<!-- gh-comment-id:3960142588 --> @fiorins commented on GitHub (Feb 25, 2026): Thanks you are right, I edited the issue
GiteaMirror commented 2026-04-15 01:29:17 -05:00
Author
Owner
Copy Link

@pamperer562580892423 commented on GitHub (Feb 25, 2026):

Expected Result
It should be a sorted list but it is not.
I uploaded screenshots from the web app because it was difficult for me to edit them from the mobile, but the order is the same as what appears on the app.

The two edited screens are entries that I don't remember where I created, whether mobile or web, but the other "mobile test" I created and edited only on mobile.

Okay, but then it remains also unclear if only the mobile app "caused" this, right?

And whatever causes this - when it happens, it's not only "showing" in the mobile app then...

<!-- gh-comment-id:3960257589 --> @pamperer562580892423 commented on GitHub (Feb 25, 2026): > Expected Result > It should be a sorted list but it is not. I uploaded screenshots from the web app because it was difficult for me to edit them from the mobile, but the order is the same as what appears on the app. > > The two edited screens are entries that I don't remember where I created, whether mobile or web, but the other "mobile test" I created and edited only on mobile. Okay, but then it remains also unclear if only the mobile app "caused" this, right? And whatever causes this - **when** it happens, it's not only "showing" in the mobile app then...
GiteaMirror commented 2026-04-15 01:29:18 -05:00
Author
Owner
Copy Link

@fiorins commented on GitHub (Feb 25, 2026):

yes, you are right it is unclear and it's not only "showing" in the mobile app

<!-- gh-comment-id:3960390431 --> @fiorins commented on GitHub (Feb 25, 2026): yes, you are right it is unclear and it's not only "showing" in the mobile app
GiteaMirror commented 2026-04-15 01:29:19 -05:00
Author
Owner
Copy Link

@cbbit commented on GitHub (Feb 25, 2026):

Hi there,

I am unable to reproduce this issue, it has been escalated for further investigation. If you have more information that can help us, please add it below.

Thanks!

<!-- gh-comment-id:3962293373 --> @cbbit commented on GitHub (Feb 25, 2026): Hi there, I am unable to reproduce this issue, it has been escalated for further investigation. If you have more information that can help us, please add it below. Thanks!
GiteaMirror commented 2026-04-15 01:29:20 -05:00
Author
Owner
Copy Link

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

... ah - there now is a corresponding PR: https://github.com/bitwarden/android/pull/6700

<!-- gh-comment-id:4093747820 --> @pamperer562580892423 commented on GitHub (Mar 19, 2026): ... ah - there now is a corresponding PR: https://github.com/bitwarden/android/pull/6700
GiteaMirror commented 2026-04-15 01:29:20 -05:00
Author
Owner
Copy Link

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

As @pamperer562580892423 mentioned, there is a PR for this update here.

The fix should appear in the production app in a few weeks.

<!-- gh-comment-id:4099207539 --> @david-livefront commented on GitHub (Mar 20, 2026): As @pamperer562580892423 mentioned, there is a PR for this update [here](https://github.com/bitwarden/android/pull/6700). The fix should appear in the production app in a few weeks.
GiteaMirror commented 2026-04-15 01:29:21 -05:00
Author
Owner
Copy Link

@bwbug commented on GitHub (Mar 20, 2026):

@david-livefront @djsmith85 As shown in this discussion, the root cause of the problem is that the Android app is adding password history entries to the back of the list, but all other apps are adding changed passwords to the front of the list. Thus, for a user who makes password changes on both Android and non-Android devices, this inconsistency results in a randomly ordered password history. The PR will fix the display of the such disordered lists when viewed in the Android app, but won't the password history still be disordered when viewed on other devices? Instead of just fixing the symptom of the problem, wouldn't it have made more sense to just have the Android app add entries to the front of the history list, to be consistent with the other client apps and extensions?

<!-- gh-comment-id:4100862526 --> @bwbug commented on GitHub (Mar 20, 2026): @david-livefront @djsmith85 As shown in [this discussion](https://community.bitwarden.com/t/password-history-entries-mixed-and-not-sorted-by-date/92830/10?u=grb), the root cause of the problem is that the Android app is adding password history entries to the _back_ of the list, but all other apps are adding changed passwords to the _front_ of the list. Thus, for a user who makes password changes on both Android and non-Android devices, this inconsistency results in a randomly ordered password history. The [PR](https://github.com/bitwarden/android/pull/6700) will fix the **display** of the such disordered lists when viewed in the Android app, but won't the password history still be disordered when viewed on other devices? Instead of just fixing the _symptom_ of the problem, wouldn't it have made more sense to just have the Android app add entries to the _front_ of the history list, to be consistent with the other client apps and extensions?
GiteaMirror commented 2026-04-15 01:29:22 -05:00
Author
Owner
Copy Link

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

I have made an additional PR to ensure that Android always persists the password history in a sorted manner.

This will not affect the existing sort-order but it will fix the issue the next time you update the cipher.

<!-- gh-comment-id:4113361333 --> @david-livefront commented on GitHub (Mar 23, 2026): I have made an [additional PR](https://github.com/bitwarden/android/pull/6709) to ensure that Android always persists the password history in a sorted manner. This will not affect the existing sort-order but it will fix the issue the next time you update the cipher.
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:password-manager 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#15111
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?