New attachments lost if 1Password locked before saving item
Hi, just had the following chain of events which looks like a bug:
- Edited an item, and dragged new attachments from Finder into the item
- I did not save the item at this point because I had other changes to make to it
- Deleted the originals in my OS X Documents folder (which moves them to the OS X Trash)
- Went to empty the Trash in my Dock, but accidentally moved the pointer into the lower-right corner of the screen which I have configured as a "hot corner" in OS X to make my Display go to sleep — this caused 1Password to lock itself (although I didn't notice immediately)
- Finished what I was trying to do and successfully emptied the Trash in my Dock
- Realized 1Password was now locked, so unlocked it — and saw the item I had been editing appear with the new attachments
- Noticed that the item's Edit button just said "Edit", not "Resume Editing" as I expected
- Double-clicked the attachments, and 1Password then said "The file ... could not be opened because it is empty."
- Then clicked the Edit button — and 1Password crashed. I have included a link to this post in the crash report.
Now I have to scan the documents again — because I trashed the original copies in Finder, and 1Password trashed the attachment copies in my item!
Comments
-
Hi @semblance
Can you let us know what versions of OS X and 1Password you're running please. I've tried to replicated your findings but on 1Password 5.0.2 it stored the attachment and it was there when I resumed editing. At first I wondered if it was because I didn't completely delete the item but that worked okay for me too. So I'm wondering if you're using an older version and we've fixed a bug since then.
- Edited an item
- Attached a file
- Moved the file to the Trash and emptied Trash
- Locked 1Password without saving
- Unlocked 1Password, clicked on Resume Editing and file was there.
I also tried moving step 4. to just after step 2. but both resulted in the file being attached. That's why I'm wondering if we've fixed a bug and you're running an older version.
0 -
1Password 5.0.2 (502007) and OS X 10.10.1.
0 -
Hi @semblance
It seems you're running the same as myself. Can you replicate your findings?
0 -
Yes I can reproduce it as follows: create a new Secure Note called "test", drag a PDF attachment into it, and make no other changes to it. Then lock 1PW by clicking the padlock icon, unlock it by entering the Master Password, and double-click the attachment. I get the error "The file ... could not be opened because it is empty."
At first I thought maybe it's because it's a newly created item that's never been saved, not an existing item that I started editing.
So then I tried editing an existing item — this time a Login — and then doing the same remaining steps the same. Then I get a different error: “... can’t be found." But then if I Edit and Save the item without making any changes and double-click the attachment, it reverts to the original error "The file ... could not be opened because it is empty.".
0 -
Is it relevant that I'm using the Agile Web Store version of 1Password, and if I open an existing, normal, working attachment then its path is like this?
~/Library/Application Support/1Password 4/com.agilebits.Attachments/8E6BA1D3189C454C9AF241C63B2F08F1/B4FDFE915A9442E89722060C1473CDBA/
0 -
Hi @semblance
Can you do the following for me please. I'd like you to download our diagnostic report tool (see the link below) and then replicate the issue once or twice so it's fresh in 1Password's logs. Then close 1Password and do the following. Hopefully that will help the developers pinpoint what's going on as it's strange that it's happening to both of us.
I'd like to ask you to create a Diagnostics Report from your Mac.
Then attach the entire file to an email to us: support+forum@agilebits.com
Please do not post your Diagnostics Report in the forums, but please do include a link to this thread in your email, along with your forum handle so that we can "connect the dots" when we see your Diagnostics Report in our inbox.
Once you've sent the Report a post here with the ticket ID will help us to keep an eye out for it. :)
Once we see the report we should be able to better assist you. Thanks in advance!
0 -
FYI, this happens to me as well, using the MAS version. (5.02/10.10.1)
0 -
hi @littlebobbytables — that's done and the ticket ID is [#JYF-75244-416].
0 -
Hi @semblance Thank you for sending that in. I'll pass this onto a developer and see if the description and DR point anything out to them.
0 -
Hi @semblance,
I just replied via email. I was able to reproduce the issue when with a new Secure Note and I filed an internal bug in our issue tracker.
Please keep an eye out for the 1Password for Mac betas, the fix will make it there first :smiley:
Please let us know if there's anything else that we can do for you.
Cheers!
ref: OPM-2705
0 -
On behalf of Rad you are very welcome. :)
0