Problem with attachments ?!

bogomil22

Hello,
i use 1P4 and 1P5 for OSX. I sync the keychain with Dropbox. I have multiple Vaults (i have some entries from the primary vault that are shared with other vaults)
I have the following problem:
i edit an entry in the primary vault (i removed some text in the note-field and i deleted one attachment). Now i re-share that entry with antoher vault called for e.g. "Peter" so that Peter got hat changes too. When i switch to Peters vault i saw that dropbox is syncing. I also saw the changes i made on the note-field. So i guess the following problem is not a sync-error on my side. The problem is that the deleted attachment is still avaiable on Peters vault. I have to manually delete attachments in every vault alltough i "re-share" them after i edit them.

PS: I have no problem if i include a NEW attachment and re-share the entry to another vault.

AlexHoffmann

Hi there!

We're sorry to hear you have this problem.
Can you please tell us the specific versions of 1Password that you're using?
You can find out by clicking '1Password > About 1Password' in the menu bar.

Cheers and Happy Holidays!

bogomil22

Hi,
I use 1P4 v4.3.3 on my MBA (Mavericks). Like i said i reshare the entry with other vaults. After that i switched immediately to that vaults and i have to manually remove the attachment because it was still there.
So far i only use my MBA with 1P4.

Now i turn on my iMac (Yosemite) with 1P5 v5.0.2 and dropbox is sycing. I see all changes (like the changes in the note-field or a new included attachment) but the deleted attachment is still there too. I dont know but this is maybe a generally bug that 1P do not remove attachments when using dropbox???

Thanks

sjk

Thanks for the version details, @bogomil22.

I have a few more questions to help isolate where the trouble is:

i edit an entry in the primary vault (i removed some text in the note-field and i deleted one attachment).

Which version of 1Password is that edit made with? And is that primary vault being synced/shared?

Now i re-share that entry with antoher vault called for e.g. "Peter" so that Peter got hat changes too. When i switch to Peters vault i saw that dropbox is syncing.

Is "Peter" the secondary vault that's being synced/shared between versions 4 and 5?

I also saw the changes i made on the note-field. So i guess the following problem is not a sync-error on my side. The problem is that the deleted attachment is still avaiable on Peters vault.

Which version of 1Password is that "Peter" vault in where the attachment still exists after it's been removed from the item in the other version?

Does the same problem happen after making a similar edit in the other version of 1Password?

Thanks in advance for the answers!

bogomil22

Hello, thanks for your help @sjk:

To answer your questions:

Which version of 1Password is that edit made with? And is that primary vault being synced/shared?
-> The first edit was made with 1P4 v4.3.3 and yes, the primary vault is being synced/shared too.

(But: it doesnt matter if i use 1P4 or 1P5 because even on 1P5 is the same thing: You can test it yourself: (1) create a simple login in your primary vault and attach one small file (like test.jpg). (2) then share that new entry with another vault. (3) switch to that other vault an edit that new entry (delete that "test.jpg" file and attach a new "test.jpg.zip"-file and maybe write some text in the note-field) (4) Save that new changes and reshare that to the primary vault so that the primary vault got the new changes too. (5) If you switch to the primary vault you can see the changes in the note-filed and you can see the new attachment (test.jpg.zip) , but there is still the old "test.jpg" avaiable.....

Is "Peter" the secondary vault that's being synced/shared between versions 4 and 5?
-> Yes "Peter" is the secondard vault and it is beeing synced between v4 and v5. Like i said the primary vault is also being synced between v4 and v5. All my vaults are synced and shared because i use them to get more clarity. Some entries in the primary are shared with my secondary vaults. But i guess it doesnt matter if i synced all my vaults right?

Which version of 1Password is that "Peter" vault in where the attachment still exists after it's been removed from the item in the other version?
-> For what i have tested, it doesnt matter if i use 1P4 v4.3.3 or 1P5 v5.0.2 because its the same thing. Maybe you understand my issue if you follow my instructions in (1).

Thanks

littlebobbytables

Hi @bogomil22‌

I can replicate your bug.

When we added this feature I don't think it was envisaged it would be used to maintain multiple copies of an item over different vaults. By this I mean it works properly (both copying and moving) if the item isn't in the vault already. However, if the item is present in both vaults there are things to be aware of. It doesn't try to merge differences, it overwrites the entry in the other vault i.e if you're moving from the primary to the secondary vault the secondary vault's copy is overwritten. So if you make changes on both items and then copy or move the edits to the target location's item will be lost and there isn't a warning at the moment. As you've also discovered and notified us of, it isn't handling attachment deletions properly either.

Until we can correct these issues it might be prudent to limit yourself to a single copy of an item. So rather than two separate copies of an item just keep the ones in your shared vault. This hopefully wouldn't be too much of a hassle if you sync all your vaults (as I understood your last post). Of course this suggestion does partly depend on why you normally keep the same item in multiple vaults. You might have your reasons and find my suggestion unworkable, it depends a lot on why you're doing what you're doing.

I've created a bug report for this so the developers are at least aware of the issue now. Thank you for reporting this.

ref: OPM-2735

bogomil22

Hi @littlebobbytables,

Thanks for your answer. It is good to hear that the issue is not on my side and that the dev's of 1P may fix that.
I know that 1P doesnt try to merge differences if one entry/item is avaiable in two or more vaults. Because of that i immediately reshare/copy the entry to the other vault if i edit something. Like you said: the entry in the secondary vault will be completely overwritten if i reshare/copy it to it.

And thanks for your suggestion. I think i can handle that issue until it is fixed. I will delete all "duplicate" entries in the secondary vaults which have attachments. So i only have one copy in the primary vault until the issue is fixed. (I also have some entries shared in multiple vaults without any attachments. I think that entries are fine because if i only edit some Text-field and reshare it again to the other vault it will be synced correctly, right?).

It would be nice if you can notify me again if the dev's have fixed the issue and an update for 1P is available. (PS: i guess the issue occurs not only in 1P for Mac. It occurs also in 1P for Windows and on iOS. I guess you have to update all verions of 1P :\ )

Do you know / do you can estimate when the dev's have time to look at that issue?

littlebobbytables

Hi @bogomil22‌

If you want the items to remain shared with others I'd actually recommend keeping the single copy in the shared vault and simply switch between the vaults as required. For troubleshooting I'm often jumping between vaults and I find the keyboard shortcuts ⌘1 (your primary vault) and ⌘2...⌘9 (your secondary vaults) very useful. After a small while I find it second nature when an entry isn't in one vault but another as I separate my work and personal entries anyway.

The issue is most likely confined to just 1Password for Mac given how both 1Password for iOS and 1Password for Windows work. We don't have a way of moving items between vaults in iOS yet and in 1Password for Windows you close one vault to open another. 1Password for Mac is unique at the moment in how it handles vaults.

Unfortunately we can't give an ETA but I will be bringing it to their attention when I next chat to them - as it's the holiday season the 'offices' a little quieter than normal.

bogomil22

Hi @littlebobbytables,

Thanks for an answer. Are you sure that 1P for Windows and for iOS are fine? I do not yet test it on Windows but on my ipad i have the same problem that i saw the "old" attachment which acually should be deleted. I guess it doesnt matter if iOS havent the share-option yet, because i do it on my Mac and all devices are connected via dropbox.

Thanks

littlebobbytables

Hi @bogomil22‌

If there's an issue with your iPad I would suspect that it is a sync issue.

Can you create a test item on your Mac in one of the vaults you sync with your iPad and attach two silly/unimportant files to it. Let it sync and confirm there are two files present on your iPad. Delete one of the attachments from your Mac, are you saying the deletion isn't syncing?

Cheers for your help there.

bogomil22

Hi @littlebobbytables,
Thanks for your effort. The support of 1P is amazing!

Yes i have the issue on my ipad too. Then minutes ago i test it like that:
I create a test entry with two attachments on my iMac in the primary vault. After that I deleted the 1P App from my iPad and redownload it from the AppStore (v4.5.3 - because i am still on iOS 7 on my iPad). After downloading i configured Dropbox in the 1P app to sync my primary vault. I saw the test entry with the two attachments on my ipad. I closed the app on my ipad and after that i edit the test-entry on my iMac and deleted only one attachment. I opened 1P on my ipad and click the sync button. I still saw "old"/deleted attachment.

PS: i also test it with my iMac (1P4) and my MacBook (1P5) like that. I sync my primary vault like in the example above and it is the same thing. If i delete one attachment on my iMac and sync my MacBook, the "old" attachment is still there.

I do not test it on Andriod and Windows.

littlebobbytables

Hi @bogomil22‌

Thank you for testing that for me. It won't be the same issue despite the common factor of deleting attachments as the two sections of code will be very different. I believe this one will be fixed in the next release (but don't quote me on that!)

ref: OPM-85

bogomil22

Hi @littlebobbytables,

I only assume that it is the same issue because it happens on both "OSX to OSX" and "OSX to iOS", but you know the source code from 1P much better than me. :)
Nice to hear that it may be fixed in the next release.
Until then, thanks for the support.

Drew_AG

On behalf of @littlebobbytables, you're very welcome! And sorry again for the inconvenience.