Date format is incorrect in 1Password for Mac

@Arnoud

Thank you for the feedback and I'm sorry for the friction that the issue is causing. I've forwarded your request and comments to our development team so that they're aware of the impact to you.

-Dave

I came there to report the same thing. I have YYYY-MM-DD set as date format in macOS (13.4)

In 8.10.7 the date editor uses YYYY-MM-DD (but without leading zeros) but the display is still DD/MM/YYYY

@leedxw

I'm sorry that the issue is affecting your use of 1Password as well. I've added your report to the internal work item open for the issue.

-Dave

Hi,

I am having trouble with the date formats on macOS. My passport expiry is shown in MM/DD/YYYY, even though my date locale is clearly set to DD.MM.YYYY. In 1Password 7, as far as I can tell, it used to be DD/MM/YYYY.

I have literally had a ton of trouble because of this because I entered my passport expiry date wrong on an airline form. As both numbers in the date can be flipped and will still show a valid date, this error isn't easy to catch, either. After looking this up, it has been first reported over 1.5 years ago! That is not an acceptable timeframe!

Can you please share a specific timeline for this to be fixed? I have been in touch with email support over this and they told me it would be forwarded and eventually fixed. This was months ago as well, with no update at all. It is not a hard thing to fix! Yet, it causes a ton of trouble for the affected members.

I realize the company likely uses North American date formats, but please consider the impact on the European folks on here, too.

Cheers

1Password Version: 8.10.8
Extension Version: Not Provided
OS Version: macOS 13.4.1
Browser: Not Provided

@nikxda

I'm sorry that you're also affected by the issue. I don't have an update to share at the moment but I can tell you that our developers are aware that this is something in need of fixing that is causing friction and frustration for many people.

I've passed along your comments to the team and I'll continue to push to have us improve how dates are localized so that we can improve the situation.

-Dave

Here to echo @nikxda . It’s been over a year and the one version still supporting date formats is now EOL, leaving non-US users with a broken format.

You even already have this partially programmed, as “created/modified” fields and the date fields in edit mode on iOS use the system format, but not date fields in “view” mode:

And in edit mode:

+1 for this.

I noticed, just in time, that my drivers license would expire the 10th of May and not the 5th of October (5/10/2023 is October for me, not May). Was not happy about this. Come on guys, this is a very annoying bug that has actual real life implications.

@posttoast

Good morning! I'll let the team know you've encountered this. I'm sorry for the trouble.

ref: dev/core/core#8747

I’m surprised on how long does it take to take care of date format. This is going on since more than a year and still there’s no update for it? I’m sure this is one of the easiest part in the software compared to the complete app and the system.

It‘s almost two years now since it was reported. For me this is slowly but surely also a sign of lack of respect towards your international customers.