Error if new entries are not saved before auto-lock: Database Error
Support Staff2 Posted by Kyle Swank on 20 Feb, 2012 04:58 PM
I do apologize for the trouble. We don't want to assume anything
since in many cases saving or editing can be destructive and could
result in data that wasn't intended to be saved or perhaps wasn't
fully updated prior to us assuming it needed to be saved.
There may be some other solutions to this but right now the
easiest way to do this is to simply click the Save button if that's
what you intend to happen. Our thinking is that we shouldn't
"block" the locking of the application because there is an open
item in edit mode so we just lock and call it good. The intended
outcome is that when you unlock you have the opportunity to save
the item as if you had never left.
I'll make a note of this and see if we can come up with any
alternatives. Thanks for the feedback though!
Support Staff4 Posted by Khad Young on 30 May, 2012 08:18 PM
Thanks for your persistence with this. The behavior you describe
is actually a regression. This was resolved in 1Password 3.8 and
somehow reintroduced in 3.9. We should have this resolved in a
future update, although I can't give a time frame for a specific
If we can be of further assistance in the meantime, please let
us know. We are always here to help!
I noticed in your original report you were using version 3.9.4.
Is that still the case? Our latest release is 3.9.6 so let me know
if that's what you have now or not, this will let us know if it's
still an issue in our shipping code.
Yes, sorry, I forgot to mention that. I'm using the App Store version and currently have 3.9.6 installed on both my Macs (Mac mini Early 2009 and MacBook Air 2012), which are both running OS X 10.8 GM (12A269).
I also use the iOS version on my iPhone 4S and iPad 3 (iOS 5.1.1), and both are running the latest version of 1P available through iTunes.
Am 03.08.2012 um 01:07 schrieb "Kelly Guimont" <[email blocked]>:
Support Staff8 Posted by Khad Young on 03 Aug, 2012 02:46 AM
This is definitely something we want to get fixed, but it is not
possible to give a time frame. I've added some notes on this issue
to our internal tracker (including a link to this ticket so we
should be able to notify you when this is resolved). I've also
bumped the developers on this but know they are waist deep in some
other very critical projects right now. I'm sorry I don't have a
more immediately gratifying answer.
Please do let me know if there is anything else I can help with,
Support Staff9 Posted by Khad Young on 03 Aug, 2012 02:48 AM
I almost forgot: It is obviously not ideal, but just be sure to
save the item before walking away from your computer or closing the
lid and that will mitigate the issue until we are able to resolve
I'm sure you have already thought of this, but I just wanted to
make sure to mention it just in case or as a reminder.