Date format is incorrect in 1Password for Mac

vishalsheth

1Password 8 is a complete rewrite of the app and doesn't use code from 1Password 7. Hopefully the fix will go through testing without issues and be included in a production update soon.

When the fix is available in the production version you'll see it noted in our release notes: 1Password for Mac Releases

Thank you for your patience.

-Dave

1P_Ben

Why was the date issue not there in 1pw7? Why should it be in beta when you've been using date since a very long time?

vishalsheth

The changes are currently available in nightly builds of 1Password. If you need the fix today, you'll need to use the nightly. After the fix is tested in nightly it'll progress into beta and ultimately into a stable build, but I couldn't say with certainty when that will happen. It'll depend on how the testing goes.

Ben

1P_Ben

I cannot try trial versions. Can we have the date format updated?

Hi @ndfred

I'm sorry to hear you're still having trouble with this item while using the nightly. Can you please try creating a new item, and see if the problem also applies in that case? Also, as a troubleshooting step, what if you edit this existing item and re-enter the dates. Does the problem persist in that case?

Please let me know.

Ben

And a lot of people looking for someone to blame / calling for a public post-mortem post for what is arguably a minor issue

Just wanted to gently push back on this. For me, a post-mortem would serve two purposes:

1. Give us confidence that the issue has been solved in a manner that prevents it recurring in future
2. Satisfy technical curiosity — 1Password do a great job sharing engineering details of their products, and I’m sure the explanation of this issue would be illuminating/educational for other UI engineers.

Case in point: the latest nightly didn't fix the issue for me.

1Password for Mac 8.10.12 (81012006)
macOS Ventura 13.5 (22G74)

Locale settings, note the DD/MM/YYYY format:

Before on a passeport entry, notice MM/DD/YYYY:

After, still MM/DD/YYYY:

Expected DD/MM/YYYY like the macOS locale settings specified:
1/2/2017 or 1 Feb 2017

Hit this issue as I was looking up birthdates in passeports, so super happy to see this fixed. For complainers, please test the nightly to make sure it fixes your problem, contrary to what I have seen calendar / locale bugs are tricky to fix because you have such a complicated matrix of setups (every country out there basically).

Kind of baffled that the response to "we've fixed it" is "please skip all the testing and dump this into prod" or "point me to someone I can blame through a post-mortem post" and no "I've just tested this and it solved my issue". If this goes to prod in a few weeks and doesn't fix your problem you will be mad again, so do your part and test it to see if it solves the problem you care about.

I also got quite confused in the past with birthdates on passeports showing up in the wrong format, UK locale with French language on macOS here, will try the nightly build and let you know if the problem is fixed.

I find the tone of the replies quite troubling here: "please release to prod right away" is not what I would expect from a critical app like 1Password, so I am actually glad this goes through all the typical testing and release stages along with all the other improvements in the next release, while I understand the "BUT I NEED IT NOW" feeling, this is software development 101 really.

And a lot of people looking for someone to blame / calling for a public post-mortem post for what is arguably a minor issue instead of testing / giving feedback on the nighly build that fixes the very issue they complained about and is by definition super tricky to test across all different locales. Help by testing, to make sure you don't complain a couple weeks from now when the fix doesn't work for you! Contrary to anyone's intuition, calendar / locale bugs are really tricky to get right.

Off we go:

I think this issue must be one of the most perfect example of Brooks's law I've ever seen. I second the request from the previous poster for a write up from Dave T. This issue and how it's been handled has severely damaged my trust in 1Password.