Hi, greetings from the UK. I noticed that the date / time format for created / modified uses North American format (ie. back to front for us Brits). Could this be changed to use the locale of the user please? Many thanks. 1Password Version: 8.7.1 Extension Version: 2.3.5 OS Version: macOS 12.4 Browser:_ Firefox 101.0

Hello everyone, The development team is working on a complete overhaul of how dates are handled in the app as a whole but that work will take time since we want to make sure that we get it right. Fixes included in previous updates to 1Password have improved the situation considerably for many but there are certain cases where localization is still not working as it should be. Specifically, if you're using a region that differs from the language selected. For example: Region: United Kingdom Preferred language: English (US) Although the region is set to the United Kingdom, 1Password displays the date format as if the region was set to the United States. This is due to language and region not being clearly separated. A workaround is to change your language to the region that includes the date format that you'd like to use. So, if you wanted to use the DD/MM/YY format used in the UK you would set your preferred language in macOS to English (UK). This suggestion isn't going to work for everyone since some folks require a specific regional language that differs from their geographic region. Our development team is actively working on a proper solution. But I wanted to mention the workaround again for those who were new to the thread. As mentioned, our developers are working on a complete refactor of the code that handles the rendering of dates/times. Not only will this refactor improve 1Password in many areas, and allow for better date rendering in general, but the refactored code will allow 1Password to correctly display dates/times according to the region set in macOS and will resolve the issue reported in this thread for all users and all regions. The team's focus is on getting this new date/time rendering system developed and released. While I'm unable to say which update will include the overhaul, our developers continue to be aware of the importance of getting date regions correct. I know that this issue has been affecting some folks for quite some time and I'm sorry for the continued impact to your workflows. Your feedback and frustration regarding this issue is heard by the entire team. We appreciate everyone’s patience and understanding as we continue to work to develop and release a solution that will resolve the issue for everyone. -Dave

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.

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 notice this problem still hasn't been fixed completely after 2 years? I'm in the UK, using a Mac and have just tried updating my passport expiry date which is displaying in mm/dd/yyyy format instead of my system default which is dd/mm/yyyy. I can't see any way of changing this. Seems strange that such a simple problem is apparently so difficult to fix - doesn't exactly instil confidence!

Nope. This is the non-edit-mode: (this should show 13/7/23, or preferably even 13/7/2023) This is the edit mode: This one is correct. Same issue still also on iOS, in the latest version of 1P (8.10.18). Once more, for completeness sake, my region settings in MacOS 14.0: What I honestly don't get (and I am genuinely interested) is why this is so hard to test. You guys have Macs right? Just set your language to US English en your region to The Netherlands. I have reproduced it on 4 different machines here in the office. It feels like you think you fixed the issue but didn't actually test it before releasing.

Date format is incorrect in 1Password for Mac

paulgrav
New Contributor
2 months ago
jgwhite Didn’t even know that existed. Would I trust it? TBH it’s not a problem I need 1Password to solve.
jgwhite
Occasional Contributor
2 months ago

What’s just occurred to me is that for date fields in passports it’s probably safer to store the dates as text

paulgrav the only drawback with that approach is you won’t get to take advantage of the very nice 1Password feature where it can inform you of passports and IDs that are expiring soon.
paulgrav
New Contributor
2 months ago
I think this is a lost cause. 2yrs and it’s still a problem. I’m giving up.

What’s just occurred to me is that for date fields in passports it’s probably safer to store the dates as text. 9 times out of 10 I just want to see what the value is, so if my expiry date is displayed exactly as I entered it e.g., 1970-01-01, it’s unambiguous what the month and day are.
snapperfish
New Contributor
2 months ago
I notice this problem still hasn't been fixed completely after 2 years? I'm in the UK, using a Mac and have just tried updating my passport expiry date which is displaying in mm/dd/yyyy format instead of my system default which is dd/mm/yyyy. I can't see any way of changing this. Seems strange that such a simple problem is apparently so difficult to fix - doesn't exactly instil confidence!
1P_Dave
Moderator
5 months ago
Hello folks,

Thank you to everyone who sent in screenshots and diagnostics reports. The team doesn't require any more information from affected users and work is actively progressing during the current development cycle to get this issue resolved.

I apologize for the continued inconvenience that the issue is causing. As soon as a fix is available in the beta version of 1Password I'll make sure to update this thread to let everyone know. Thank you for your continued patience.

-Dave
vishalsheth
Frequent Contributor
5 months ago
fok
I have the same option on iOS. The issue is on Mac and Android. When viewing I get the correct format on Mac but when editing it switched to another format. Same is the case on Android.
This was not an issue till 1pw7. I don't know what has changed. I'm sure this part can be taken care by 1pw so at least the format is viewed in the same format on other devices. 1P_Dave
fok
Occasional Contributor
5 months ago
vishalsheth developers can also query these formats from the operating system, what you want is the medium date format string variant instead of the short one. Here is a screenshot from the iOS settings when using Germany for regional settings (please note the format examples on the bottom):

It's all there in all operating systems, developers just need to actually use them. What you probably want is a way to switch between short/medium/long date format strings in 1Password once the system settings are correctly used by 1Password, but given the ignorance they have shown regarding this issue I think we all can be happy if they eventually at least support system locale at all.
vishalsheth
Frequent Contributor
5 months ago
fok

I would always like to have format DDMMMYYYY or MMMDDYYYY. The idea is in this format the month is always in alphabets so one can never mis read it. These formats are not available on Mac, Android or iPhone.
fok
Occasional Contributor
5 months ago
vishalsheth Because using the system settings' locale is the correct way to do this. This is usually very trivial with modern SDKs because you just ask the operating system for the correct format and use it.

I think the main question is: Why is this so complicated in this case or for 1Password?
vishalsheth
Frequent Contributor
5 months ago
1P_Dave

Why is it so difficult to have a correct date in correct format? Why depend on the systems? Why not 1pw allow the date formats? Allow all possible option in formats so nothing is missing and everyone is happy.