Empty vault when opening shared vault from Dropbox
I have a vault which was shared through Dropbox. When I double-click it and enter the password, the vault is added and opened, but it's empty. The vault file is 407k in size, so I know it's not empty. What might be happening?
Comments
-
Hi @adriantoll,
I'm sorry to hear that you've been having trouble getting things synced up. Please confirm that the settings in Preferences > Sync point to the same folder in Dropbox on both computers.
Now, let's do a few tests here:
- Create a test entry on your computer: does it show up on the other users'?
- Have the other user create a test entry on their computer: does it show up on yours?
Please let me know the results of this little experiment. :)
0 -
Hi Megan
Thanks for your reply. I should perhaps have mentioned that this was a secondary vault.
The settings in Preferences > Sync both pointed to the same vault file in the same directory on Dropbox.
I had a slightly older export of the vault as a .pif folder, which I imported into the apparently empty vault and all the items were imported correctly.
I created a test entry on my computer and it didn't show up on the other person's computer, and the same was true the other way around.
However, when I added an item it seemed to be syncing via Dropbox, but when they added an item it wasn't. So I got them to delete their secondary vault from 1Password and re-add it by double-clicking the vault. The entered the password and it started syncing properly, so it's all working fine now.
I'm not sure why this wasn't happening normally previously, and in particular why the items weren't turning up when I added the secondary vault to 1Password, but at least it's working now!
Adrian
0 -
Hi Adrian ( @adriantoll ),
Thanks so much for letting me know that you've managed to sort it all out! There was a bug in an earlier version of 1Password 4 where 1Password 4.1 Losing Sync Permissions after System Restart. If you're using the version from the Mac App Store, this may have been where your trouble came in. If you reset sync (as you had the second user do) it should re-write the permissions and get things behaving properly again.
If you do see any further snags, please let me know, but I'm sure hoping that things work nicely for you now! :)
0