Getting started with 1Password for your growing team, or refining your setup? Our Secured Success quickstart guide is for you.
Forum Discussion
Solved
Date field format does not match system settings
In the macOS client, I was just entering the details for a new item and notice the date fields are using mm/dd/yyyy as template. The macOS system settings are set to dd/mm/yyyy. This incon...
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
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
I'm not sure why this is marked as solved as I live in a locale that uses DD-MM-YYYY; but I set my OS to YYYY-MM-DD (because that's the CORRECT way to format dates - I'm opinionated that way, but ISO8601 is a common way to deal with this). I really don't understand why I see dates formatted in ways that I don't want or use anywhere in my system. Please prioritise fixing this, it isn't just a preference but errors get made and then there are consequences. My child's passport application was held up because of this bug (month and date transposed led to secondary questioning). Again - this isn't a cutesy thing but a real operability bug. As a 10+ year customer I really really want to see this fixed. The whole world isn't using the same date system and that the ISO standard isn't working correctly is a bit of a shocker to me after all these years. Sorry that I'm venting; but this isn't just a preference - it causes people problems.
1P_Dave
Moderator
Moderator muonzoo
I'm sorry for the impact that this issue has caused. 1Password should respect your system date format and this is a known issue that our development team is working to resolve in a future update.
-Dave
Thanks for the response. I'm not sure that I reported another subtle and dangerous bug: dates appear in iso8601 as per my locale setting but when I hit edit it quickly reverts to something else mm/dd/yyyy or dd/mm/yyyy. Which causes data entry errors as I need to notice and transpose.
apologies if this is documented elsewhere but I'm on mobile today.
- 1P_Dave
Thank you for the report, I can confirm that seeing a different date format when viewing an item and editing an item is also a known issue that can occur for certain system regions and date formats. Our developers are working to resolve the issue and I've added your report to the internal work item open with the team, I'm sorry for the confusion.
-Dave
Thanks Dave! Much appreciated
