Date format is incorrect in 1Password for Mac

That’s not actually a fix though, is it? I have my language set to US English for a reason. Changing it to UK English because of a bug in 1P which STILL hasn’t been fixed, seems rather silly.

+1 @posttoast
I find 1P v8 less friendly to use that v7. This is an egregious example, but not the only example.

@SebDanielsson, @andrehjan, @dalembertian, and @posttoast

Thank you for posting details about your configuration. I've added everything to the internal work item open with our development team.

You can indeed workaround the issue by changing your preferred language but, just to be clear, that isn't considered a fix by the team. The issue is still open internally and active work is being done to get things working correctly for each of the cases being reported to us in this thread.

Thank you again for your patience. 🙂

-Dave

@1P_Dave

If there is any way for me to help you guys resolve this issue (test build, log files, whatever) please let me know. It would be very nice if this would finally be fixed.

@posttoast

The issue is reproducible here on our end so no other information is needed for now, however I'll definitely post here if our developers do request anything else. Thank you for the kind offer to help. 🙂

-Dave

Hi @1P_Dave , any news yet?

@posttoast

1Password 8.10.18 was released yesterday and contains this in its release notes:

We’ve fixed an issue where dates weren’t properly formatted in some regions when US English was selected as your language.

— from 1Password Releases – Mac

Try updating and using US English in a non-US region and let us know how things go.

Nope.

This is the non-edit-mode:

(this should show 13/7/23, or preferably even 13/7/2023)

This is the edit mode:

This one is correct.

Same issue still also on iOS, in the latest version of 1P (8.10.18).

Once more, for completeness sake, my region settings in MacOS 14.0:

What I honestly don't get (and I am genuinely interested) is why this is so hard to test. You guys have Macs right? Just set your language to US English en your region to The Netherlands. I have reproduced it on 4 different machines here in the office. It feels like you think you fixed the issue but didn't actually test it before releasing.

Same here, nothing has changed for me on 8.10.18 on macOS or iOS. My settings on all devices:

I confirm the same behaviour on 8.10.18 on Sonoma with my Region - Spain and language "English - Primary". And I agree that the fix is looking like not tested at all.