Date format is incorrect in 1Password for Mac

I’ve observed something new and different. When I look at an item with date the date format is DD/MM/YY. When I edit the same contacts it’s showing me DDMMMYYYY. My suggestion was that it appears in DDMMMYYYY format and show all orders. This is on iOS.
On android it’s different. On my pixel it’s yyyy-mm-dd. This is when I open an item. In edit it’s Dd/m/yyyy.

Still no change for me as of v8.9.15 on macOS. Times and dates in 1Password remain stubbornly in US format, regardless of system settings.

When will the world date filter to the production version? I'm on the current 1Password for Mac 8.9.15 (80915001) and the dates are still the US version.

@kamion

We don't have a date for when this will reach the Production version, but you can find out what's new each time 1Password updates by choosing the question-mark icon next to the "+ New Item" button, then What's New in the dropdown menu.

Alternatively, you can visit our 1Password Releases blog directly:

☞ 1Password Releases – Mac

The release note for 8.9.12 seems to say that localization for dates and time have been added.

but on 1Password for Mac 8.9.15 (80915001), the dates are still being shown in US format:

The Settings on my Mac are correct:

Is there some setting to be done or option to be turned on?

Using 8.10.0 and it still appears incorrectly for me. Changing the language to some other place in the world where the order is sensible doesn't change the numbers either, this behaves like it is hard-coded.

same problem here - please correct the date format - this used to be correct but for some reason it's broken now

This only happens on mac by the way. The dates appear in the right order in version 8.10.0 on windows.

Are there any updates on this? I just botched my passport dates while booking a flight due to this issue. I’m using 1Password for Mac 8.10.0 (81000055).

I've been ignoring this as a minor annoyance, but like @jgwhite I just had real-world consequences when I based the answer to a colleague's question on a date I read from 1Password, leading to some embarrassment for me — 4 November, not April 11.

As a programmer myself, I tend to have understanding for the challenges developers face. But for heaven's sake, time/date representation is a solved issue where in any high-level language or framework, you have built-in facilities to do the hard work for you.

I cannot offhand think of a single Mac app I have ever used that had an issue with displaying times and dates in the format I selected system-wide. At which point I'm starting to think, if a company has this much of an issue fixing a trivial problem like this over such a long period of time, why would I believe they still have the technical savvy to protect those most personal secrets I entrusted to them?

I mean, come on. That cryptography and infosec stuff is supposed to be hard. This should be simple!