1Password 7 do not resolve Dropbox conflicts just yet but it is coming in a future update. They're generally safe to ignore as 1Password 4 doesn't resolve them either but we'll be implementing it for 1Password 7.

@MikeT To clarify this, when we see a conflict document in Dropbox, do we assume the changes are in place and to ignore it or what's the best course of action? (Two Windows 7 beta versions, one in heavy use, two iOS current version, one in moderate use).

To clarify this, when we see a conflict document in Dropbox, do we assume the changes are in place and to ignore it or what's the best course of action?

It is not us creating the conflict copy, it is Dropbox. In this case, you'll want to double check your latest change is visible in other 1Password app. Usually, Dropbox uploads the change you made on the local device and rename the remote copy as conflict.

Well, how is it not you, since nothing else has conflicts. There is something creating this. I wouldn't even know it existed except for the 'uploaded files' Windows 10 shows you. What else would be changing two 1P files at the same time? I'm only using one copy of the app at a time, I assure you.

Is there an easy way to see updates in the client by timestamp? All I can tell from dropbox is that this happened last night at 8:15, for example. So if I know what entries were made about that time...

While 1Password updates and creates the file, it is Dropbox that copies that file over to its servers and download it to other computers connected to the Dropbox account. In other words, it is Dropbox that is actually overwriting files in 1Password directory when syncing.

This is not limited to 1Password. You can replicate this easily by having the same or even multiple tools update the same file on two separate computers and Dropbox will create a conflict copy. This is a natural side effect of any syncing solution, nothing is immune to this unless the said sync tool is configured not to do this and that can cause data loss.

What is happening is that 1Password made a change to an item on the local drive, Dropbox copies it but detected there is an incoming change to the same file. If Dropbox cannot successfully figure out which is newer, it simply uploads the one you just did locally and rename the remote file as a conflict, so you'd have both files.

What else would be changing two 1P files at the same time? I'm only using one copy of the app at a time, I assure you.

Do you only use Dropbox? Is there any other syncing or backup tools you may be using? We had a customer who was syncing the Dropbox folder with their local NAS sync tool as well (to create a back up) and that caused a sync loop that resulted into sync conflicts.

Is there an easy way to see updates in the client by timestamp?
Edit: Sorting by modified time gives me nothing changed since yesterday morning at least in 'All Items'.

That won't work because you don't see the conflict in 1Password at all, it is not imported. That's why we have to add our own method to working with sync conflicts.

Never used anything else with 1P, in how many years I've been using 1P (since before version 4). Nothing else hitting 1P data, and as I said, not at the same time. Never had an issue with 1P data before, as far as I know.

So, what now? Delete the conflict file? Does it matter 'which' one it's in? (F)

For now, ignore them. Only tell us if it happens all the time, it is okay to see one conflict every once in a while .

No need to back it up; and we have the 1P backups, of course.

Since you said "of course", implying that you shouldn't back up, that's not the case.

Dropbox is not a backup service and only store deletions for 30 days for regular accounts. It's a single copy that's on several PCs, if you delete it and didn't realize, it's gone from all PCs. The general rule for backups are 3 copies, two local and one remote. A backup of your Dropbox folder is still recommended and another copy of your 1Password backup stored on an external drive (in case your hard drive dies) and one offsite (in case your home burns down especially if it has all of the several PCs) is still the best backup plan.

"Hi @bgsuisu, 1Password 7 do not resolve Dropbox conflicts just yet but it is coming in a future update. They're generally safe to ignore as 1Password 4 doesn't resolve them either but we'll be implementing it for 1Password 7." Considering an upgrade to 1Password7 but this is a factor. Thanks!

@jakegoat: We don't have the ability to "address" conflicts with a 3rd party sync service. Dropbox creates these when it tries to reconcile changes made to the same file on different devices within a time frame. If you're not missing anything, it's safe to ignore. However, I'd suggest checking your data/time/zone across all devices and setting manually if necessary to correct any discrepancies. Those can really wreak havoc with Dropbox's attempts to reconcile changes made across multiple devices, since there is no "source of truth"; it's taking everything and trying to pick the right "winner". Nothing against Dropbox, because what they're doing is nearly miraculous in that it works most of the time, across very different file systems. But this is par for the course, and can be difficult to figure out when something does happen to go wrong.

In addition to what Brenty said, this should not be a factor in your decision simply because it is not really a 1Password feature nor has it ever been implemented in any 1Password versions on Windows. This is just a courtesy thing from us to help make Dropbox sync easier to use but we recommend our 1Password.com membership instead if you have a lot of problems with Dropbox sync as we can't help much with Dropbox sync problems. Of course, this is a very rare issue with 1Password.com since we have servers handling this intelligently and automatically in the background.

MikeT, I don't have any problems with dropbox syncing - I've been sharing a password file with my wife for many, many years which has always worked, even if we're editing passwords simultaneously (not the same ones of course).

However, the reason I ask is because I haven't upgraded us to 1Password 7 yet and I understand that this requires a conversion of the agilekeychain to OPVault. The way I understand it, the agilekeychain was 100% granular - 1 file per record - but the OPVault implementation is banded. This suggests to me that it's more likely my wife and I could be accessing different passwords that happen to be in the same band. I'm looking for a little confirmation of this and a better understanding of how many passwords / records are held in each band. I've read this: https://support.1password.com/opvault-design/ and it tells me that if I had 600 passwords then I could potentially have 50 passwords per band, maybe more, maybe less, depending on UUID.

This would increase the chances of conflicts by 50x. So... it makes me wary of updating to v7. Hope that's a little clearer. Look forward to a response!

Yes, you would have an increased chance of sync conflicts if you're sharing the same vault with other users, same reason we're stopped recommending Dropbox sync for shared standalone vaults for many years now even before we switch to OPVault for all 1Password 7 versions.

If you're changing a lot of data at the same time with your wife, then I would recommend waiting until we add this support but we don't have a timeframe on this.

With me, today, it was the contents.js file that was in the conflicted state. I was concerned at first, but it resolved itself after I saved another password entry. I am running Version 7.3 on 2 iPhones and an iPad. I am still using Dropbox on a win10 box to sync. Must have been looking the other way when the Agilebits folks rescinded their Dropbox recommendation.

Mike's point was that you get a lot of conflicts with multiple people using the same vault since the same files will more likely be in use in multiple places at once. Dropbox is still a great service for syncing files in general, and I'd guess that a majority of us here still use it for that -- just not 1Password since there's a better option now. That's nothing against Dropbox; rather 1Password accounts were just designed with 1Password in mind, and it's a more seamless experience since we built the whole thing from top to bottom. Not having to deal with the filesystems across all sorts of devices and platforms helps avoid those kinds of issues -- especially in a group setting.