github-starred/android
2
0
Fork 0
mirror of https://github.com/bitwarden/android.git synced 2026-03-13 13:44:36 -05:00
Code Issues 144 Packages Projects Releases 116 Wiki Activity

Can't change date standard #2165

New Issue
Closed
opened 2025-11-26 23:10:45 -06:00 by GiteaMirror · 4 comments
GiteaMirror commented 2025-11-26 23:10:45 -06:00
Owner
Copy Link

Originally created by @svendsvin on GitHub (Feb 4, 2025).

Steps To Reproduce

The date in Sync is set to mm/dd/yyyy and time is am/pm. I am in Europe and prefer dd/mm/yyyy and 24 hour time.

Expected Result

A European standard date/time.

Actual Result

The date is US standard

Screenshots or Videos

Image

Additional Context

No response

Build Version

  1. 1.1

What server are you connecting to?

US

Self-host Server Version

No response

Environment Details

Motorola g54 G5 Android 14

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 @svendsvin on GitHub (Feb 4, 2025). ### Steps To Reproduce The date in Sync is set to mm/dd/yyyy and time is am/pm. I am in Europe and prefer dd/mm/yyyy and 24 hour time. ### Expected Result A European standard date/time. ### Actual Result The date is US standard ### Screenshots or Videos ![Image](https://github.com/user-attachments/assets/6d28cd68-dbe4-4fd0-93c5-633a0f459471) ### Additional Context _No response_ ### Build Version 2025. 1.1 ### What server are you connecting to? US ### Self-host Server Version _No response_ ### Environment Details Motorola g54 G5 Android 14 ### 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 bug label 2025-11-26 23:10:45 -06:00
GiteaMirror commented 2025-11-26 23:10:46 -06:00
Author
Owner
Copy Link

@bitwarden-bot commented on GitHub (Feb 4, 2025):

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

@bitwarden-bot commented on GitHub (Feb 4, 2025): Thank you for your report! We've added this to our internal board for review. ID: PM-17941
GiteaMirror commented 2025-11-26 23:10:46 -06:00
Author
Owner
Copy Link

@richardb64 commented on GitHub (Feb 5, 2025):

Looks like this has been a long-standing issue, though I only recently noticed it. #3717 is the same problem, reported last August.

@richardb64 commented on GitHub (Feb 5, 2025): Looks like this has been a long-standing issue, though I only recently noticed it. #3717 is the same problem, reported last August.
GiteaMirror commented 2025-11-26 23:10:46 -06:00
Author
Owner
Copy Link

@richardb64 commented on GitHub (Feb 6, 2025):

The same problem also affects the "last updated" date on individual entries in the vault. That's more of an issue, because those dates are typically weeks or months in the past, so the date is relevant and needs to be unambiguous and understandable by the user (whereas the "last sync" is seldom more than a few minutes ago).

@richardb64 commented on GitHub (Feb 6, 2025): The same problem also affects the "last updated" date on individual entries in the vault. That's more of an issue, because those dates are typically weeks or months in the past, so the date is relevant and needs to be unambiguous and understandable by the user (whereas the "last sync" is seldom more than a few minutes ago).
GiteaMirror commented 2025-11-26 23:10:47 -06:00
Author
Owner
Copy Link

@MarikaBW commented on GitHub (Feb 8, 2025):

Hi there!

Thank you for your report, it seems like it is a duplicate of this one: https://github.com/bitwarden/android/issues/3717.

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

This issue will now be closed.

Thanks!

@MarikaBW commented on GitHub (Feb 8, 2025): Hi there! Thank you for your report, it seems like it is a duplicate of this one: https://github.com/bitwarden/android/issues/3717. If you wish to add any further information/screenshots/recordings etc., please feel free to do so at any time in there - our engineering team will be happy to review these. This issue will now be closed. Thanks!
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 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#2165
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?