It’s Cybersecurity Awareness Month! Join our interactive training session, or learn about security and AI from 1Password experts.
Forum Discussion
1P_justin
1Password Team
5 months agoImproved date formatting in the 1Password desktop app
Hello 1Password Community!
With the next update to the 1Password desktop app (version 8.10.80), we have improved how date formats are handled when viewing and editing an item.
Leading up to this ...
alexejk
4 months agoNew Contributor
Creating a separate thread as the original issue of Date format in date editing control does not respect locale settings | 1Password Community was resolved
From my understanding, 8.10.80 is supposed to improve handling of date formatting, but at the moment it does not seem to follow system locale settings.
According to another post, I read that the release "Decouples date formatting from 1Password’s supported languages and it respects the OS’s locale choice." My observation however is different - system locale formatting settings are not honored by 1Password app on Mac or Windows (or im misunderstanding what the point above should mean).
Regardless, the main issue is that 1Password is showing unexpected date format that is unreadable without mental gymnastics for anyone who does not use the mm/dd/yyyy format (and is often confusing and leading to problems).
Here is the example on Mac settings and how 1Password display things.
MacOS Region & Locale SettingsLanguage settings in the 1Password app (I assume should be ignored - but set to System defaults)1Password format for fields always mm/dd/yyyyThe observed date format seems to always default to "mm/dd/yyyy" even thought system locale defines it at "yyyy-mm-dd". Even if i change locale to "yyyy/mm/dd" or "dd/mm/yyyy" for my systems, it does not seem to take any effect on what 1Password shows, which creates a lot of confusion and frustration when copying or viewing data such as expiration dates for different elements in the vault.
I have also tested the Beta channel and validated that behavior seems to be the same on Windows as well as Mac. Behavior is obviously wrong for anyone outside of US (as we don't use that format).
Additional thought: Using an ISO standard date format would make more sense as a default if its not possible to determine the locale format from the system, but I believe every system readily exposes it.
-----
1Password Version: 8.10.80
OS Versions: Windows 11, MacOS 15.5
1P_Dave
Moderator
4 months agoHello alexejk! 👋
Thanks for reaching out, I've merged your post into our new thread for date formatting. The improvements in 1Password for Mac version 8.10.80 do the following:
- Completely resolve an issue where, in certain situations, you might see a different date format when viewing an item and when editing an item.
- Decouple date formatting from 1Password's supported languages and it respects the OS's locale choice.
For the Mac, the date format currently corresponds to the default date format associated with your currently selected preferred language rather than the region. Customizations beyond the default date format aren't supported but our developers are considering further improvements in the future and I'll pass along your feedback.
Can you let me know what your current preferred language is in macOS system settings?
-Dave
- franciscolour2 months agoNew Contributor
- pepijnve2 months agoNew Contributor
For the Mac, the date format currently corresponds to the default date format associated with your currently selected preferred language rather than the region.
TBH, this is a really poor implementation choice. The system data format can be configured independently from the preferred languages and the region on macOS. Why not use the actual date format setting instead of making an incorrect derivation? The current implementation means I really can't trust 1password when it comes to date fields and always need to triple check.
As an example, in 1password I now see dates like this
while my system settings are.
- jimthing2 months agoDedicated Contributor
While I completely agree, I explained a couple of issues with how 1P may have trouble selecting a date format if they have different ones set across devices, and even if not, this would mean a lot more coding to sort out.
See this thread post (on the related alerts date format issue):
- franciscolour2 months agoNew Contributor
Same problem. English as language, but living in the EU.
- ckd4 months agoNew Contributor
Since I don't see a language choice for "English - People Who Use ISO 8601", let me add my vote for having 1Password 8 use the system locale since that's what I, the user, have actually chosen.
Note that in this screenshot not only does it not use the chosen short date format, it doesn't even honor the system's 24 hour time setting for the "last edited" date!
- alexn4 months agoNew Contributor
Hello 1P_Dave,
I have English (English — Primary) set as my Preferred language and the Region is Spain. My 1Password 8.10.80 for Mac formats dates as MM/DD/YYYY.
I understand that the Region doesn't matter now, so what Preferred Language should I set to have dates in 1Password as DD/MM/YYYY?
- Dunecat4 months agoDedicated Contributor
I'd try English UK, if that's an option--but I'm just a guy on the Internet and have no idea if that is actually an option
- semraae4 months agoNew Contributor
1P_Dave I think you might not have enough non-Americans in your team? It's very common for people in Europe to set their OS language to English. And because people in Europe in general don't use the US date format MM/DD/YYYY, they then change the date format to the either the typical DD/MM/YYYY or the ISO format of YYYY/MM/DD
1password 7 handled this fine by using the system's date format, it would be good if 1password 8 did the same and behaved like a standard app.
For now a workaround, alexn you can set the preferred language to English UK. This will default to the UK date format and so use DD/MM/YYYY. I personally prefer the ISO format but at least that prevents filling out the passport expiration date wrong on websites (which I almost did because of 1password not respecting dates properly)