Date format is incorrect in 1Password for Mac

Same here running Sonoma. I think Apple changed the behaviour in Sonoma.

@GreyM1P did the developers test on Ventura or Sonoma?

Why can't I have a different date format? I'm not getting an option for DD MMM YYYY.

@SebDanielsson I can't imagine this works differently in Sonoma. I have a MPB2017 running Ventura at the office, I'll check if it's fixed later today on there and will report back here.

They did change it. The date in the menu bar on Sonoma is in the wrong format where it was not under Ventura. If the change had any effect on 1Password is still not certain.

I just checked on Ventura with the same region settings, same issue there. So it seems the developers didn't test on Ventura as well.

1Pwd Mac 8.10.16: date format follows the macOS settings for:
❌passkey date | ✅custom date fields | ✅modified/created date

1Pwd Win 8.10.16: date format follows the Windows settings for:
❌passkey date | ✅custom date fields | ❌modified/created date

It would be good to fix the red crosses. Maybe the developers can call the same function to get the right output according to the OS settings.

Weird, because for me custom dates also don't work (expiry date in my screenshot is a custom date field).

I’m sorry for the confusion. We expect that the fix included with 8.10.18 will improve the situation for some customers but are aware that it’s not a complete fix yet. If you are not seeing an improvement yet, your region was not included in this update. Our developers are continuing to work on the issue so that we can get the date format correct for all regions. If you’re still running into the issue on the latest version of 1Password for Mac then please post in this thread, and include a screenshot of your region settings, and I’ll make sure to get this information to our development team.

For those who have already posted that the fix didn't work for them, there's no need to post your information again and we're committed to getting things fixed for you as well.

-Dave

Why is that fix region specific? 1Password should just use the date and time format provided by the operating system locale whenever a date or time is shown, no matter what language or region is configured. You can also have different date/time formats for the same region. I'm genuinly surprised that this seems to be so complicated since this is pretty basic and has been solved for decades.

I agree with @fok , as a developer myself this seems inefficient at best, but it even sounds a bit sloppy. And that is not a word I like to use in relation to software which stores all my passwords and private data…

Maybe a 1P developer can share some insights on this bug and the ways you are trying to solve this? Because I’m honestly starting to feel a bit anxious about this. I am completely aware that something “cosmetic” like region settings doesn’t influence the security of an application (per se), but the way this is handled, is starting to feel more and more unprofessional.

Sorry for being a bit harsh about this, It’s not to be taken personally. But I would really like to be proven wrong about my feelings.