1Password 8 has been formatting dates incorrectly for over a year

I can certainly echo the (HN) poster&#x27;s comment from a few days ago:<p>&gt; I am having trouble with the date formats on macOS. My passport expiry is shown in MM&#x2F;DD&#x2F;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&#x2F;MM&#x2F;YYYY.<p>&gt; 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&#x27;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!<p>I&#x27;ve already had some wrestling with incorrect date formatting in 1Password, but I recently added my family&#x27;s passports and <i>almost</i> made the exact same mistake.<p>You could somewhat justify future support back when 1P 7.x was in support, but now that it&#x27;s <i>completely</i> EOL (mobile app is unlisted), there&#x27;s absolutely no reason for this. It&#x27;s literally one system API call. (Which they&#x27;re already using in the &quot;modified&#x2F;created&quot; fields on iOS!)

The debate here over which date format is best is pointless, and has nothing to do with the problem reported here. Computers have locale settings. You can set the date format to your preferred or expected format. The issue is that 1Password isn&#x27;t respecting that locale. This has literally nothing to do with whether the US is backwards or your own unique personal date coding is better.

I’ve been a happy user of 1 password for 5+ years, but I’m considering changing.<p>This goes beyond date format for me. Issues like these show that the company is not committed to listening to feedback and addressing issues. It erodes my trust in them. Given that they hold my passwords, trust is paramount.<p>Same with their decision of not adding 1 password 8 into the Mac App Store. I won’t install outside the App Store, so I’m sticking with 7. The moment that goes, so do I.

Hey HN!<p>Glad to have this reach the frontpage as 1Pass support has been unhelpful with this for months, so I‘m hoping to get some attention to this issue via this route.<p>My previous comment has already been quoted here, so I won‘t reiterate, but this issue is generally easy-to-fix, yet can have a huge impact if not working.<p>Very annoyed with 1Password’s product direction and support on this. Their customer focus has been off for a while in my eyes, sadly.

I&#x27;ve been holding out on 7 for reasons like this. The native macOS version seems to honour my system locale settings. I don&#x27;t see myself moving to an Electron-based app, and am really hoping that the updated keychain stuff in Sonoma will be such that I can just say goodbye, despite how much I&#x27;ve enjoyed 1Password for the _many_ years I&#x27;ve been a loyal customer.

The responses from 1Password are maddening. &quot;Can&#x27;t say if of when the dev team will address this&quot;, &quot;I&#x27;ll add a vote on your behalf (smiley)&quot;, &quot;Keep checking our release notes&quot;

&quot;We&#x27;re moving to Electron so that we can iterate and ship features and fixes much faster&quot;. This is the same 1Password that hobbled keyboard navigation 2 versions ago and still hasn&#x27;t fixed it.

The best date format, in my humble opinion:<p>yyyy-mm(mmm)-dd<p>2023-07(Jul)-12<p>...<p>Why?<p>- Goes from biggest to lowest value (year, then month, then day)<p>- To remove any ambiguation, also shows month in alpha format.<p>- Still sortable :-D This is the best part I think.

Time is a PITA to normalize between frontends and backends, but not an overly arduous task. I wonder what&#x27;s preventing them from know what the users preferred format is.<p>Anecdotally, I worked for a British company that used YY&#x2F;MM&#x2F;DD and it regularly caused reliability issues during operations. Of course, they responded with, &quot;What&#x27;s wrong with the date? It&#x27;s correct.&quot; Yes - correct, but not accessible especially operationally so. If you want to take advantage of a global userbase or workforce be prepared to have the tax of these kinds of features being necessary.

The 1Password move to election has left it full of things like this that AgileBits then pretend aren’t real. I won’t be renewing my subscription now this is the only option.

I had 1Password gobble my GitHub account credentials, which is fucking terrifying since most of my 2fa backup codes get stored in 1Password.<p>I really need to back everything up offline more frequently.

Would love to know if and why it is hard to implement this kind of feature for 1P. Any takes?<p>Also there is a heated debate that the UK is doing dates &quot;the right way&quot; and the US is wrong. Other than that people from Europe seem to think all of their practices are better than others, what is the possible reasoning that the order of numbers in a date string could have a right and wrong solution?

<a href="https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=36633116">https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=36633116</a>

Glad I&#x27;ve jumped ship to KeePassXC after 1PW7. The transition from 7-&gt;8 introduced nothing but bugs, electron bloat and lack of sensible data control to users, all of it sold by a tone-deaf PR department as &quot;but written in rust!&quot;

I wonder if this was a result of a PM treating localizacion as a feature that can be deprioritised to oblivion rather than a core deliverable of the feature “show a date”?

Why does a password manager even have major breaking changes?

<a href="https:&#x2F;&#x2F;www.youtube.com&#x2F;watch?v=y8OnoxKotPQ">https:&#x2F;&#x2F;www.youtube.com&#x2F;watch?v=y8OnoxKotPQ</a>

In the military, they force you to do dates as follows, which seems like the best idea to date.<p>01 JUN 2023

is anyone using 1Password 8? I thought everyone are still on 7