Date format is incorrect in 1Password for Mac

@Tirioka

I'm happy that the date format is correct in 1Password on your Mac, thank you for confirming. 🙂

-Dave

@1P_Dave, thank you for your quick reply.

As requested, I'm attaching a screenshot with the Language & Region settings on my Mac.

@1P_Dave

I have attached Mac system setting and the date view issue.

I fail to understand why do you need these details? As I had suggested earlier give all formats in 1pw and let users choose. Once set would remain the same throughout the login.

The other issue of being able to search has started in Safari. I'm not able to search for the login from the prompt screen. I have to use the browser screen only.

Thank you for providing those screenshots. I can confirm that you're running into the known issue and I've passed those details, and your comments, along to our development team.

-Dave

I also have this issue where my date should be dd/mm/YYYY but is mm/dd/YYYY

@darbid I see the exact same issue when creating (for example) a new Software Licence entry. I've region set to 'UK', preferred language 'English (UK) - Primary' and date format 19/08/2024.

1Password insists on asking for purchase date in the format mm/dd/yyyy.

Same here. Additionally, it's displaying the week with the first day as Sunday despite the fact that I've set it to Monday…

Given most countries use dd/mm/yyyy and start the week on Mondays, should the default not match what the majority uses, rather than what the USA uses?

July 5, 2024. 1Password for Mac 8.10.34

Confirming that with system settings on English (Australia), Region: Australia and Date Format: 19/8/2024, 1Passport displays fields (in a Passport entry) as dd/mm/yyyy, but as mm / dd / yyyy when editing.

I can see that this issue has a long, long history. These are some of the aspects of the issue I see:

• Inconsistency between the display format and the editing format
• Bypassing multiple system settings (Region, Language, Date Format)
• Potential for errors when month and day are switched
• Serious consequences for errors involving identity and security
• Preference for developers' local format over international standards and user preferences
• No application-level setting available for users whose preferences don't align with any of the above
• Unnecessary friction when viewing dates requires a rethink of what they really mean. (I also get this I see that a book a I am waiting for is being released on 09/06/2024, and I get excited thinking it's already available, but... looking at you, Audible.)

I understand that work on the issue is on-going, but I also remember raising this issue when I first started using 1password, many years ago. (Oldest entry is from June 2011, with quite a few from 2013.)

What I don't understand is why using the system date format was not the first/only option in initial releases.

Coming from a smaller country, I am aware that anything I write (words, programs, whatever) may be read or used by people using a different system. Sometimes a writer's local flavour is good for the product. This is not the case for software.

When you assume that local customs are universal you make it harder for your audience to appreciate the good things you do.

Anita

I fully agree with everything @AnitaGraham said. It's completely ridiculous and it just seems 1Password doesn't care about their customers. Also the fact that customers have to do so much work when reporting an issue, like it's not that hard for test developers to test this obvious stuff themselves...

For me the issue happens only when entering dates:

If I enter the date using mm/dd/yy it then matches my system once saved.
While I'm at it, there is some very bad UX with the date picker- can't easily switch years, and paging between months causes the form to jump around- I can't just click 10x on the month button.