Forum Discussion
[Bug Report] Dates with year 3000+ show as 0
Hello AJCxZ0! 👋
Thank you for reporting this! Our developers are aware of an issue where dates that include years higher than 3000 aren't displaying properly in the 1Password app. An internal work item is open in our backlog to investigate this further and get it fixed in a future version of 1Password.
Out of curiosity, is there a practical reason why you need to enter 3000 or higher as the year? Or was this just the result of testing the app? I'm asking so that I can share any use cases with our development team to prioritize the issue appropriately.
-Dave
#32013
I first noticed this while testing.
While I don't expect many legitimate use cases for items having dates before 1900 or after 2999, I would prefer there be no such arbitrary constraints. Sanity checking for data type and length to ensure that date operations work is expected, but even something as reasonable as limiting the year to four digits will upset folks who want to store dates from the Duniverse.
PS. I have not tested in other language environments, so trust that the day and month are only in the wrong order for Usonians.
ModeratorThank you, an issue is open with our development team so that this can be fixed in the future.
-Dave
