Windows 11 - Date formats are mm/dd/yyyy when my format is dd/mm/yyyy

Hello @inetbas! 👋

I'm sorry that you're not seeing the correct date format in 1Password. Our developers are working on a few edge cases where the system date format may not be respected properly.

Are you able to tell me if you see the wrong format when using 1Password in the browser? Or the 1Password for Windows desktop app? Can you post a screenshot of the wrong date format in 1Password?

I look forward to hearing from you.

-Dave

ref: dev/core/core#28051
ref: dev/core/core#28017

Hello Dave,

I am using the Windows 11 1Password App. I.e. when creating a new item e.g. Passport. It default as entry and showing mm/dd/yyyy instead of dd/mm/yyyy.

I was not sure if it was due to the dd-mmm-yyyy (1-jan-1970) format on my Business laptop. So I Check also om my personal WIndows 11 laptop on which the local format is dd/mm/yyyy.
See screenshots now also from my personal laptop.

Dave,

doing the same via Chrome on my private laptop.

@1P_Dave . Hello Dave any update from your side on this?

@inetbas

I'm sorry for the delay in responding. 1Password for Windows not respecting your operating system's country and regional formats is a known issue that is under investigating by our development team. I've let them know that you're affected by the issue as well.

While I don't have an ETA on when the issue will be resolved, you'll see it mentioned in our release notes when it is: 1Password Releases

Thank you for reporting the issue and I'm sorry for the inconvenience.

-Dave

ref: dev/core/core#28017

Hello @1P_Dave , thank you for the reply. As the same was already reported for a while. I hope that this gets address in the short term. I encourage (software) companies that often are very USA focused to understand there is also another world with a lot diversity and take local standards and differences into account with their products.

Best regards, Bas,

@inetbas

Understood, the app is designed to respect the operating system's date format but a bug prevents that from happening in certain cases. The team has fixed the issue for many of the reported situations and hopefully the rest are fixed soon as well.

-Dave