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

Sync text date format not match system settings #1957

New Issue
Open
opened 2025-11-26 23:03:00 -06:00 by GiteaMirror · 13 comments
GiteaMirror commented 2025-11-26 23:03:00 -06:00
Owner
Copy Link

Originally created by @MDXDave on GitHub (Aug 12, 2024).

Bitwarden Beta

  • I'm using the new native Bitwarden Beta app and I'm aware that legacy .NET app bugs should be reported in bitwarden/mobile

Steps To Reproduce

  1. Change device languages to german
  2. Go to 'Einstellungen'
  3. Click on 'Sonstiges'

Expected Result

The text should show the last synced date & time in the system settings (e.g. DD/MM/YYY, HH:MM, 24 hours):

Zuletzt synchronisiert 12/08/2024 19:40

Actual Result

The text shows a (fixed?) Format, not reespecting the system settings (M/DD/YYYY, 12 hours)

Zuletzt synchronisiert: 8/12/2024 7:40 PM

Screenshots or Videos

Screenshot_20240812_194223_Bitwarden Beta

Additional Context

No response

Build Version

2024.08 18985

Environment Details

  • Device: Samsung Galaxy S23 Ultra
  • OS: 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 @MDXDave on GitHub (Aug 12, 2024). ### Bitwarden Beta - [x] I'm using the new native Bitwarden Beta app and I'm aware that legacy .NET app bugs should be reported in [bitwarden/mobile](https://github.com/bitwarden/mobile) ### Steps To Reproduce 1. Change device languages to german 2. Go to 'Einstellungen' 3. Click on 'Sonstiges' ### Expected Result The text should show the last synced date & time in the system settings (e.g. DD/MM/YYY, HH:MM, 24 hours): > Zuletzt synchronisiert 12/08/2024 19:40 ### Actual Result The text shows a (fixed?) Format, not reespecting the system settings (M/DD/YYYY, 12 hours) > Zuletzt synchronisiert: 8/12/2024 7:40 PM ### Screenshots or Videos ![Screenshot_20240812_194223_Bitwarden Beta](https://github.com/user-attachments/assets/e14b3150-07b4-443a-b5e1-c4d879fdb4d1) ### Additional Context _No response_ ### Build Version 2024.08 18985 ### Environment Details - Device: Samsung Galaxy S23 Ultra - OS: Android 14 ### 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 2025-11-26 23:03:00 -06:00
GiteaMirror commented 2025-11-26 23:03:01 -06:00
Author
Owner
Copy Link

@bitwarden-bot commented on GitHub (Aug 12, 2024):

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

@bitwarden-bot commented on GitHub (Aug 12, 2024): Thank you for your report! We've added this to our internal board for review. ID: PM-10795
GiteaMirror commented 2025-11-26 23:03:01 -06:00
Author
Owner
Copy Link

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

I've just noticed that this is even an issue between dialects of English - the "Last sync" message in the Android app appears to be fixed to display in the confusing half-reversed American format (M/dd/yy h:mm a). The same problem affects the "Last updated" message on individual vault items.

If for some technical reason it's really not possible for this to be properly localised, could it perhaps at least then universally use the ISO standard format? (yyyy-MM-dd HH:mm)?

@richardb64 commented on GitHub (Feb 5, 2025): I've just noticed that this is even an issue between dialects of English - the "Last sync" message in the Android app appears to be fixed to display in the confusing half-reversed American format (M/dd/yy h:mm a). The same problem affects the "Last updated" message on individual vault items. If for some technical reason it's really not possible for this to be properly localised, could it perhaps at least then universally use the ISO standard format? (yyyy-MM-dd HH:mm)?
GiteaMirror commented 2025-11-26 23:03:01 -06:00
Author
Owner
Copy Link

@edent commented on GitHub (Feb 20, 2025):

This error also shows up in the TOTP section in version 2025.1.2 (19740). This makes it misleading when trying to understand if a TOTP code is valid.

I think the issue is with this line:

61c48bf673/app/src/main/java/com/x8bit/bitwarden/ui/platform/feature/settings/other/OtherViewModel.kt (L28)

However, there seem to be a few places where "month / day" is hardcoded

https://github.com/search?q=repo%3Abitwarden%2Fandroid+%22d%2Fyy%22&type=code

@edent commented on GitHub (Feb 20, 2025): This error also shows up in the TOTP section in version 2025.1.2 (19740). This makes it misleading when trying to understand if a TOTP code is valid. I think the issue is with this line: https://github.com/bitwarden/android/blob/61c48bf6736cb6777336ec1b9e9b30ff5b7102e8/app/src/main/java/com/x8bit/bitwarden/ui/platform/feature/settings/other/OtherViewModel.kt#L28 However, there seem to be a few places where "month / day" is hardcoded https://github.com/search?q=repo%3Abitwarden%2Fandroid+%22d%2Fyy%22&type=code
GiteaMirror commented 2025-11-26 23:03:01 -06:00
Author
Owner
Copy Link

@richardb64 commented on GitHub (May 3, 2025):

Any progress on this? ETA for a fix? Is there anywhere that users can track any further discussion? This is really quite a serious and basic fault in an application that desires global reach. For anyone anywhere outside the US, the "M/d/yyyy" format is dangerously misleading.

@richardb64 commented on GitHub (May 3, 2025): Any progress on this? ETA for a fix? Is there anywhere that users can track any further discussion? This is really quite a serious and basic fault in an application that desires global reach. For anyone anywhere outside the US, the "M/d/yyyy" format is dangerously misleading.
GiteaMirror commented 2025-11-26 23:03:01 -06:00
Author
Owner
Copy Link

@richardb64 commented on GitHub (May 3, 2025):

This general problem isn't specific to Android, either. The Windows desktop app similarly ignores the user's locale and displays dates in the form "Jan 31, 2020, 1:23:45 PM". At least the use of a textual month makes it less ambiguous, but it's still wrong. The web vault seems to get it right.

@richardb64 commented on GitHub (May 3, 2025): This general problem isn't specific to Android, either. The Windows desktop app similarly ignores the user's locale and displays dates in the form "Jan 31, 2020, 1:23:45 PM". At least the use of a textual month makes it less ambiguous, but it's still **wrong**. The web vault seems to get it right.
GiteaMirror commented 2025-11-26 23:03:01 -06:00
Author
Owner
Copy Link

@richardb64 commented on GitHub (May 3, 2025):

Also to be clear (because the related issues have been closed as duplicates): this issue doesn't only affect the "last sync" date. It seems to affect pretty much everywhere a date is displayed across the entire application - notably also in the "last updated" date on individual records.

@richardb64 commented on GitHub (May 3, 2025): Also to be clear (because the related issues have been closed as duplicates): this issue doesn't _only_ affect the "last sync" date. It seems to affect pretty much everywhere a date is displayed across the entire application - notably also in the "last updated" date on individual records.
GiteaMirror commented 2025-11-26 23:03:02 -06:00
Author
Owner
Copy Link

@david-livefront commented on GitHub (Oct 22, 2025):

@richardb64 This issue should have been fixed here.

Can you confirm that this issue is resolved for you?

@david-livefront commented on GitHub (Oct 22, 2025): @richardb64 This issue should have been fixed [here](https://github.com/bitwarden/android/pull/5333). Can you confirm that this issue is resolved for you?
GiteaMirror commented 2025-11-26 23:03:02 -06:00
Author
Owner
Copy Link

@richardb64 commented on GitHub (Oct 22, 2025):

Looks good! Many thanks for getting this over the line @david-livefront!

The Windows desktop app still seems to have the same problem, though - do you know if that's being worked on (with I guess an almost identical fix to the one you've successfully applied to Android)?

@richardb64 commented on GitHub (Oct 22, 2025): Looks good! Many thanks for getting this over the line @david-livefront! The Windows desktop app still seems to have the same problem, though - do you know if that's being worked on (with I guess an almost identical fix to the one you've successfully applied to Android)?
GiteaMirror commented 2025-11-26 23:03:02 -06:00
Author
Owner
Copy Link

@david-livefront commented on GitHub (Oct 22, 2025):

@richardb64 I don't believe anyone on the desktop app is investigating this. I would recommend writing up an issue in the clients repo.

@david-livefront commented on GitHub (Oct 22, 2025): @richardb64 I don't believe anyone on the desktop app is investigating this. I would recommend writing up an issue in the [clients repo](https://github.com/bitwarden/clients).
GiteaMirror commented 2025-11-26 23:03:02 -06:00
Author
Owner
Copy Link

@david-livefront commented on GitHub (Oct 22, 2025):

@richardb64 I did reach out to one of the client devs and we were hoping you could provide a screenshot of exactly where this issue is occurring on desktop?

@david-livefront commented on GitHub (Oct 22, 2025): @richardb64 I did reach out to one of the client devs and we were hoping you could provide a screenshot of exactly where this issue is occurring on desktop?
GiteaMirror commented 2025-11-26 23:03:03 -06:00
Author
Owner
Copy Link

@pamperer562580892423 commented on GitHub (Oct 22, 2025):

As I see it, at least the browser extension 2025.10.0 still has it (Settings --> Vault options):

Image

PS: ... as I also documented it here: https://github.com/bitwarden/android/issues/5327 😉

@pamperer562580892423 commented on GitHub (Oct 22, 2025): As I see it, at least the browser extension 2025.10.0 still has it (Settings --> Vault options): <img width="613" height="114" alt="Image" src="https://github.com/user-attachments/assets/19ea213f-9a7f-40ff-abac-49ef641d8c2b" /> PS: ... as I also documented it here: https://github.com/bitwarden/android/issues/5327 😉
GiteaMirror commented 2025-11-26 23:03:03 -06:00
Author
Owner
Copy Link

@richardb64 commented on GitHub (Oct 22, 2025):

@richardb64 I did reach out to one of the client devs and we were hoping you could provide a screenshot of exactly where this issue is occurring on desktop?

No problem - I'll gather some examples from the desktop app. Is there a relevant issue over on the other repo to attach them to?

@richardb64 commented on GitHub (Oct 22, 2025): > @richardb64 I did reach out to one of the client devs and we were hoping you could provide a screenshot of exactly where this issue is occurring on desktop? No problem - I'll gather some examples from the desktop app. Is there a relevant issue over on the other repo to attach them to?
GiteaMirror commented 2025-11-26 23:03:03 -06:00
Author
Owner
Copy Link

@david-livefront commented on GitHub (Oct 22, 2025):

@richardb64 I did reach out to one of the client devs and we were hoping you could provide a screenshot of exactly where this issue is occurring on desktop?

No problem - I'll gather some examples from the desktop app. Is there a relevant issue over on the other repo to attach them to?

I don't believe there is an issue for this at this time.

@david-livefront commented on GitHub (Oct 22, 2025): > > [@richardb64](https://github.com/richardb64) I did reach out to one of the client devs and we were hoping you could provide a screenshot of exactly where this issue is occurring on desktop? > > No problem - I'll gather some examples from the desktop app. Is there a relevant issue over on the other repo to attach them to? I don't believe there is an issue for this at this time.
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#1957
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?