Itβs Cybersecurity Awareness Month! Join our interactive training session, or learn about security and AI from 1Password experts.
Forum Discussion
cpmcgrath
2 years agoNew Contributor
Date format in date editing control does not respect locale settings
When viewing an entry with a date in it, it shows in the correct format - dd/MM/yyyy. You then hit the edit button, and it switches to MM/dd/yyyy.
As a side, the control is very hard to use, as you have to use the popup calendar to navigate to the month you want and select the day. Really, we just want to be able to type 21/02/1992 and be done with it.
1Password Version: 8.10.33
Extension Version: Not Provided
OS Version: Windows 11
Browser: Not Provided
Hello folks,
Our developers have released improvements to how 1Password handles date formatting in the latest version of the 1Password desktop app (8.10.80). You can read more here: Improved date formatting in the 1Password desktop app
This update resolves the issue reported by the original poster in this thread where you might have seen different date formats when viewing and when editing an item in certain situations.
If you still see an issue with version 8.10.80 (or later) then please post a screenshot of what you see in the 1Password app and your current operating system region/date settings in the new thread. I'll close this old thread in order to keep the conversation in one place.
-Dave
28 Replies
Replies have been turned off for this discussion
- 1P_Dave
Moderator
Hello folks,
Our developers have released improvements to how 1Password handles date formatting in the latest version of the 1Password desktop app (8.10.80). You can read more here: Improved date formatting in the 1Password desktop app
This update resolves the issue reported by the original poster in this thread where you might have seen different date formats when viewing and when editing an item in certain situations.
If you still see an issue with version 8.10.80 (or later) then please post a screenshot of what you see in the 1Password app and your current operating system region/date settings in the new thread. I'll close this old thread in order to keep the conversation in one place.
-Dave
- 1P_Dave
Moderator
cpmcgrathβ, bb1β, echobeachβ, StephenR306β, roy_orbisonβ
Thank you for your patience. Our developers are testing a fix in the latest beta version of the 1Password desktop app. Would you mind temporary switching to the beta version to see if the fix resolves the issues that you're seeing:
If you still see the issue with Beta 8.10.80-18 (or later) can you post screenshot of what you see in the 1Password app and your current operating system region/date settings?-Dave
- bb1New Contributor
Hi Dave, I've switched to the Beta channel and attempted to update the date in the membership card. The issue looks to be fixed, as it was showing dd/mm/yyyy.
Do you know when the Beta with the fix will be released to Production? I resisted updating to Beta in the past because it used to be a pain to switch back to Production, I'm not sure if that's still the case.
- 1P_Dave
Moderator
Thank you for confirming that the beta fixes the issue for you! We expect to release the fix to the stable version as soon as testing in the beta is complete. If you'd like to roll back to the stable version you can use the steps in this guide.
edit: See our new post here.
-Dave
- bb1New Contributor
How has this issue been left languishing for 2 years? Do your developers not realise that everyone outside the US does NOT use mm/dd/yyyy?
I had to update an expiry date for a membership card, and found there is absolutely no way to view dates in the way that is correct for me: dd/mm/yyyy. A date displayed as "04/01/2026" in 1Password means 4th January 2026 to me.
Please update this, and fast. It should be a high priority issue. I presume you have lots of users outside the US. FYI this is in the latest MacOS build.
- echobeachNew Contributor
1P_Dave I agree the default should be ISO (not mm/dd/yyyy). The Windows app also does not respect system date format. Android app just has dashes (--/--/----) which is also a curious design decision but is also in mm/dd/yyyy. Finally, the graphical date picker does not have a year toggle so you have to endlessly scroll through months for distant dates. This has been an issue for ages (excuse the pun). How about a Settings option?
- 1P_Dave
Moderator
Thank you for the feedback, I'll pass along your requests regarding the date format to the team for consideration.
Finally, the graphical date picker does not have a year toggle so you have to endlessly scroll through months for distant dates.
On which platform are you seeing this? If you're on mobile, can you open the year selector by tapping on the Month/Year? If you can't then can you post a screenshot of what you see?
-Dave
PB-47587804
- echobeachNew Contributor
I think the date pickers have been updated so the year/month selector is now present in both versions (Win and Android). Thanks!
The Android app (v. 8-10-70) now displays saved dates in YYYY-MM-DD (respecting the system setting - success!). However, it is displaying --/--/---- in a new item before a date is selected which is odd.
The Windows app (v. 8-10-70) does not respect the system setting. It displays dates as MM/DD/YYYY before and after a date is picked. All saved dates are in the US format.
So, partly resolved! Thanks for following up.
- 1P_Dave
Moderator
The issue is still open with our development team, I'm sorry for the continued inconvenience.
-Dave
- StephenR306New Contributor
This is still an issue in January 2025.
- 1P_Dave
Moderator
- roy_orbisonOccasional Contributor
1P_Dave I get that, but it's still using a poor default. From my logs (that also have the good sense to use ISO dates):
text
INFO 2024-11-06T23:07:01.540+00:00 ThreadId(18) [1P:op-localization/src/lib.rs:230] system locale detected as 'en-GB'
INFO 2024-11-06T23:07:01.543+00:00 ThreadId(18) [1P:op-localization/src/lib.rs:256] selected translations for EN_US based on detected locale en-GB
Even if the locales are improved, it's quite possible there will continue to be edge cases, and in those cases U.S. formats should not be the default. If the translation locale is not an exact match of the system's, it should still fall back to ISO. - 1P_Dave
Moderator
1Password should respect the system date format but there are cases where that isn't occurring, such as if you have a different region set from your preferred language, and our development team is actively working on the issue.
I apologize for the inconvenience. Keep an eye on our release notes which will mention a fix as soon as it is released: https://releases.1password.com/
-Dave
ref: dev/core/core#28051
- roy_orbisonOccasional Contributor
If 1Pass can't yet format dates based on users' locales, it should at least use the unambiguous ISO format. It still places month before day but everyone knows what's what when you use YYYY-MM-DD. https://alessandrorossini.org/we-can-put-an-end-to-month-day-year-dates/