Birthdates off by one day in 1Password 5. [Fixed in Version 5.3]
Comments
-
Having the same issue across devices -- VERY disappointed. This is not merely an inconvenience, but a vital issue -- I put in passport dates in plane tickets and visa application, this could be a major disruption to my life.
Been a loyal customer to 1P for a few releases now and paying customer -- now having faced this unexpected and mission critical problem, I discovered that the AgileBits does not provide any easily obtainable way to contact support, sending you in endless circles to their manuals and FAQ(you) sites, there's not email, no phone number. So when I finally log in having spent 30 min of my workday looking for an answer -- do I get a response from the company rep -- no, from Community Moderator.
VERY disappointing, and no way to treat customers on a MISSION CRITICAL app.
If I don't get an explanation from the vendor, will not hesitate to publish this in social networks.0 -
This content has been removed.
-
Hi,
Do you have an expected completion date for this fix (I have the same off by -1 day on iOS issue described above, 1Password5 on OS X and iOS syncing via dropbox)?0 -
This content has been removed.
-
Hi @jimthing,
Thanks for keeping us to task on this! Believe me, when this bug is properly squashed, it will be in big flashing lights at the top of our release notes. (I'm not quite sure how the developers will make flashing lights happen inside a static text field, but I'm pretty sure they'll try. ;) )
Unfortunately, this means that, for the time being, the date issue is still present. As always, we'll be sure that your feedback is passed along to our development team.
0 -
One more month has passed since last post. Any news?
In the meantime I got a problem with my bank when tried to cancel the transaction abroad due to mentioned wrong date - thanks to 1password. Nasty situation, should I say...
0 -
Hi @Stas Pavlov ,
I am so sorry to hear that you've run across this bug. Our developers are working on this issue, but I don't have an update for you at this time.
We do know that it's important, and we're doing all we can to have it resolved as soon as possible. I will pass your thoughts along to the team.
0 -
Oh, and by the way in another thread regarding the "change of date while syncing" problem I got an answer: "...we don't have a timeframe for when the problem with 1Password for iOS will be resolved". Nice attitude towards data corruption problems for a top-notch super-safe and secure password manager. Keep up the good work, please!
0 -
Hi @Stas Pavlov ,
The reason we don't provide time-frames for fixes is simply that there are many factors that can influence an update's release schedule, many of which are beyond our control. For an important fix such as this, we do not want to promise something that becomes impossible.
I know we've said it several times already in this thread, but we do know that this is important, and the support team has been vigilant in reminding developers that this is a vital issue for our users. We will get this fix out to you all just as soon as we can.
0 -
I have just discovered this bug while on holiday -5 time zones from where I set up my passport information for four passports. I was wondering how I could possibly have managed to get my birth date wrong, and then noticed that the birth dates were wrong in all passports (as were all the dates). A quick test by setting my computer clock to my regular time zone caused the dates to be correct again, so I could see what the problem was and that led me to this thread. It looks like not so much a bug as a major oversight by the initial development team, and I can see why it will be a challenge to fix--probably need something like storing the tz where the data are entered and calculating the offset when not in the tz of entry.
Question: Posting prior to this is Feb 25? Has this been fixed yet? I am still on Mac Version 4.4.2 and not in a hurry to upgrade to Yosemite so I haven't seen the version upgrade notices. If it is fixed that would be another reason to upgrade to Yosemite.
0 -
@deoldphart - It's fixed, but I'm not sure which update brought the repair. The release notes are here, but I'm not where I can search for the announcement. I do believe you may need to correct the dates once after getting to the right version, and then you'll be set.
0 -
-
See also Better date handling in the 5.3 release notes.
0 -
So, @deoldphart, it would appear that the motivation to move to Yosemite to which you referred is in place. And thanks @MrC for adding the information I couldn't locate last night.
0 -
Great news. Thanks folks. Looks like I have to upgrade to Yosemite now. And for any other latecomers to this issue we can consider the issue fixed.
0 -
Thanks for the update @deoldphart :)
0