Forum Discussion

pepijnve's avatar
pepijnve
New Contributor
3 months ago
Solved

Date field format does not match system settings

In the macOS client, I was just entering the details for a new item and notice the date fields are using mm/dd/yyyy as template. 

The macOS system settings are set to dd/mm/yyyy.

This inconsistency can be confusing and a cause of errors. Would be great if 1password could follow the system settings.

macos
  • 1P_Dave's avatar
    1P_Dave
    3 months ago

    Hello pepijnve! 👋

    I'm sorry that 1Password for Mac doesn't match the date format that you have set for macOS itself when editing an item. This is a known issue that our development team is aware of and is working on a fix for. 

    Keep an eye on our release notes which will mention a fix as soon as it is released: https://releases.1password.com/

    -Dave

16 Replies

Sort By
  • muonzoo's avatar
    muonzoo
    New Contributor
    4 days ago

    I am still seeing this as reported. As a power user an additional suggestion is that I would always prefer typing in a date in iso8601 format with flexible or absent separators over the interactive pop ups that force protracted interaction scrolling for (literally) years :).

    • 1P_Dave's avatar
      1P_Dave
      Icon for Moderator rankModerator
      3 days ago

      Hello! I've replied to your other post here. I'm sorry for the delay.

      -Dave

  • bendap's avatar
    bendap
    New Contributor
    29 days ago

    this is still not working. Why is this marked as solved?
    American format is so annoying, causing a lot of problems.

    • 1P_Dave's avatar
      1P_Dave
      Icon for Moderator rankModerator
      29 days ago

      bendap 

      I'm sorry for the continued disruption. Our developers are still working on the issue. Can you tell me which language/region you're using for macOS and which date format you expect to see in 1Password? 

      edit: Edited my reply since I'll need more information to identify the specific issue that bendap is running into. I'm sorry for the mistake! 

      -Dave

      • bendap's avatar
        bendap
        New Contributor
        29 days ago

        thanks for the prompt reply
        my settings are as follows:
        macOS: 15.3.1
        Region: United Kingdom
        Calendar: ISO8601
        Date Format: dd/MM/yyyy

        1Password for Mac 8.10.68 (81068014)

  • klindberg's avatar
    klindberg
    New Contributor
    2 months ago

    Yeah, this is really annoying, using the American format is really confusing and leads to actual issues (missed expirations and similar). Date format should follow Regional Settings i Windows or be possible to chose in Settings.

    And also, it should not follow language. I speak Swedish but live in Finland so I want the Finnish date format (dd.mm.yyyy), not the Swedish (yyyy.mm.dd), but at least that is better than American.

  • muonzoo's avatar
    muonzoo
    New Contributor
    2 months ago

    I'm not sure why this is marked as solved as I live in a locale that uses DD-MM-YYYY; but I set my OS to YYYY-MM-DD (because that's the CORRECT way to format dates - I'm opinionated that way, but ISO8601 is a common way to deal with this). I really don't understand why I see dates formatted in ways that I don't want or use anywhere in my system.  Please prioritise fixing this,  it isn't just a preference but errors get made and then there are consequences. My child's passport application was held up because of this bug (month and date transposed led to secondary questioning). Again - this isn't a cutesy thing but a real operability bug. As a 10+ year customer I really really want to see this fixed. The whole world isn't using the same date system and that the ISO standard isn't working correctly is a bit of a shocker to me after all these years. Sorry that I'm venting; but this isn't just a preference - it causes people problems.

    • 1P_Dave's avatar
      1P_Dave
      Icon for Moderator rankModerator
      3 days ago

      ​ muonzoo​ 

      I'm sorry for the impact that this issue has caused. 1Password should respect your system date format and this is a known issue that our development team is working to resolve in a future update. 

      -Dave

      • muonzoo's avatar
        muonzoo
        New Contributor
        3 days ago

        Thanks for the response. I'm not sure that I reported another subtle and dangerous bug: dates appear in iso8601 as per my locale setting but when I hit edit it quickly reverts to something else mm/dd/yyyy or dd/mm/yyyy. Which causes data entry errors as I need to notice and transpose. 

        apologies if this is documented elsewhere but I'm on mobile today. 

    • pepijnve's avatar
      pepijnve
      New Contributor
      2 months ago

      FWIW, I did not mark this as a solution myself. I was a bit disappointed to hear that this has been a problem for quite some time. I’m a software developer myself. Date and time handling is not trivial in programming, but consistent formatting and parsing is really not the hard part. Correct handling of timezones, arithmetic taking leap seconds and such into account, etc. is.

      I agree with you muonzoo that this kind of bug makes using date fields quite error prone. To make matters worse, it’s not just that on input the field uses the wrong format. On display it does the use the correct one. So the entered value flips from one format to a different one. In the end you can’t really trust the software and have to double check every time.

  • 1P_Dave's avatar
    1P_Dave
    Icon for Moderator rankModerator
    3 months ago

    Hello pepijnve! 👋

    I'm sorry that 1Password for Mac doesn't match the date format that you have set for macOS itself when editing an item. This is a known issue that our development team is aware of and is working on a fix for. 

    Keep an eye on our release notes which will mention a fix as soon as it is released: https://releases.1password.com/

    -Dave

  • snozdop's avatar
    snozdop
    Super Contributor
    3 months ago

    1Password has had problems with date formatting for input and display since v8 first came out years ago, with little progress in that time. They fix date related problems in one area, and introduce new issues elsewhere.

    I don't know whether its the same for you, but for me, whilst entering a date, the format is mm/dd/yyyy but then when not editing, the same date switches to dd/mm/yyyy format as it should be for my locale.

    I know dealing with dates can be complicated in programming in general, but this has been going on for years, and is a fundamental aspect of the app, yet remains unfixed after all this time.

    They've even recently added an expiration date field to items in the beta, but this suffers from the same ancient date formatting bugs as other date fields. You'd think they'd fix the date formatting functionality first, before introducing new date related features that just highlight these bugs.